Evidence-Based Management (EBM)

Evidence-Based Management (EBM): A Comprehensive Guide for PSM II

Why Evidence-Based Management (EBM) Matters

In today's complex business environment, organizations often make decisions based on opinions, gut feelings, or vanity metrics rather than meaningful data. Evidence-Based Management (EBM) is a framework developed by Scrum.org that helps organizations measure, manage, and improve the value they derive from their product delivery efforts. For PSM II candidates, understanding EBM is critical because it directly connects the work of Scrum Masters to organizational agility and value delivery — moving beyond team-level facilitation into the domain of evolving the agile organization.

EBM matters because it provides a structured, empirical approach to making strategic decisions about product investments, organizational improvements, and agile transformations. Without evidence-based thinking, organizations risk investing in initiatives that feel productive but deliver little actual value. A Professional Scrum Master operating at the PSM II level must be able to guide leaders and stakeholders toward data-informed decisions rather than relying on subjective assessments of progress.

What is Evidence-Based Management (EBM)?

Evidence-Based Management is an empirical approach that helps organizations make better decisions by using intentional experimentation and structured measurement. It draws on the same empirical principles that underpin Scrum — transparency, inspection, and adaptation — but applies them at the organizational and strategic level rather than just the team level.

EBM is built around four Key Value Areas (KVAs) that represent different dimensions of value an organization can measure and optimize:

1. Current Value (CV)
This KVA measures the value that the product or service delivers to customers and stakeholders right now. It answers the question: How happy are users and stakeholders with what we currently deliver?

Example metrics include:
- Revenue per employee
- Customer satisfaction scores (e.g., Net Promoter Score)
- Employee satisfaction
- Product cost ratio (cost of maintaining vs. cost of new features)
- Customer usage index

2. Unrealized Value (UV)
This KVA represents the potential value that could be realized if the organization met the needs of all potential customers or users. It answers the question: How much more value could we deliver if we addressed unmet needs or untapped market segments?

Example metrics include:
- Market share
- Customer or user satisfaction gaps
- Desired customer experience vs. current experience

The relationship between Current Value and Unrealized Value helps organizations decide whether to invest in improving existing offerings or pursuing new opportunities.

3. Ability to Innovate (A2I)
This KVA measures the organization's capacity to deliver new capabilities that might better serve customer needs. It answers: How effective are we at delivering new value?

Example metrics include:
- Percentage of time spent on new features vs. fixing defects or managing technical debt
- Number of active product index items (feature count or complexity of the codebase)
- Innovation rate (ratio of effort on new capabilities vs. maintenance)
- Defect trends
- On-product index (installed version index — how many users are on the latest version)
- Technical debt metrics
- Production incident trends

A low Ability to Innovate often signals that the organization is burdened by technical debt, complex codebases, or organizational impediments that slow down delivery of new value.

4. Time to Market (T2M)
This KVA measures the organization's ability to quickly deliver new capabilities, services, or products. It answers: How fast can we deliver new value to customers?

Example metrics include:
- Release frequency
- Lead time (from idea to production)
- Cycle time
- Release stabilization period
- Mean time to repair (MTTR)
- Time to learn (time from forming a hypothesis to gathering enough data to evaluate it)

How EBM Works in Practice

EBM operates through an experimental loop that mirrors the empirical process at the heart of Scrum:

Step 1: Establish a Strategic Goal
The organization defines a meaningful, measurable strategic goal — something aspirational that represents a significant improvement in value delivery. This is analogous to a Product Goal but operates at a higher organizational level.

Step 2: Assess the Current State
Using the four Key Value Areas, the organization gathers baseline measurements. This creates transparency about where the organization currently stands.

Step 3: Identify Intermediate Goals
The organization defines smaller, achievable intermediate goals that represent steps toward the strategic goal. These are concrete, measurable targets.

Step 4: Run Experiments
Teams and leaders design and execute experiments — small, time-boxed initiatives intended to move toward intermediate goals. Each experiment has a clear hypothesis about what outcome is expected.

Step 5: Inspect and Adapt
After running experiments, the organization inspects the results against the KVA metrics. Did the experiment produce the expected outcome? What was learned? Based on evidence, the organization adapts its approach — continuing, pivoting, or stopping specific initiatives.

This loop repeats continuously, creating an ongoing cycle of improvement driven by evidence rather than opinion.

The Role of the Scrum Master in EBM

At the PSM II level, a Scrum Master is expected to serve the organization beyond just the Scrum Team. In the context of EBM, the Scrum Master can:

