Business Analyst, Requirements Analyst, Business Systems Analyst…different “titles”, but usually performing the same job…
The requirements analyst’s primary responsibility is to gather, analyze, document and validate the needs of the project stakeholders. As the principal conduit through which requirements flow between the customer community and the software development team, you’ll play a central role
in collecting and disseminating product information, whereas the project manager takes the lead in communicating project information.
Requirements analyst is a project role, not necessarily a job title – although many companies use this as a job title. A talented analyst can make the difference between project success or failure. In his book, Software Cost Estimation with Cocomo II (Prentice Hall PTR, 2000), Barry Boehm notes that seasoned analysts can reduce a project’s required effort by one third compared to similar projects with inexperienced analysts, and projects with highly skilled analysts require half the effort of those using the least capable analysts.
Because the role of requirements analyst has such a significant cost impact, companies recognize the need for this role and it’s an excellent career choice.
If you want to move into a BA role or think you may want to, but aren’t quite sure, set up a time to speak with me during a complimentary assessment session and we’ll discuss the options available to you. Click here to access my calendar.