Study guide
9.4 Applying EBM in Product Decisions and Key Value Measures (KVMs)
Professional Scrum Product Owner II PSPO II
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview, Scrum Foundations & The Advanced PO Role
1.1 PSPO II Exam Format, Competencies, and Passing Standards 1.2 Empiricism and First Principles in Advanced Product Ownership 1.3 Scrum Values and Accountabilities in Product Decision Making 1.4 Events, Artifacts, and Commitments Through the PO Lens
2 Chapter 2: The Six Product Owner Stances and Anti-Patterns
2.1 The Preferred Product Owner Stances: Visionary, Collaborator, Customer Representative 2.2 The Preferred Product Owner Stances: Decision Maker, Experimenter, Influencer 2.3 Misunderstood Stances: The Clerk, Story Writer, Manager, and Project Manager 2.4 The SME, The Gatekeeper, and Developing Stance Versatility
3 Chapter 3: Product Vision, Strategy, and Business Modeling
3.1 Crafting an Inspiring, Actionable Product Vision 3.2 Business Model Canvas and Lean Canvas for Agile Products 3.3 Strategic Alignment and Competitive Differentiation 3.4 Evolving Product Strategy in Complex Markets
4 Chapter 4: Product Discovery, Hypothesis-Driven Development, and Experiments
4.1 Continuous Product Discovery and Customer Evidence 4.2 Opportunity Solution Trees and Opportunity Mapping 4.3 Hypothesis-Driven Product Development and Experiment Design 4.4 MVPs, Pretotyping, and Pivot vs. Persevere Decisions
5 Chapter 5: Product Goal, Sprint Goal Craftsmanship, and Outcome Alignment
5.1 The Product Goal: Commitment, Scope, and Evolution 5.2 Sprint Goal Craftsmanship and Coherence 5.3 Connecting Strategic Goals, OKRs, and Sprint Goals 5.4 Escaping the Feature Factory: Outcome vs. Output Mindset
6 Chapter 6: Value Definition, Cost of Delay, and Prioritization Techniques
6.1 Multidimensional Product Value 6.2 Cost of Delay and Weighted Shortest Job First (WSJF) 6.3 The Kano Model and Customer Satisfaction Dynamics 6.4 Value vs. Cost Prioritization and Anti-Patterns
7 Chapter 7: Empirical Forecasting, Release Planning, and Agile Contracting
7.1 Empirical Forecasting Using Throughput and Flow Metrics 7.2 Probabilistic Forecasting and Monte Carlo Simulation 7.3 Adaptive Release Planning and Outcome-Based Roadmaps 7.4 Agile Contracting and Collaborative Procurement
8 Chapter 8: Stakeholder Management, Collaboration, and Governance
8.1 Stakeholder Identification and the Mendelow Matrix 8.2 Handling Conflicting Stakeholder Demands and The 'Evidence-Based No' 8.3 The Product Owner as Single Source of Truth for the Backlog 8.4 The Sprint Review as Strategic Working Session
9 Chapter 9: Evidence-Based Management (EBM) and the Four KVAs
9.1 Evidence-Based Management (EBM) Overview and Goal Hierarchy 9.2 Market Value KVAs: Current Value (CV) and Unrealized Value (UV) 9.3 Organizational Capability KVAs: Time-to-Market (T2M) and Ability to Innovate (A2I) 9.4 Applying EBM in Product Decisions and Key Value Measures (KVMs)
10 Chapter 10: Organizational Design, Culture, and Team Topologies
10.1 Organizational Design for Product Agility and Value Streams 10.2 Team Topologies in Product Development 10.3 Fostering an Experimental Culture and Psychological Safety 10.4 Decentralized Decision-Making and Team Autonomy
11 Chapter 11: Scaling Product Ownership (Nexus, LeSS, and Multi-Team Scrum)
11.1 Core Scaling Principles: One Product, One Backlog, One PO 11.2 The Nexus Framework: The Product Owner's Role 11.3 Large-Scale Scrum (LeSS) and Multi-Team Backlog Refinement 11.4 Scaling Anti-Patterns: Component Teams, Proxy POs, and Bureaucracy
12 Chapter 12: Product Lifecycle Management and Agile Portfolio Planning
12.1 Product Lifecycle Stages and Value Strategies 12.2 Dynamic Agile Portfolio Planning and Resource Allocation 12.3 Real Options and Economic Decision-Making in Portfolios 12.4 Product Sunset, Decommissioning, and Sustaining Agility
9.4 Applying EBM in Product Decisions and Key Value Measures (KVMs)
Key Takeaways Explain This Topic AI
Designing balanced EBM dashboards requires synthesizing all four Key Value Areas (CV, UV, T2M, A2I) into a cohesive scorecard to prevent local optimization and eliminate the distortions of Goodhart's Law.
Goodhart's Law states that 'when a measure becomes a target, it ceases to be a good measure'; tracking vanity metrics like velocity, story points, or lines of code incentivizes gaming and disconnects teams from customer value.
Diagnostic synthesis across KVAs enables root-cause problem identification: for example, high UV combined with poor T2M requires fixing the delivery pipeline before adding feature scope, while high CV with low UV warrants a sustaining investment strategy.
EBM transforms traditional Scrum events: Product Backlog refinement becomes hypothesis formulation, Sprint Planning tests leading indicators, and the Sprint Review becomes an evidence-based working session inspecting live telemetry and KVM shifts.
Agile portfolio governance under EBM replaces rigid annual fixed-scope budgeting with dynamic, venture-capital-style milestone funding released in small tranches based on validated progress toward Intermediate Goals.
Last updated: September 2026
9.4 Applying EBM in Product Decisions and Key Value Measures (KVMs)
Quick Answer: Applying Evidence-Based Management in operational product leadership requires balancing all four Key Value Areas (KVAs) simultaneously: Current Value (CV), Unrealized Value (UV), Time-to-Market (T2M), and Ability to Innovate (A2I). Measuring a single KVA in isolation triggers Goodhart's Law ( "When a measure becomes a target, it ceases to be a good measure" ) and incentivizes damaging organizational gaming. An advanced Product Owner uses balanced EBM dashboards to diagnose systemic dysfunctions—such as recognizing that a product with High UV and Poor T2M needs delivery pipeline automation rather than more feature backlog items. EBM operationalizes agility by transforming the Sprint Review into an empirical working session where stakeholders inspect production telemetry and KVM shifts, and by replacing static annual project budgeting with venture-capital-style incremental funding tied to the fulfillment of Intermediate Goals.
Designing Balanced EBM Dashboards: Counteracting Goodhart's Law
One of the most dangerous traps in corporate performance management is the over-simplification of measurement. When leadership selects a single metric to drive behavior, the system inevitably optimizes for that metric at the expense of systemic health. This phenomenon is codified in Goodhart's Law :
- "When a measure becomes a target, it ceases to be a good measure."
- The Vanity Metric Trap vs. Empirical KVMs
Traditional organizations heavily track vanity metrics —statistics that make teams feel productive or look impressive in executive slide decks, but bear zero empirical correlation with customer value or financial viability: +----------------------------------------------------------------------+
- | Vanity Metrics vs. Empirical KVMs |
- +----------------------------------------------------------------------+
- | VANITY METRICS (Easy to Game) | EMPIRICAL KVMs (Drive Value) |
- | - Story Point Velocity | - Customer Satisfaction (CSAT) |
- | - Lines of Code Written | - Customer Cycle Time |
- | - Number of Features Shipped | - Innovation Rate (% on new val) |
- | - Registered Accounts (Dormant) | - Active User Retention / Churn |
- | - On-Time Milestone Adherence | - Technical Debt Ratio |
- +----------------------------------------------------------------------+
If leadership incentivizes Developers based on Velocity (story points delivered) , what happens? Developers effortlessly game the system: a 3-point user story becomes an 8-point story. Story point velocity doubles, management celebrates, and absolutely zero additional customer value is delivered. If leadership demands Feature Volume , teams cut corners on automated testing and refactoring, causing defect density to skyrocket and destroying Ability to Innovate.
The Principle of Balanced KVA Tension
To prevent gaming and sub-optimization, an advanced Product Owner constructs a Balanced EBM Dashboard that maintains dynamic tension across all four Key Value Areas: +----------------------------------------------------------------------+
- | The Balanced 4-KVA Dashboard |
- +----------------------------------------------------------------------+
- | CURRENT VALUE (CV) | UNREALIZED VALUE (UV) |
- | - Customer Satisfaction: 88| - Market Share Gap: 42% |
- | - Customer Churn: 2.1% | - Customer Satisfaction Gap: 35% |
- | - Employee Happiness: 8.2 | - Addressable Market Size: $450M |
- | ---------------------------+--------------------------------------- |
- | TIME-TO-MARKET (T2M) | ABILITY TO INNOVATE (A2I) |
- | - Customer Cycle Time: 6 d | - Innovation Rate: 72% |
- | - Release Frequency: Daily | - Technical Debt Ratio: 14% |
- | - MTTR: 28 minutes | - Installed Version Index: 1.0 |
- +----------------------------------------------------------------------+
By monitoring all four quadrants concurrently, any imbalance is immediately visible:
If T2M improves (faster releases) but CV drops (customer dissatisfaction rises) and A2I drops (defect count explodes), the team is cutting quality corners.
If CV is exceptional but UV is stagnant and A2I is collapsing, the product is an aging cash cow being drained without reinvestment.
Diagnostic Framework: Cross-KVA Scenario Analysis
On the PSPO II assessment, candidates are presented with complex organizational diagnostic profiles. An advanced Product Owner must synthesize signals across all four KVAs to determine the correct strategic prescription:
Diagnostic Archetype KVA Profile Root-Cause Diagnosis Product Owner Strategic Prescription
1. The Constipated Pipeline UV: High; CV: Low; T2M: Poor (Slow); A2I: Moderate Large untapped market demand exists, but the organization takes 6+ months to deliver releases. Feedback loops are too slow to discover what users want. Freeze new feature scope. Allocate upcoming Sprints to CI/CD automation, trunk-based development, and reducing batch sizes to accelerate T2M before scaling features.
2. The Maintenance Quagmire UV: High; CV: Moderate; T2M: Poor (Slow); A2I: Very Low Massive technical debt, regression defects, and manual testing consume 80% of capacity, paralyzing delivery speed and blocking new value. Aggressively invest in A2I. Dedicate 40%+ of backlog capacity to automated testing, refactoring, and paying down debt to liberate developer capacity.
3. Efficient Irrelevance UV: Low; CV: Low; T2M: Elite (Fast); A2I: High The team has world-class DevOps pipelines, daily releases, and clean code, but nobody uses or wants the product. Halt development. Do not build more features. Conduct deep customer discovery to find a real problem, pivot the Product Goal, or sunset the product.
4. The Golden Cash Cow UV: Low; CV: High; T2M: Moderate; A2I: Moderate The product dominates a mature, saturated market. Customers are highly satisfied, and retention is strong, but growth headroom is exhausted. Sustain and harvest. Shift the product to lean sustaining maintenance. Reallocate development teams and budget to high-UV emerging products.
Operationalizing EBM Across Scrum Events and Governance
Evidence-Based Management is not an abstract executive reporting tool; it directly reshapes how a Scrum Team operates every day:
1. Product Backlog Refinement: Hypothesis Formulation
Rather than refining items as static requirements specifications, the Product Owner and Developers frame Backlog Items and Epics as falsifiable value hypotheses anchored to specific KVMs:
" We believe that introducing an automated batch PDF export for invoices (Output) will result in enterprise accountants spending 80% less time on manual billing (Outcome), which will increase our enterprise CSAT from 72 to 85 and reduce churn by 1.5% (Current Value Impact). We will confirm this when live telemetry shows that at least 60% of corporate accounts use batch export weekly within 30 days of release."
2. The Sprint Review: From Feature Demo to Evidence Inspection
In traditional organizations, the Sprint Review deteriorates into a passive, one-way PowerPoint presentation or "acceptance demo" where stakeholders judge whether Developers followed instructions.
In an EBM-driven organization, the Sprint Review is an empirical working session :
The Scrum Team and stakeholders inspect real customer telemetry and changes in KVMs resulting from previously deployed Increments.
They evaluate: Did our last experiment achieve the hypothesized outcome?
They inspect shifts in the market, competitive actions, and updated budget forecasts.
Together, they adapt the Product Backlog and determine whether the active Product Goal should be continued, adapted, or abandoned.
3. Dynamic Venture-Capital Portfolio Budgeting
Traditional budgeting locks organizations into 12-month fixed-cost, fixed-scope annual cycles. This is catastrophic in complex product environments because it penalizes learning: teams must spend their allocated budget on obsolete plans rather than adapting to market realities.
EBM replaces annual budgeting with incremental venture-capital governance :
Products and Scrum Teams are not funded for a 12-month fixed scope.
Instead, leadership funds teams in small tranches (e.g., 3-month allocations) tied to achieving an Intermediate Goal (Product Goal) .
At the end of each tranche, leadership and the Product Owner inspect the empirical KVM evidence. If the team demonstrates validated progress toward closing a Customer Satisfaction Gap or Market Share Gap, the next tranche of funding is unlocked. If the hypothesis fails or market conditions change, funding is redirected to higher-UV opportunities without penalty.