Value-Based Delivery and Benefits Realization
MVP
First Delivery
Minimum Viable Product, early value
WSJF
Prioritize
Weighted Shortest Job First = Cost of Delay / Duration
4
MoSCoW Tiers
Must, Should, Could, Won't
not every feature delivers value the same way
The Kano Model
how to read this
- › Three kinds of features, three curves.
- › Must-haves · nobody notices when they work. Customers rage when they break. Ship them first.
- › Performance · more is always better. Linear reward for investment.
- › Delighters· small investment, disproportionate joy. But today's delighter is tomorrow's must-have.
WSJF · Weighted Shortest Job First
WSJF = Cost of Delay ÷ Duration
| Feature | Cost of Delay | Duration | WSJF | Rank |
|---|---|---|---|---|
| Checkout redesign | 20 | 2 | 10.0 | #1 |
| Legacy cleanup | 15 | 3 | 5.0 | #2 |
| Dark mode | 8 | 4 | 2.0 | #3 |
| Admin dashboard | 5 | 5 | 1.0 | #4 |
how to read this
- › Divide how painful a delay would be by how long the work takes.
- › Short jobs with big payoff float to the top. Long jobs with small payoff sink.
- › This beats gut-feel prioritization and is the default in SAFe release planning.
MoSCoW · Four Buckets
Must
required
Release-blocking
Should
painful to skip
Important, not blocking
Could
bonus
Nice if time allows
Won't
deferred
Not this release
Exam Traps
Value delivery beats scope adherence
PMI cares more about delivering value than rigidly hitting scope. If the business case changes, the scope should change too.
Benefits realization extends past closing
Benefits are measured after the project closes. The PM supports the benefits realization plan but is not always accountable for long-term outcomes.
Must-have does not mean critical
In MoSCoW, Must-have means required for the release to succeed. If it is not release-blocking, it belongs in Should or Could.
WSJF favors small, high-impact work
Short jobs with high cost of delay rise to the top. Long jobs with vague value fall down the list.
Value over variance
A project that finishes on time, on budget, but delivers no business value is still a failure. Value is the scorecard.
Do not confuse features and value
Shipping more features does not equal more value. The Kano model separates must-haves from delighters.
One cheese pizza everyone will eat. That is the MVP. It solves the core problem — hunger — right away.
The pepperoni pizza is a Must-Should for half the group. Order it next. Waiting longer costs you happy customers.
Fancy pineapple pizza is a nice-to-have for one person. It goes in Won't unless you have extra time and budget.
The goal is a full, happy group — not the highest pizza count. Value is satisfaction, not volume.
Ready to test your PMP knowledge?
1,800 practice questions written by certified professionals.
Start Practicing PMP