Scrum, day 54: sponsoring change

Today's objective: identify a concrete decision a sponsor can make to improve the conditions for a team, while preserving the team's ability to manage its work.

Read alongside: Software in 30 Days, chapter 4. Focus on your own authority and the conditions you could help change. Allow roughly five minutes for this companion, plus the book section.

Support becomes real when priorities collide

The fictional café owner announces support for the ShiftSwap pilot. A week later, another manager asks one of the Developers to leave the pilot temporarily for an unrelated report. The request is described as urgent, and nobody knows which commitment takes precedence.

The owner's earlier encouragement does not resolve the conflict. Sponsorship becomes practical through decisions about priorities, authority, availability, and constraints. Without those decisions, the team may be expected to succeed while the organization repeatedly removes the conditions it needs.

The sponsor does not need to direct the team's daily implementation. They need to make the surrounding commitments credible.

Clarify the priority and its limits

The owner explains why the pilot matters, what capacity has been committed, and how competing requests should be discussed. A genuine emergency may still require a change, but it should lead to an explicit trade-off rather than an invisible addition to the team's workload.

This protects transparency for everyone involved. The other manager can explain their need. Elena can explain the product consequence. The Developers can revise their forecast using actual availability.

The sponsor should also state the limits of the commitment. Protected focus is easier to use responsibly when people understand its purpose, duration, and review conditions. An undefined instruction that the pilot “comes first” can create unnecessary conflict with other important work.

Give product authority a usable shape

Elena is named Product Owner, but several managers continue to issue direct feature instructions to Developers. If the sponsor tolerates that pattern, the title provides little practical authority.

The sponsor can make the decision route clear: stakeholder needs should inform product decisions through Elena, with Developers contributing feasibility and uncertainty information. Disagreements can be discussed openly, but separate private commitments should not create competing backlogs.

This does not require Elena to work alone or ignore important stakeholders. It gives collaboration a coherent place to produce decisions and makes the resulting priorities visible.

Remove a constraint the team cannot remove

The pilot needs a dependable verification environment. The current arrangement requires repeated manual approval from a group with unrelated priorities. The team can improve its requests, but it cannot independently change the organization's allocation or access process.

The sponsor can bring the relevant decision-makers together, establish the product consequence, and authorize a bounded improvement that preserves necessary safeguards. The technical details remain with the people qualified to design and operate the solution.

This is a concrete service to the team. It changes a condition that affects delivery instead of asking the Developers to compensate indefinitely through extra effort.

Ask for evidence that supports decisions

The sponsor's questions influence what the team reports. Asking only whether every original feature is on schedule can encourage attention to plan compliance. Asking what users can now do, what the team learned, and what decision needs help encourages a more informative account.

The sponsor still needs to understand cost, forecast, and risk. Those concerns can be discussed alongside usable product evidence. The choice is not between financial responsibility and adaptation; the organization needs both.

When the team reports an uncomfortable discovery, the sponsor should respond consistently with the invitation to be transparent. Otherwise, people may learn that the stated interest in evidence applies only to favorable evidence.

Avoid turning sponsorship into task control

A sponsor who attends every Daily Scrum to assign work may undermine the autonomy the pilot is meant to develop. The Developers need to adapt their plan within clear boundaries, using their knowledge of the work.

The sponsor can inspect outcomes and address organizational decisions without choosing who implements each item. If they lack confidence in the team's decisions, they should discuss the specific concern and missing evidence rather than silently reclaim all control.

Clear accountabilities help distinguish useful involvement from interference. The sponsor can ask what decision requires their authority and allow the team to handle decisions that do not.

Make support survive the launch announcement

Early enthusiasm often produces temporary access to people and resources. The sponsor should inspect whether those conditions remain available once ordinary pressures return.

A short record of commitments can help: protected availability, a route for product decisions, an owner for the environment constraint, and a review point for the pilot's evidence. The record should remain small enough to use.

If the organization withdraws a condition, it should also revisit the expected result. Preserving the original expectation while quietly removing support creates a misleading judgment of the team's performance.

Choose one sponsorship action

Identify a recurring difficulty the team cannot resolve alone. Describe the decision within a sponsor's authority, the people affected, and the product consequence of leaving it unchanged.

Propose a specific action and a way to inspect its effect. Include what remains the team's decision so that support does not become unnecessary task management. If you are not the sponsor, prepare the evidence that would make the request understandable.

Reflection: which organizational promise currently depends on goodwill rather than an explicit decision? Making that promise concrete may help more than another statement of support.

Next, day 55 examines the everyday conditions behind the team label.