stark
Adaptive Sprints

Keep the sprint connected to what changed.

Review capacity and scope as work moves, with proposed adjustments that keep commitments visible.

Meridian · workspace
Adaptive Sprints
ACDFMC+1

Illustrative workspace · interactive demonstration

See capacity pressure

Surface overloaded weeks before adding more work.

ENG-284Linked context

Review the adjustment

Discuss moving a task or changing scope with the affected owner.

Review the range

Keep the original commitment

Compare the current plan with its earlier assumptions.

86Ready for reviewHuman approval
A practical workflow

Review the sprint when the assumptions change.

New scope, changed availability and unfinished prerequisites all deserve a visible planning conversation.

01

Inspect the current load

Use the capacity heatmap to inspect each person and week. Select a cell to view the fictional utilization and identify where the plan needs a closer look.

02

Explain the pressure

Check whether the change comes from added work, reduced availability or a dependency. The same capacity number can describe different situations and require a different response.

03

Review an adjustment

Discuss moving or reducing work with the affected owner. Compare the updated plan with the original commitment so the change remains understandable in the next status review.

A connected working example

Bring the capacity question into the schedule.

The Meridian example shows capacity across eight people and ten weeks. It gives a planning discussion a concrete place to start without claiming that utilization alone predicts delivery.

A proposed schedule should preserve dependency ordering and explain what moves. Review alternatives with the team before changing a sprint, especially when a move affects another project or release.

Meridian · workspace
Meridian · connected view
ACDFMC+1

Illustrative workspace · interactive demonstration

Inside the approach

How the model works.

Suggested changes respond to recorded progress, capacity and dependencies. The demonstration uses seeded utilization data. A suggested move never proves that an actual team can complete more work.

Methodology and evaluation
Before you move forward

Keep the plan and the commitment connected.

ReviewWhat to look for
BaselineRetain the scope and availability assumptions behind the current sprint.
PressureInspect overloaded periods and distinguish additional work from a change in availability.
ProposalCheck which tasks move, who is affected and whether dependencies still hold.
AgreementReview the adjustment with the responsible people before presenting a new commitment.
Questions & answers

A few useful answers.

Is an overloaded cell a performance judgment?

No. Utilization describes recorded planning load against available capacity. It does not measure a person’s value or prove how quickly they can complete the work.

What can I inspect in the example?

Tap or hover a capacity cell to view the person, week and seeded utilization. Select another cell to compare periods.

Does the demo move real tasks?

No. The capacity and sprint examples use fictional records. Actual adjustments need the workspace’s permissions and a reviewed planning decision.

Ship what you promised.

Bring the plan, the work and the next decision together.