'Value-Driven Delivery' is one of the highest-weighted domains on the exam. Can someone explain how we prioritize the backlog based on "Value" vs. "Risk"? I'm struggling with the concept of "Risk-Adjusted Backlogs" and how it affects the delivery of a Minimum Viable Product (MVP).
3 answers
Value-Driven Delivery means prioritizing work that delivers the most business value first. However, a "Risk-Adjusted Backlog" means you also prioritize high-risk items early—this is "Fail Fast." If a feature is high-value but also high-risk, you do it immediately to prove the concept. If it fails, you haven't wasted the whole budget. For the exam, remember the "Value-Risk Matrix." You want to tackle High Value/High Risk items first, then High Value/Low Risk. This ensures the MVP is not just a set of easy features, but a viable core that has survived technical scrutiny.
Deborah, how does "MoSCoW" prioritization fit into this? Is it better for the MVP than just ranking things by a simple numerical value?
Value isn't just revenue; it can be knowledge gained or risk reduced. The exam looks for this broader definition when asking about prioritization.
Exactly! Sometimes a "Spike" (a research task) has the highest value because it prevents the team from going down the wrong technical path for months.
Richard, MoSCoW (Must have, Should have, Could have, Won't have) is excellent for the MVP because it forces stakeholders to categorize the "Must haves." However, for the PMI-ACP, you should also know "Relative Prioritization" and "Kano Analysis." MoSCoW is a great starting point, but the exam often asks about "Relative Weighting" where you compare features against each other to find the true priority. It's about having a conversation to reach a consensus on what "Value" actually means.