This entry was posted on Sunday, June 19th, 2011 at 11:11 pm and is filed under business requirements gathering. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Importance of Gathering Business Requirements
In any project, among the critical elements is the business requirements gathering and creating a clear picture of what needs to be delivered. The initiators of the project generally have a clear view of the end goal and what needs to be accomplished, but they rarely consider or understand all the specific requirements of the stakeholders regarding the system that is being purchased or developed.
Proper gathering of requirements and creating a complete set of clear system requirements upfront enables more accurate cost estimates, better planning and better adoption of the final outcome. It also improves customer satisfaction and provides shorter delivery cycles. System requirements gathering may seem a simple task. However, it must be done effectively. Otherwise, the whole project could be in trouble. At the beginning of a project, the system requirements are often somewhat vague. If you ask the stakeholders what they think the requirements are, there is a good chance that you will get different opinions and perceptions of what is to be accomplished. Nevertheless, with the help of a business analyst with good background in business system analysis and requirements gathering, a common vision of the business requirements can be achieved.
The business analyst should start with the sponsors of the project to get a clear understanding of both the objectives of the project and the business goals. This will enable him to gather the requirements in the correct context. Failing to do this will just result to the gathering of requirements that are out of scope or that promote individual agendas rather than the true vision of the organization.
Leave a Reply

