![]() Releases should include an evenly distributed mixture of stories from each stage in the usage sequence. We use the MoSCoW method: Must, Should, Could, and Won't Have.įor each stage of the usage sequence, identify “must-have” features. Together, these features create an MVP that allows users to progress through the entire usage sequence. For an online storefront, this might include “searching for a product,” “product page,” and “checkout screen.”Īdd necessity criteria. High-level descriptions of a user's requirements.ĭefine your usage sequence. Low-value, high-risk: Items that should be avoided.Ī story map is a matrix that organizes user stories: the X-axis is the chronological sequence of actions taken as users interact with your product the Y-axis shows how important each story is to the overall experience. Low-value, low-risk: Might be worth your time eventually, but should be prioritized below high-value features. Understand your team's risk tolerance and use careful judgment. The calculated priority will be used in Add Change and Edit Change screens. High-value, high-risk: May have greater product impact than high-value, low-risk items, but you risk wasting time on features you don't use. This matrix defines the priority of a change based on the category and impact. High-value, low-risk: Items that should be prioritized. Useful for addressing uncertainty about underlying assumptions: how long a feature might take to complete, how much it might cost, your team's ability to execute, or how much executive support a project might receive. Low-value, high-complexity: Items that should be prioritized. Revisit these features later and consider approaches to make them of higher value. ![]() Low-value, low-complexity: Might or might not be worth your time. If possible, break these down into less complex tasks. High-value, high-complexity: Larger strategic initiatives that require effort and time but pay enormous dividends. High-value, low-complexity: “Easy wins” that should be considered for your roadmap-but not at the expense of high-value, high-complexity features. Implementation “complexity” encompasses the time it takes to implement, the technical challenge, and development cost. Turn your feature backlog into an actionable matrix of prioritized initiatives using these three frameworks:īusiness “value” depends on strategic objectives: a feature's usefulness for customers, employees, or suppliers its ability to generate revenue, traffic, or publicity positive impact on product performance, security, and reliability.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |