What the executive and stakeholder management campaign trains
This campaign treats every stakeholder interaction as a trade across three dials, and it teaches you to make that trade visible in language the stakeholder already speaks, revenue, contract terms, board reporting, rather than in Scrum vocabulary they may not value. The opening lessons cover why stakeholders break frameworks that were designed around a cooperative, single-team assumption, then teach three ways to answer an executive interruption: refuse it, which is cheap for the team but expensive for your credibility, capitulate to it, which is cheap in the moment but expensive for the Sprint, or reframe it, buying time to size the real cost and returning with two honest options for the business to choose between.
The economics lesson gives you a concrete tool for that reframe: a four-number page showing the value of doing the new thing this Sprint, the value of doing it next Sprint, the cost of delaying the current Sprint Goal, and the rough cost of the context switch itself. Putting all four numbers in front of an executive at once usually makes the right answer obvious without anyone needing to win an argument. The first scenario, a C-suite interruption, puts this exact tool under real pressure.
A second thread covers fixed-scope, fixed-price contracts, environments where Agile delivery meets a legal document that assumes waterfall certainty. The module names the two most expensive mistakes here directly: silently cutting internal quality to hit a contractual date, and reflexively reopening the contract price the moment a discovery surprises the team. Its answer is scope buffering, reserving fifteen to twenty-five percent of contracted capacity at negotiation time as currency for late discoveries, while keeping the Definition of Done fixed no matter what. A scenario on the fixed-scope trap tests this directly.
The final third dismantles vanity metrics an executive might request, individual story points, hours logged, PRs merged, or any single-engineer number pulled from team artifacts, and replaces the reflex to simply refuse with a better move: show the executive what the requested metric would actually reveal, why it would backfire, and offer a dashboard built on DORA, flow, and OKR-style outcome metrics that answers the real underlying question instead. A scenario on redesigning an executive dashboard, a full playbook lesson, and a ten-question certification quiz close the module.
Mistakes teams make with this material
Reflexively protecting the Sprint by saying no to every request from above, without pricing the actual trade-off. This burns credibility fast and teaches executives to route around the Scrum Team instead of negotiating with it.
Skipping tests or review to hit a contractual date without telling anyone. This is the single most expensive mistake in fixed-scope work because the debt is invisible until it fails in production, usually after the contract has been signed off as complete.
Handing over Sprint artifacts split by individual engineer because an executive asked for it. This data gets gamed within a Sprint or two and damages the trust the team needs to report honestly.
Treating each new piece of information mid-contract as grounds to renegotiate price. Using the scope buffer instead, and reserving renegotiation for when the buffer is genuinely exhausted, preserves the relationship far longer.
Questions people ask
How do you push back on an executive without damaging the relationship?
Reframe rather than refuse. Buy a short amount of time, price the interruption honestly using real numbers for this Sprint, next Sprint, delay cost, and switch cost, then return with two workable options and let the executive choose. This respects their authority while protecting the Sprint Goal.
What is a scope buffer and how big should it be?
A scope buffer is capacity reserved at contract negotiation time, roughly fifteen to twenty-five percent of total contracted work, explicitly set aside to absorb late discoveries without cutting quality or renegotiating price every time. It is spent through a scheduled scope-swap conversation, not silently.
Why are individual velocity metrics dangerous to report upward?
Sprint artifacts are team artifacts, and splitting them by individual destroys their meaning while creating strong incentives to game the number. Once leadership starts comparing individual velocity, engineers optimize for the metric instead of for the Sprint Goal, and psychological safety around honest estimation collapses.
A question from this module's assessment
One sample question with the reasoning, so you can judge the level before you start. The rest of the assessment stays inside the module.
A VP interrupts mid-Sprint with an 'urgent' feature for a major deal. Strongest first move?
- Refuse in the room to protect the Sprint Goal
- Accept immediately to protect the deal
- Buy 15 minutes, size honestly with engineering, come back with two costed options
- Escalate to your own manager
The Product Owner's job is not to say no; it is to make the trade-off economics visible so the business can decide with real numbers.