Plan a project so the plan can change

Two-week reporting cycles do not make your project agile.

Move from executing a fixed upfront list to planning around what you learn along the way.

Does this sound familiar?

The project has a complete backlog and everyone is expected to execute it from start to finish. Sprint endings check whether the team is on schedule. New findings become change requests to keep out.

The plan is protected from learning. Iterations cannot help you adapt when all meaningful decisions have already been made and cannot be revisited.

What we will work on

Recognise fixed-plan execution disguised as iterations.
Connect each iteration to the assumptions and opportunities that matter next.
Use findings to keep, change, remove or investigate planned work.
Make the effect of adaptation on commitments explicit with the people who control them.

For product owners, project leaders and Scrum Masters working inside fixed scope and upfront commitments.

Start with the free guide

Why Sprint Goals don't work for your team helps you name the underlying problem and take a first practical step.

Get the guide →