Requirements prioritization
The normal scenario while gathering and analyzing requirements is gather User requirements (WHAT the business/user needs), then derive the Functional requirements (WHAT the system should generate) and later the Functional specification (HOW to achieve the requirements). Now the question;
Once the BA prioritize the User requirements, does s/he need to prioritize the functional requirements too (once derived), if yes and if the priority is not at par with the respective UR how do we go about it. Can the BA only prioritize the URs and not the FRs? What is the best way to handle such scenarios?
Groups:
- Ranjit's blog
- Login or register to post comments
- 5320 reads
Business Priorities by kmatthews
Prioritization by kartiq
Requirements Prioritization by kartiq
Why prioritize? by dwright
Priorities and Natural Build Cycle by kmatthews
You Rarely Need to Comprimize Business Priorities by ScottWAmbler
Agree on Rarely Need to Compromise .... by kmatthews
Different Topic: Agile and Maintenance by dwright
Stakeholders, Not BAs, Should Prioritize Requirements by ScottWAmbler
Prioritization and gathering by Ranjit
