Sprint Commitment Discipline: Locked Sprints, Reopened Weekly
The account below comes from a change programme we ran in one of the largest business units belonging to a global research and advisory firm. Nine product and technology teams operated there, responsible for hundreds of millions of dollars in annual sales and a mandate to double it. We anchored the programme in evidence by scoring twenty-five dimensions across the organisation, with a qualitative pass alongside to capture what the scores would not.
The analysis started with the map.
Start with the map
Correlation, not causation: every edge is a measured statistical association (p<0.05) from this engagement, not an asserted cause. Edges below |r|=0.35 are omitted for legibility; the rest are drawn thicker and more opaque the stronger they are. The map stays focused on Portfolio agility: hover any dimension to preview its own connections against it, and use the strength slider to keep only its strongest links.
The map opens centred on portfolio agility: the organisation’s ability to change direction. Its strongest neighbour is not a strategy dimension. It’s product intake, the front door where work enters. That edge is the whole argument of this page: an organisation can only change direction as cleanly as it takes in work. When the front door has no ordering, every change of direction arrives as a raid on someone’s committed sprint.
What the numbers said
A median of 8 out of 10, and the tightest of clusters: of sixty-one respondents, only four scored it at 4 or below. The organisation believes it can change direction. The words say it changes direction constantly, and that this is the problem.
What the words said
The two dark blobs not lining up is the chart.
Mentions here number seven, six of them sore, and they describe a paradox. Rigid where it should flex:
“Little room for being flexible to make big strategic changes because we’ve made significant investments in specific business strategies, so we have to see it thru.”
“Not as responsive as we should be, stage gated process, requirements, design, approval, and scheduling process. It is not easy to be responsive.”
And fluid exactly where it should hold:
“Business tries to lock down a week before the sprint start, but often make changes to the locked sprints to the last minute for urgent priorities.”
“Sometimes priorities change while we are in the middle of something, having to context switch.”
“Scope creep is difficult to manage and creates the perception that things don’t get delivered on time.”
The worst of both settings: the big strategic bets were locked in, and the two-week commitments were not. Both are the same missing capability, an orderly way to accept new work and re-sequence the old, seen from opposite ends.
Where it lived
Nine teams, anonymised, best to worst. Thin rows render wider and flatter; less data looks uncertain, not falsely precise.
Within a couple of points of one another, the nine team medians run from 8 down to 6, one of the flattest spreads in this assessment. No team stands out because the churn isn’t a team’s property: it’s ambient. Everyone’s sprint is equally reopenable.
What agility turned out to be entangled with
The measured neighbourhood:
- Product intake (r = .63), the strongest pull
- Testable requirements (r = .59)
- Portfolio vision and strategy (r = .56)
The neighbour thread runs through prioritization, one of the assessment’s most-mentioned dimensions (seventeen coded mentions of its own), where the churn’s cost is written down plainly:
“Our team has too many things to focus on.”
“Team has 4 areas of focus, need to zero in on one area of focus.”
“Large backlog that we don’t have opportunity to work on, keeps growing.”
This client’s intake case study traces the same mechanism from the front door: no owner to sequence what enters. This page is what that absence does downstream, to sprints already committed. It is a coherent account of agility tracking intake rather than strategic will. The reading stops at correlation and claims no cause.
What happened next
The counter-evidence in the same dataset is precise about what kind of agility this organisation already had:
“I observed that our ability to react to unforeseen events is high. Teams are able to react quickly and resolve incidents effectively.”
Reactive agility was real: when the turn was small, shared, and urgent, the organisation turned. What it lacked was a mechanism for the deliberate turns, and its leaders knew which one was coming:
“A lot of our marketing strategy is using SEO and the SERP. AI / Chat GPT has disrupted this, how do we keep up with this.”
The check that travels: count the items in your current sprint that weren’t there at sprint start. Then ask what was re-sequenced out to make room, and who signed that trade. Churn with a ledger is recalibration. Churn without one is just noise wearing urgency’s clothes.
A note on the data
A real engagement; an unnamed client, and it stays that way. Team names and identifying details are removed, and quotes are lightly edited for anonymity. This page’s charts and figures are rebuilt straight from the underlying assessment data with every run, drawing on almost 2,000 qualitative and quantitative data points together, with nothing simply asserted. One organisation, correlations not causes.
Read Next
- WSJF: recurring recalibration at PI boundaries
Re-scoring on a cadence is the orderly version of what this client did chaotically: churn with a ledger is recalibration.
- Portfolio Kanban: the states an epic moves through, Funnel to Done
An explicit intake state-machine is the mechanism that lets an organisation change direction without reopening committed work.