Sprint 14, Day 6: the €2M demo that is not on the backlog
Your team builds a B2B payments portal. It is an eight-person Scrum Team, two-week Sprints, and today is Day 6 of Sprint 14. The Sprint Goal is 'Guest checkout: a first-time buyer can pay without creating an account.' The Developers forecast 38 points and have finished 20. On Day 5 the VP of Sales told the CEO she has promised a €2M prospect a live demo on Day 10 - the last day of the Sprint. The prospect wants a branded payment page with their own logo, colours and a custom confirmation email. None of that is on the Product Backlog; it has never been refined; there are no acceptance criteria, and legal has not seen the copy. The VP asks you to 'move two developers onto it for three days; it is small.' The Tech Lead tells you switching now would leave the guest checkout half-integrated behind a feature flag, so nothing would be demonstrable either way.
1. Who has the authority to cancel Sprint 14, and what options do you actually have on Day 6?
Read the worked answer
Authority. Only the Product Owner can cancel a Sprint, and only when the Sprint Goal has become obsolete. Nothing here makes guest checkout obsolete - a new, smaller want has appeared next to it. Cancelling would also throw away 20 points of finished work and a half-integrated flow, so cancellation is the wrong tool.
Your real options:
- Protect the Sprint Goal. The Developers keep working; on Day 10 you demonstrate the guest checkout Increment and are explicit about what is Done and what is not. The demo's purpose is feedback, and a truthful half-flow plus a conversation is worth more than a staged fake.
- Negotiate scope with the Developers, not above them. The Sprint Backlog belongs to the Developers; you can propose removing a lower-value item to free capacity, but they decide. The branded page is a poor candidate anyway: no description, no acceptance criteria, no legal review - it is not a Sprint-sized item.
- Put it on the Product Backlog and order it. If it genuinely outranks everything, it starts on Day 11, one working day after the demo.
- Escalate the trade-off, not the task list. Tell the VP and CEO what the choice costs: either the guest checkout slips or the demo shows unrefined, legally unreviewed work.
Reasoning. The Sprint is a container of stability precisely so that short-term noise cannot continuously reorder work. Empiricism requires that what you show is what exists.
2. The VP says: 'You are the Product Owner - just tell the developers what to do.' How do you respond, and what do you do about the demo?
Read the worked answer
On the instruction. The Product Owner does not assign tasks or direct individuals. The Developers self-manage how they turn Product Backlog items into an Increment, and they own their Sprint Backlog. Your influence runs through three legitimate levers: the ordering of the Product Backlog, the Sprint Goal agreed at Sprint Planning, and negotiation with the Developers when something changes. Going around those levers buys you three days of work and costs you the team's self-management and your credibility.
'You are the PO' also does not mean unilateral authority to change a Sprint mid-flight - the PO can propose removing scope, but the Developers own the Sprint Backlog.
On the demo, in this order:
- Speak to the VP before Day 10, ideally with the account manager, and establish what the prospect will actually see.
- Offer something honest and useful: the working guest checkout flow in a staging environment, plus a 30-minute conversation with the prospect about their payment requirements. Prospects usually want confidence, not a logo.
- Convert the branded page into a proper Product Backlog item with a description and acceptance criteria, and start the legal review now so it is not a blocker later.
- Ask the product question: is a branded payment page a generalisable opportunity across your customer base, or a one-off? That answer - not the size of the deal - determines where it sits in the order.
Saying no to a VP is part of the job; the Scrum values call it courage, and the alternative is a team that learns to distrust its own Sprint Goal.
3. The CEO overrules you and insists the branded page is built this Sprint. What do you do, and what must stay visible?
Read the worked answer
Make the consequence explicit, then act cleanly.
- Do not run a Sprint with a dead Sprint Goal. If the work is redirected, the Sprint Goal is obsolete. As Product Owner, cancel the Sprint and re-plan with a new, coherent Sprint Goal for the remaining days - or let the Developers agree a revised goal. Silently continuing under the old goal destroys the only measure of success the team has.
- Record the waste. The 20 completed points and the half-integrated guest checkout return to the Product Backlog, re-estimated and re-ordered. The feature flag means no value is live. Write that down where the steering group can see it.
- Report truthfully in the Sprint Review. Show the branded page at whatever state it is, labelled as not meeting the Definition of Done (no legal review, no acceptance criteria agreed). Do not let 'demoed' become 'Done'.
- Adjust the forecast. Expect the next Sprint to absorb rework; velocity will dip and the roadmap slips. Say so now, not in three weeks.
Reasoning. A CEO can direct a company; a Product Owner cannot pretend the Sprint is healthy afterwards. Your accountability is for value and for effective Product Backlog management, and that includes making the cost of a top-down decision visible in writing. If the decision is genuinely strategic, it deserves a revised Product Goal and a re-ordered backlog - not a quiet exception that the team pays for.