Many people, and organizations, consider requirements elicitation as the only task that the Business Analyst (BA) performs. That couldn’t be further from the truth, and those organizations are missing out on the benefits of all the other tasks that a BA is the optimal role within the organization to perform. This is not limited to Cincinnati and Dayton area companies, it happens all over.
We have already discussed one task of a BA, Stakeholder Analysis and Management. By identifying all possible stakeholders for a particular solution, the BA helps ensure inclusion of all requirements for the solution in the project. This leads right into today’s topic: Getting Requirements Right!
Getting requirements right means getting them right the first time, at the beginning of project work; before the project gets into the development stage of the Project Life Cycle (PLC). This reduces re-work and frees up project team members to move on to other projects. This can lead to reduced headcount and increased project success rates within the organization. This can also lead to fewer projects within the organization as getting all requirements included in a project and getting those requirements right can mean that follow-up projects to remove a solution feature because it interferes with another system that was not considered during the initial project will not be necessary. Also, a follow-up project to add a solution feature that was missed in the initial project can be avoided.
Getting requirements right the first time affects an organization’s bottom line, and that can be a considerable effect. Many consider this the primary role of the BA and their main purpose for being. As for the tactical role of a BA that is correct. So Get the Requirements Right the first time!