Not too long ago I was talking to a prospect about their business analysis requirements for his clients. I left with the impression that the Business Analyst (BA) is viewed just as an interface between the developer and the client? I get a similar impression when I talk to other prospects about their business analysis requirements. Organizations looking at hiring BAs to just act as go-betweens between the client and developers need to rethink this approach.
I think the BA is more than just an interface. The BA needs to understand why the project is being implemented in the first place and what the long term goals of the company are. S/he needs to identify trends and make an educated guess about the future requirements too. Whenever I have donned the BA hat (most projects were for small businesses), I find that the end users typically do not think strategically. They just want the application to mimic their existing business process. Never mind if those processes may need a change with new technology.
I once worked on a project where the use of paper and a pen for record keeping is still a norm. The pen and paper technology needs to follow a different business process than when compared to an IT enterprise system. For example, with the former you will need to file multiple copies of the same paper in physical files while in the latter all you may need to do is to scan it and destroy the physical copy. Same result, different processes.
Hence, BAs need to understand how the project scope fits into the bigger picture of the organization’s strategy. BAs need to correctly identify the scope of the solution, costs and benefits of the proposed features and how important each feature is to the organization’s strategy execution. After all, strategy implementation is the hard part and the BA can make or break that objective.
So the next time you look for a BA, evaluate if s/he also understands business and strategy. Unless you want a glorified programmer, the BA’s IT skills are secondary when considering the big picture.
Excellent observations. I’d also add the following:
Business Analysts need to master the art of change management: how to successfully introduce change into an organization. People skills are critical as a great deal of the BA’s time may involve communicating, coaching, mentoring, negotiating and persuading in order to get the job done.
Thank you Mark for the excellent input Mark. You are absolutely right - change management is a skill that the BA needs the most; more so when process change is involved.
I am totally with you on the points you outlined.
Excellent comments.
Of course not all projects call for strategic BAs, and not all BAs on strategic projects need to be at the strategic apex of the org, but yes many do.
Better Projects
Modern Analyst
Craig, Thanks for stopping by and taking the time to comment. I suppose it would depend on the kind of work that is needed to be performed.