- Help leaders understand and adopt empirical thinking at the strategic level
- Facilitate discussions about which metrics are meaningful and which are vanity metrics
- Coach stakeholders on the importance of measuring outcomes (value delivered) rather than outputs (features shipped)
- Encourage the use of experimentation rather than big-batch, plan-driven approaches to organizational change
- Help teams and leaders connect their daily work to the Key Value Areas
- Advocate for reducing technical debt by making its impact visible through A2I metrics
- Support transparency by ensuring that KVA data is accessible and understood

Key Concepts to Remember for the PSM II Exam

- EBM is about measuring value and outcomes, not measuring team performance or individual productivity.
- The four KVAs are: Current Value, Unrealized Value, Ability to Innovate, and Time to Market.
- EBM is rooted in empiricism — the same foundation as Scrum.
- EBM uses an experimental loop: set goals, measure current state, hypothesize, experiment, inspect results, adapt.
- Strategic Goals are long-term aspirational targets; Intermediate Goals are stepping stones toward them.
- Metrics should focus on outcomes (Did customers get value?) rather than outputs (How many story points did we complete?).
- EBM helps organizations decide where to invest — e.g., if Current Value is high but Unrealized Value is also high, there may be significant market opportunities. If Ability to Innovate is low, the organization may need to invest in reducing technical debt before it can pursue those opportunities.
- EBM is not prescriptive about which specific metrics to use. Organizations should select metrics that are meaningful to their context.

Exam Tips: Answering Questions on Evidence-Based Management (EBM)

Tip 1: Focus on Value, Not Activity
When answering EBM-related questions, always lean toward answers that emphasize measuring value delivered to customers and stakeholders rather than tracking team activities like velocity, story points completed, or hours worked. EBM is fundamentally about value and outcomes.

Tip 2: Know Your Four KVAs Cold
Be able to quickly identify which KVA a given metric belongs to. For example, customer satisfaction relates to Current Value, release frequency relates to Time to Market, technical debt relates to Ability to Innovate, and market share gaps relate to Unrealized Value. Exam questions may describe a scenario and ask which KVA is most relevant.

Tip 3: Emphasize Empiricism and Experimentation
If a question presents a scenario where an organization is trying to improve, prefer answers that involve forming hypotheses, running small experiments, measuring results, and adapting — rather than implementing large-scale changes based on assumptions or best practices from other companies.

Tip 4: Watch for the Relationship Between KVAs
EBM questions may test your understanding of how the KVAs interact. For example, a low Ability to Innovate (high technical debt) will eventually degrade Time to Market, which in turn limits the organization's ability to capture Unrealized Value. Understanding these connections will help you select the best answer in scenario-based questions.

Tip 5: Distinguish Strategic Goals from Intermediate Goals
Strategic Goals are aspirational and long-term. Intermediate Goals are tactical, shorter-term, and measurable. If a question asks about setting direction for the organization, it is likely about a Strategic Goal. If it asks about near-term targets for an improvement experiment, it is about an Intermediate Goal.

Tip 6: The Scrum Master as a Catalyst for Organizational Improvement
PSM II questions may frame scenarios where the Scrum Master helps leadership adopt EBM thinking. The best answers will show the Scrum Master coaching, facilitating, and teaching — not dictating metrics, making strategic decisions, or acting as a project manager. The Scrum Master helps create conditions for evidence-based decision-making but does not own the decisions.

Tip 7: Avoid Vanity Metrics
If an answer option includes metrics like number of user stories completed, velocity trends across teams, or lines of code written, these are likely not the correct EBM answer. EBM favors metrics that directly connect to customer and business value — satisfaction, time to deliver, innovation capacity, and unrealized market potential.

Tip 8: Remember That EBM Is Not Prescriptive
EBM does not mandate a specific set of metrics for every organization. If a question implies that there is one correct set of metrics all organizations must use, that answer is likely wrong. EBM provides a framework for thinking about measurement, but the specific metrics chosen should be tailored to the organization's context and goals.

Tip 9: Connect EBM to the Scrum Values and Pillars
EBM reinforces transparency (making value data visible), inspection (regularly reviewing KVA metrics), and adaptation (changing course based on evidence). It also connects to the Scrum values of openness (being honest about what the data shows) and courage (making difficult decisions when evidence suggests a change in direction).

Tip 10: Practice Scenario-Based Thinking
PSM II questions on EBM are unlikely to be simple recall questions. They will present realistic organizational scenarios and ask you to apply EBM thinking. Practice by reading a scenario and asking yourself: Which KVA is most relevant here? What experiment would I suggest? What metric would help the organization understand its current situation? What would an empirical approach look like in this context?

By internalizing these concepts and practicing their application, you will be well-prepared to handle EBM questions on the PSM II exam and — more importantly — to help real organizations make better, evidence-informed decisions about their product and agile journey.