Soft Skills

In the world of underlying competencies that contribute to strong business analysis, the soft skill of analytical thinking and problem solving may seem pretty self-explanatory. Clearly, it involves sorting through business problems and information in an informed, methodical way. In order to do this, an analyst must research the problem and then propose intelligent solutions.

Driving Lessons. We all did it. We all know how that very first one went. It was described to us that the clutch should be engaged, place the car in first gear, release the handbrake, release the clutch and press down on the accelerator… Only for the car lurch forward then stutter and lurch forward again. This process continues several times before the car stalls and comes to a stop.

What does innovation mean to the Business Analyst?  This article is my practical way of handling innovation and understanding the role that the Business Analyst plays in innovative projects.  Giving five tips for success the article explains how innovative projects can be approached and how the unique skill set of the Business Analyst can add measurable business value. 

Business analysts are jacks-of-all-trades -- and masters of some... unfortunately, many BAs fall short. They often spread themselves too thin, lack the requisite confidence to speak with authority, or don’t understand fully the important role they play.

It’s pretty rare to be a business analyst and not facilitate meetings...  In this article, we’ll look at 3 possible roles new BAs fill in meetings, how to expand your meeting facilitation experience, and review 5 critical meeting facilitation techniques that will help you run working, productive meetings.
 

Interaction skills are a soft skill set that includes tactful communication, mediation, and diplomacy. BABOK divides interaction skills into three broad areas: facilitation and negotiation, leadership and influencing, and teamwork. All of these skills encompass the ability to navigate politics, even in tricky territory, in order to bring people together in consensus on a project, to mitigate conflicts, and to help people feel heard.

In an ideal world, a single, full-time, expert user would indeed be sitting within view—“on sight”—of developers, ready at a moment’s notice to speak definitively for the entire user community. In reality, this is unlikely in most situations.

This article describes an integrated system of actions, tasks, and methods for managing project stakeholders. It highlights the strategic business actions, the tactical project tasks, and operational methods conducted by project sponsors, project managers and business analysts respectively.

Business analysts need to understand their role on a project. Please note I use the word 'role' and not 'job' or 'the work we do'. As business analysts, our role is to deliver business value. If you do not have a clear definition of what that business value is, how can you expect to deliver it? “Improve the customer experience.” Where is the business value in that? And how do you measure it? When faced with objectives that are poorly defined, the business analyst is allowed to become like that irritating toddler, constantly asking “why? why? why? why? why?”.

Recently I saw the movie “42,” based on the true story of Jackie Robinson,who in 1947 bravely fought custom, bigotry, and violent hostility to become the first African American to play major league baseball. His courage came from his inner strength which allowed him to withstand with dignity the cruel behavior from fans, other team managers and players, and at first some of his own teammates.

Multiple stages of a project can benefit from brainstorming, from identifying your stakeholders, to eliciting requirements, to enterprise analysis. In UML for the IT Business Analyst, Howard Podeswa describes brainstorming as useful “during the Initiation phase and whenever the project is ‘stuck’”.

The purpose of this article is to assist business analysts in writing business requirements. This article provides six guidelines on technical writing. The six I cite here are the major ones I consider when writing a business requirements document (BRD).There are, of course,other technical writing guidelines; for comprehensive texts, see Further Reading (1).