1. RICE Scoring
|the percentage of users or customers who will be affected by the feature, or initiative.
|an assessment of the potential value or benefit that the project or feature will bring to the users or the organization.
|The team's level of certainty in the Reach and Impact estimates.
|Effort quantifies the resources, time, and complexity required to implement the project or feature. It considers factors like development time, design work, testing, and any other resources needed. Effort is typically scored numerically, such as assigning a time estimate in hours or days.
2. MoSCoW Method
|User stories that are essential for the project's success.
|Important stories but not critical for the project's immediate success.
|Desirable stories, but not necessary
|Stories that will not be included in the current iteration.
3. Weighted Shortest Job First (WSJF)
|CoD (Cost of Delay)
|This represents the business value or impact that a particular user story or feature will deliver. It measures how much financial loss or opportunity gain would be associated with delaying the implementation of that item.
|CoR (Cost of the job in Progress)
|This factor accounts for the ongoing cost incurred while the job is in progress. It considers aspects such as the operational costs or maintenance expenses that the organization bears until the task is completed.
|This refers to the size or effort required to complete the user story or feature. It can be measured in various ways, such as story points in Agile development.
4. Kano Model
|Basic Needs (Must-Have)
|The essential features that customers expect as a minimum requirement ie Hygiene Features. Without these features, customer dissatisfaction is almost guaranteed. However, fulfilling these requirements typically does not lead to increased customer satisfaction.
|Performance Needs (Linear)
|Features that correlate directly with customer satisfaction. As the performance of these features improves, customer satisfaction increases. These features are often explicitly stated by customers.
|Excitement Needs (Delighters)
|unexpected or surprising features that have the potential to delight customers. When these features are present, they can significantly boost customer satisfaction, but their absence doesn't necessarily lead to dissatisfaction. Customers often do not express these desires because they haven't experienced them before. Differentiating Features
|Indifferent Needs (Neutral)
|The presence or absence of these features doesn't significantly affect overall satisfaction.
|Reverse Needs (Unwanted)
|When present, can lead to customer dissatisfaction.
5. Value vs Effort Matrix
Conclusion - what do I really use??
- MoSCoW flushes out the hygiene features.
- The time-cost of NOT having a feature is next most important
- Ongoing investment in the Linear Features (from the Kano Model) with due regard to continuously topping up investment in Differentiating Features.
- Use Ring Fence Development (on Page 3 of my Feature Prioritisation article) to make sure you have a reasonable balance between bug fixes, hygiene features, linear development and big innovation bets.
- Once a year, do a product portfolio analysis (using Feature Prioritization and Roadmapping technique) to benchmark all significant future projects against each other. For product enhancements that are requested after the annual review, measure them against a couple of existing projects that have already been benchmarked.