7.5 Stakeholders, Evidence, and Business Agility

Stakeholder Collaboration and the Sprint Review

Stakeholders are not a distraction from Scrum — they are integral to empiricism, supplying the external feedback that makes inspection and adaptation meaningful. The primary formal touchpoint between the Scrum Team and its stakeholders is the Sprint Review.

Quick Answer: The Sprint Review is a working session where the Scrum Team and key stakeholders inspect the outcome of the Sprint and adapt the Product Backlog together. It is collaborative, not a one-way demo. Evidence-Based Management (EBM) and business agility are supporting Scrum.org concepts, not Scrum Guide rules.

Hard Scrum Guide rules

• The Sprint Review is an event where the Scrum Team presents the results of its work to key stakeholders, and progress toward the Product Goal is discussed. The attendees collaborate on what to do next, and the Product Backlog may be adjusted to meet new opportunities.
• It is a working session — the Scrum Team should avoid limiting it to a presentation. The value of the event comes from the conversation and the adaptation it produces, not from a polished demo.
• It is the second-to-last event of the Sprint (the Sprint Retrospective is last) and is timeboxed to a maximum of four hours for a one-month Sprint, and proportionally shorter for shorter Sprints.

A Scrum Master coaches stakeholders to treat the Sprint Review as the place to give feedback and influence direction, which is also how you redirect stakeholders who try to reorder the Product Backlog outside the proper channel: the Product Owner remains accountable for the backlog, but the Sprint Review is where stakeholder input is gathered transparently.

Evidence-Based Management and the Four Key Value Areas

Evidence-Based Management (EBM) is a Scrum.org framework — not part of the Scrum Guide — for improving an organization's ability to deliver value under uncertainty by using evidence rather than opinion or seniority to guide decisions. The exam expects you to recognize EBM at a high level and, above all, to know that it is supporting material, not a Scrum Guide rule. EBM organizes measures into four Key Value Areas (KVAs):

A useful framing: CV and UV describe value itself (now versus potential), while T2M and A2I describe the organization's capability to deliver value (how fast, and how effectively it can innovate). EBM connects naturally to the outcomes-over-outputs idea from earlier — it measures value and capability, not volume of work produced.

Business Agility and Scaling — Without Overclaiming

Business agility is the organizational capability to sense change and respond quickly while continuing to deliver value. Scrum supports business agility, but the Scrum Guide does not define a "business agility" process — treat it as supporting context, not a tested rule.

The Scrum Guide states that its foundation is unchanging and that scaling is largely out of scope for the Guide itself. Professionally, and without overclaiming:

• Multiple Scrum Teams can work on one product, sharing one Product Owner, one Product Backlog, and one Product Goal — the single-product rules from 7.3 and 7.2 still hold.
• Nexus is a Scrum.org framework for scaling Scrum across teams on a single product; it adds an integration focus but does not replace Scrum.
• There is no single "official" mandated scaling model in the Scrum Guide, so reject any answer claiming the Guide requires Nexus (or any other framework). The most accurate exam answers describe scaling cautiously and keep the single Product Owner / Product Backlog / Product Goal intact.

Putting It Together: Evidence-Driven Stakeholder Conversations

The through-line of this whole focus area is that value is empirical: you cannot know how much value a product delivers by planning harder — you find out by delivering, inspecting outcomes with stakeholders, and adapting. The Sprint Review and EBM are two complementary lenses for that conversation. The Sprint Review is the mandated Scrum event where inspection-and-adaptation of the product happens with key stakeholders; EBM is the optional Scrum.org thinking tool that helps an organization frame what to measure when it has those conversations.

Common exam traps in this section

1. "The Sprint Review is a demo for sign-off." It is a working session to inspect outcomes and adapt the Product Backlog — there is no sign-off ceremony, and limiting it to a presentation is explicitly discouraged.
2. "EBM is part of the Scrum Guide." No. EBM is a separate Scrum.org framework. Any answer that mandates EBM "per the Scrum Guide" is wrong.
3. "The Scrum Guide mandates Nexus (or SAFe, or any model) for scaling." No. The Guide leaves scaling largely out of scope and mandates no model; the single Product Owner / Product Backlog / Product Goal rules still apply to one product.
4. "Stakeholders can reorder the backlog at the Sprint Review." They influence the Product Owner through feedback; the Product Owner still holds the ordering accountability.

Quick-reference: rule vs. supporting concept

If you can keep this table straight, you can answer most 7.5 questions correctly: choose the option that respects the Sprint Review's real character, keeps EBM and scaling frameworks clearly outside the Scrum Guide, and never overclaims.