Struggling to define Business Analysis and the BA role

There is still a lot of debate in BA circles around what our role is and what is offered by the various organisation representing and supporting BAs. Is the role all about requirements analysis? Are we just interested in IT and systems analysis or are our practitioners focused on the broader business and processes?

I came across an interesting article forwarded to me by some information architecture friends, Matt and Andrew. The article on the discipline and role of IAs was written by Jesse James Garrett in 2002 and the issue of defining the roles of IAs that they were struggling with back then, are very familiar issues that we are now facing as BAs.

Garrett argued that there is a discipline known as information architecture as well as a role known as information architect and that they evolved hand in hand but the time had come for change. Thus, just as there is the discipline of Business Analysis, there is the role of a Business Analyst. If we define the discipline based on the role then we may potentially be too broad as the role of as business Analyst varies from organisation to organisation an em-compasses BAs working as commercial, process, financial, technical and systems analysts. If we define the role based on the discipline, then whatever the field of business analysis is, those who are specialists in this field are business analysts. This definition however could, in practice, become too narrow.

As suggested by Garrett we seem to be at an impasse Any definition broad enough to encompass the role is too broad to foster useful discussion of the discipline; any definition narrow enough for the discipline is too narrow for the role” and “Basing either definition on the other means one is going to be insufficient. Trying to do both at once isn’t working, producing a classic chicken-and-egg problem”.

We really need to define the scope of what is business analysis and then can look at what that discipline offers in the way of frameworks and tools to its members, as the specialists in this field. If we decouple the definition of the discipline from the definition of the role entirely then we have the opportunity to concentrate on more precisely defining the discipline of business analysis.

4 Responses to “Struggling to define Business Analysis and the BA role”


  1. 1 Adrian

    Hi Maria,

    This is a subject that I have also been thinking about lately. It is very important that we open the discussion within the BA community to clarify the confusion which exsits around the BA roles and titles.

    Here is my recent blog entry on the topic:
    http://www.modernanalyst.com/Community/Blogs/tabid/78/EntryID/18/Default.aspx

    Also, here is a forum thread discussing this topic:
    http://www.modernanalyst.com/Community/Forums/tabid/76/forumid/-1/threadid/279/scope/posts/Default.aspx

    Best regards,
    - Adrian
    Publisher, ModernAnalyst.com
    http://www.ModernAnalyst.com

  2. 2 Craig Brown

    Hi Maria

    I was just dropping by to ask you to go visit Modern Analyst and look who’s been here before me!

    Your blog, mine, Moden Analyst, the AABA and IIBA etc are all going to play their part in defining the role and profession but whatever definitions we come to are only going to be temporary.

    I see the role definition beginning with the technical competencies that istinguish BAs from other roles and eventually evolving into a broader view on what BAs do and how they contribute to project and business success.

    Project management is travelling through the same arc, although with 30 years headstart. See “Practitioner development: From trained technicians to reflective practitioners ” by Lynn Crawford, Peter Morris, Janice Thomas, Mark Winter as a commentary on the PM evolution.

    All the best with the blogging - and if you are ever in Melbourne get in touch!

    Craig

  1. 1 Bad English, Business Analysis and Business Analysts « Matt’s Musings
  2. 2 Handbags at dawn — defining the damned thing « Matt’s Musings

Leave a Reply