What is a BA?

As far as I can tell, to this day, many (probably most) people still aren’t sure what a business analyst (BA) actually does. Does it consist in quantitative analysis of business data (business analytics)? Or is it related to corporate valuation?

Well, not really.

The IIBA (International Institute of Business Analysis) defines it as: Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders.

In other words, a BA reviews how an organization works by:

• Understanding and documenting it's Operating Model
• Capturing, defining and documenting business needs and requirements
• Recommending changes to processes, systems or strategies that create value and align with organizational goals and strategy
• Communicating findings, results and recommendations in a clear and concise way to various stakeholders
• Bridging business and technology (especially for Technical BAs)

This may sound like a very broad job description and truth be told… it is.

BAs are often parachuted into new contexts with very little information and structure (sometimes only a vague mission statement) and they must come back with a plan, a structure, a strategy, and an approach to tackle the problem. BAs act as strategic and tactical scouts who must not only report back the new information they gather but also process it and take an active role in planning next steps.

Business Analysts need be both good generalists and also avid learners who are always seeking to better understand the inner-workings of the organization they are in. In fact, what often separates the most effective analysts from the rest is this ability to juggle the broad generalistic aspect of "Business Analysis" with in-depth knowledge and understanding of the specificities of the business they are assisting. 

But analysis alone isn’t enough; unless you’re a one-person shop, communication is also a key aspect of the job not to overlook. Workshops, Recurrent Status Meetings, Agile Meetings, Presentations, Spec Documents, the BA is constantly put forward in situations where communication abilities makes or breaks outcomes. 

Clearly there is a bit too much to talk about for a single blog post! 

My goal with this blog is to develop the different topics surrounding the role of the Business Analyst including learning experiences, thoughts, opinions and also share material (templates and charts). I will also post about Quality Engineering as this is becoming a bigger and bigger part of the software development lifecycle (SDLC) and that I foresee BAs will start taking a progressively more important role in this process. (I might also post the impact of AI on the BA and QA professions)