Priorization
Prioritization is necessary to differentiate requirements from each other (important and unimportant), as well as to bring order into a project and to ensure the project success. Depending on the project, ad-hoc-, analytical, and agile priorization techniques can be used. This page presents tools for the prioritization process, as well as prioritization results.
Priorization workshops
The following table lists the priorization workshop(s) for the functional requirements.
| Intention | Method | Participants | Date | |
|---|---|---|---|---|
 |
Basic features for a minimum viable product (MVP) | CAF (consider all facts) & PMI (Plus Minus Interesting) after top eight method | 19.08.2022 | |
|
Basic features for a minimum viable product (MVP) | kano model | 19.08.2022 |
Input for the prioritization process
Paper-printable functional requirements list
At this link, there is a PDF version of all functional requirements. This is optimized for printing out on DIN A4 (landscape) and can be used for prioritization in workshops.Most important goals (for CAF/PMI)
The following table can be used to select the criteria for the "Consider all facts / plus-minus-interesting" (CAF/PMI) method. These criteria are usually derived from the goals for the software system. Theses goals are plotted against the functional requirements. The most often referenced goals are furthest to the left. Major goals count double.