I acknowledge that some BAs think their job is done when they hand over the requirements to the developer. I would challenge these BAs, to look beyond the formal requirements documentation and embrace the important role and position they hold in the mind of the business user - that of “translator”.
BAs with their insight into the business, are very much becoming a facilitator and hence “translator” for the business area. They are seen to “bridge” the gap between the business area and the technical group. The business feel comfortable with the BA as “they speak business”and not just “techco”. They workshop the requirements and issues with the business team and work out how to translate this into requirements that serve the needs of both groups. A Business Analyst in the broader sense, is very much focused on the client and its business and therefore has a valuable role to play.
The ABAA recognises that the discipline of a BA is not just restricted to commercial analysts, process analysts and systems analyst and that in fact the work of a BA is a lot broader than these three disciplines. In their draft framework paper, core BA activities are proposed as a starting point by the ABAA. These core activities are then built upon to introduce “the iterative facilitating activities of communication, planning and control; traditional project management disciplines, essential to effectively structure, co-ordinate and drive an analytical assignment”.
This move of BAs into the facilitation sphere may be seen as in conflict with the role of a Project Manager, however I think it is reflective of where the BA profession may be heading. This facilitator role can make the BA role a rich and rewarding experience as you move into a “trusted advisor” role for the business area.
Recent Comments