- 1. Get all involved in a room to discuss each participant’s reasons for priorities so that they are all heard.
- Don’t try to prioritize all requirements in one sitting.
- Try to get numerical priority (especially for high priority items) instead of general high, medium, low categories.
- Buy A Feature (Assign a value to each feature and give stakeholders a fixed amount of fake cash that they may use to “purchase” the features they most desire.)
- First In, First Out
- Prioritize by considering Cost of Delay
- Company Drivers/Department Drivers – Know the priority of each driver and based on that, prioritize the requirements.
- MoSCoW approach – must have, should have, could have, won’t have
- Determine if multiple requirements are addressing the same problem to reduce potential duplicates or conflicting requirements first.
- Agree on a Ranking/Rating System and define the rank values (High, Medium, Low; What do they mean?)
- Refer to the project objectives to identify high priority requirements. If a requirement does not help achieve an objective determine whether the requirement is out of scope or an objective was missed.
- Determine high priority requirements by asking “If you could only have x items in your solution which would you choose?”
- Priority Pyramid – Force the group to determine the most important feature or requirement for the top box. Next select the next 2 most important items for row 2.
Continue expanding by one feature for each row until the pyramid is built. The top 2 or 3 rows would be the highest priority.
- Realize that priorities will change over time, even on short projects. Constantly revisit
priorities to ensure validity
https://requirementsinc.com/wp-content/uploads/2018/04/Prioritize.jpg 1067 1600 Sri https://requirementsinc.com/wp-content/uploads/2022/03/RInc-logo-Hi-Res-300x79-1.png Sri2018-04-04 23:54:402018-04-04 23:54:40The Art (or Science?) of Prioritizing Requirements Right