Business analysts and project managers should be the MVPs of the IT team because of their theoretical ability to help IT understand and better meet business needs. Instead, business analysts are mostly misunderstood and even <strong>sometimes resented by IT</strong>.
Uncertainty about their responsibilities is an issue for BAs, as I found when I interviewed several of them for a story late last year, one that often results in them being asked to do an awful lot. (The job description e-mailed to me by one of my interviewees seemed incredibly broad.) Yet other positions in IT, most notably the CIO, experience the same kind of <strong>fuzziness in their job descriptions</strong>.
A bigger issue for BAs is the lack of a clear path of career advancement, says Michael Hugos on CIO.com. He writes:
So senior people in these roles get stuck in low-level positions and don't have the opportunity to show what they can really do. Everybody loses. Experienced PMs and BAs are marginalized, projects suffer, and companies who carry out system development projects don't get the results they want.
His suggestion: There should be different titles -- and salaries -- to differentiate senior business analysts from less experienced ones. The same should be true for project managers, another position that is often seen as junior-level regardless of the years of experience and professional accomplishments a person brings to the job.
Hugo believes senior project managers should have at least a decade of experience and have done stints as both a developer and a business analyst. He offers "system builder" as an appropriate title for such folks. His suggested criteria for senior BAs: five-plus years of experience and an understanding of process mapping, data modeling and user interface design. A good title for them would be "business system designers."
Project success rates will increase if "system builders" run projects, with the able assistance of "business system designers," predicts Hugo.