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.

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.