Value-Driven Delivery
Core Concepts
Value-driven delivery means prioritizing work that delivers the highest business value early and continuously. Candidates must understand techniques like MoSCoW prioritization, weighted shortest job first (WSJF), Kano analysis, and value stream mapping. Key artifacts include the product backlog, which should be ordered by value, and the definition of done, which ensures quality. Value is often measured through metrics such as return on investment (ROI), net present value (NPV), internal rate of return (IRR), and payback period. In Agile, value is delivered incrementally, and feedback loops ensure alignment with customer needs.
Traps
A frequent trap is choosing a prioritization technique that ignores dependencies or risk. For example, WSJF includes cost of delay and job size, while MoSCoW is simpler but less quantitative. Another trap is equating value with features delivered rather than outcomes achieved. Questions may ask how to handle a high-value item that is risky; the answer often involves spiking or prototyping to reduce uncertainty before committing. Also, beware of answers that prioritize low-hanging fruit over strategic value.
Worked Example
A product owner must choose between Feature A (high value, high effort) and Feature B (medium value, low effort). Using WSJF, calculate cost of delay divided by job size. If A has cost of delay 100 and size 20 (WSJF=5), and B has cost of delay 50 and size 5 (WSJF=10), B should be prioritized first. The exam answer would reflect this calculation.
Rule of Thumb
Prioritize by value and risk: high value, low risk first; high value, high risk next (with risk mitigation); low value last.