Prioritise Requirements
Prioritisation of requirements ensures that analysis and implementation efforts focus on the most critical requirements.
prioritisation of Requirements is used as a decision process to determine what should be further analysed and what should be implemented first.
1. Ensure you have the required Inputs
each project (or business analysis domain) will have specific information and documentation a Business Analyst needs to effectively Prioritise the Requirements. To effectivly prioritise requirements you will need to understand the Inputs for prioritising requirements
- Business Case
- Business Need
- Requirements
- Requirement management plan
- Stakeholder List, Roles, and Responsibilities
2. Decide how you are going to prioritise the requirements
There are many different Basis for prioritisation. In other words there are many ways a Business Analyst might decide to approach different requirements. These different approaches will change for each project or organisation. As with all things, some are better than others.
Making this decision early will make the rest of the analysis much smoother.
3. Understand the challenges you may face in prioritising requirements
- Non-negotiable demands
- unrealistic tradeoffs
4. Acknowledge the techniques you’ll need to Prioritise requirements
There are many techniques used by business analysts. By having a broad understanding of the tasks and skills a Business Analyst needs you will better be able to achieve your goals.
Specific to prioritisation you will need to understand the Techniques used to prioritise requirements. These break down into;
- General Analysis
- MoSCoW Analysis
- Budgeting and schedule
- Voting and stakeholder buy in
5. Understand the IIBA Stakeholders you may have to deal with
- Domain SME
- Implementation SME
- Project manager
- Sponsor
5. Deliver Outputs
The outputs will be prioritised requirements. These can then be distributed to stakeholders.