Scope & Value Management
Beyond MoSCoW: Applying the Kano Model to High-Stakes Requirement Prioritization
Eleanor Vance has spent 40 years managing enterprise software modernizations, medical data warehousing integrations, and distributed telehealth telemetry infrastructures. She acts as Principal Strategist at Apex Horizon Systems.
Features a kind, natural, professional female voice delivering a detailed executive summary of the project management principles discussed below.
When cross-functional software teams prioritize product backlogs, they frequently fall back on simplistic models like MoSCoW—categorizing items into Must-haves, Should-haves, Could-haves, and Won't-haves. However, under the intense operational stress of a major health-tech rollout, this linear scaling fails to capture dynamic human emotions. To truly insulate your baseline from scope inflation while ensuring user adoption, elite project managers utilize the Kano Model, pioneered by Dr. Noriaki Kano in 1984.
The Three Zones of the Kano Model
The Kano Model moves beyond simple priorities to categorize requirements based on how they affect customer satisfaction and product performance. It maps features across three main zones: Basic Needs (must-be attributes that cause extreme dissatisfaction if missing, but do not increase satisfaction if present), Performance Needs (linear elements where satisfaction is directly proportional to implementation quality), and Excitement Features (unexpected delighters that drive high delight but cause no penalty if absent).
On the PMP examination, situational questions in the scope and value domains test your ability to balance these feature dynamics under cost constraints. A common mistake for candidates is protecting "excitement features" while letting "basic needs" slip under pressure. For instance, if an automated patient record app includes an advanced AI visualization tool but fails to securely compile basic health insurance verification data, the system will face structural rejection by clinical operators.
"Satisfaction is not a linear metric. A project manager who cannot distinguish a basic expectation from a temporary excitement feature will spend their budget on delighters while their core architecture collapses."
Figure 21.1 — The Kano Model Satisfaction Matrix
Basic Needs
Non-negotiable entry stakes. Zero delight, high penalty if missing.
Performance Needs
Linear satisfaction relative to system speed and execution.
Excitement Features
True delighters. High delight if present, zero penalty if omitted.
1
2
3
Ultimately, professional certification measures your ability to align teams, protect boundaries, and manage changes systematically. By mastering these principles, you ensure high project quality and professional success.
Test Your Knowledge
Ready to go deeper on Focus on Value?
Use the Deep Mastery Drill to read this concept at expert depth, explain it back using the Feynman method, and defend your understanding against an AI Devil's Advocate.
Drill: Focus on Value