Over the past few years I have been advocating that business analysis is a distinct profession, separate from project management, separate from development, separate from quality assurance. I believe that eliciting, and analyzing requirements; and making sure they are used to create a good quality solution is a full time job. I also believe that if an individual can focus on this type of work, they improve and become more proficient.
I also recognize the reality that many organizations expect employees to perform multiple roles. I understand that on small projects one person may be the BA, PM, QA and developer! So I am interested in the titles of people who are actually doing business analysis work. Some of these individuals are not aware of the IIBA or of the phrase we have decided to use to describe requirements work (business analysis). We are working to use the title less, and the description of the work more, to reach out to individuals who would benefit by knowing about business analysis tools, techniques, and standards.
In addition, having strong problem solving, communication, and analytical skills will improve the productivity of most professions. These are critical skills to the success of every organization.
2 Comments
At my firm, we are called Business Analysts.
We also have another role: Product Owner(PO) which is the most closest to the role played by a BA. But a PO is shouldered with responsiblity for entire owning business application and its related projects. Both the BA and PO roles work hand in glove in a project or even replace each other for a project depending on size,schedule,skills,etc…
I agree with your promotion that Business Analysis should be a distinct profession. But my understanding (open to correction) is for small size firms where resources availability is tight, BAs are asked to take more responsibilities like QA, or even System Architects for that matter.
Who performs business analysis work in your organization?
Way back when I started my IT career, we were in a small shop and I programmed, designed, tested, trained, etc. My “BA” activities were considered, then, as a “liasion” and it really worked well as I got a chance to “walk in the (internal) customer’s shoes” and develop longer-range solutions that solved more than an immediate problem. So..to use your phrase above, I was a” BA, PM, QA and developer”.
In my current consulting role the customer wanted what they call a “Business Systems Analyst” which meant someone who had past experience with designing functional as well a business requirements. So I learned to adapt and use what I learned as an “IT geek”.
Waterfall was an answer to a time when there were no structured processes and “best practices”. A BA who grew up in this environment was well-suited for this. I am sooooo pleased to be here to see the transition to the Agil/Iterative approaches and to the changes it will most assuredly bring to the BA’s purpose in life. I would hope all BA’s embrace and learn how to fit their skills into this (relatively) new methodollogy.