Requirements Analysis is generally the knee-jerk step that an inexperienced or untrained Business Analyst jumps to first. It's the tactical core of Business Analysis (along with Solution Assessment) that is very easy to skip to.
Requirements Analysis is the pillar that defines how BAs prioritize and elaborate the requriements to enable a project team to deploy a given solution that meets the needs of the sponsors.
The steps involve:
1. Prioritization of the Requirements
2. Organize the Requirements in a hierarchy that fits
3. Specify the requirements and model the requirements
4. Determine the assumptions and the constraints of the project
5. Verify the requirements with the relevant team members
6. Validate the requirements
When people read the list above, a common question is "what is the difference between VERIFICATION and VALIDATION". ?
Stay tuned...
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment