BA vs. PM: Where Do We Draw the Line?
So very many acronyms, so little time…
We abbreviate, of course, to expedite talking about something that is long, complicated or that we talk about frequently. So project managers become PMs. Steering committees become SCs. Project Management Offices become PMOs. Information Technology becomes IT (and begets hundreds of other mind-numbing acronyms in the process). And Business Analysts have become BAs.
In the last few years, we’ve seen a rise in awareness, visibility and formality associated with business analysis. At the same time, there’s been an increasing intersection between business analysis and project management. The two concepts show up in the same conversations. They get talked about in the same meetings. The two roles are sometimes performed by the same people. And members of each community crash each other’s events.
All of this can leave people scratching their heads and wondering what it all means? Where are the overlaps? Where are the boundaries? What are the divisions? What does it mean to be a business analyst relative to what it means to being a project manager? When would I want one over the other? And is there any value to being both?
The alignment between business analysis and project management is relatively unsurprising, given the emphasis that both play on understanding and managing stakeholder expectations and
Please log in or sign up below to read the rest of the article.
"Managing senior programmers is like herding cats."
- D. Platt