Skip to main content

How the Sprint Backlog Supports Adaptation (29)

July 27, 2023

Remember that Scrum is founded on empirical process control, and that adaptation is the third pillar, following transparency and inspection.

Each of the Scrum Artifacts is adapted in one or more Scrum Events in order to minimise deviations to acceptable limits which they have learned during inspection.


Adaptation is making adjustments in order to minimise any deviations to acceptable limits concerning agreed goals.


This also applies for the Sprint Backlog.


The Sprint Backlog is typically adapted during Sprint Planning and during the Daily Scrum. And given the Sprint Backlog is expected to provide a real-time picture of the work still needed to achieve the Sprint Goal, also throughout the day, every minute of every day as new insights become available the Sprint Backlog is kept up-to-date.


Each time new insights are gained about the progress towards the Sprint Goal, the Developers do make the necessary adaptations.

  • work that is finished, new work that is started,
  • work that is blocked,
  • additional work identified, or work no longer deemed necessary,
  • Product Backlog Items that are Done, or no longer needed, or additional ones that support the Sprint Goal,
  • releasing a new Increment during the Sprint itself,
  • a new hypothesis that needs to be checked to determine the next steps during the Sprint,
  • a risk being identified, or addressed and closed,
  • etc. etc. etc.


Adaptation are made in order minimise deviations to acceptable limits concerning agreed goals. For the Sprint Backlog this agreed goal is the Sprint Goal.



Once the Scrum Team together agreed the Sprint Goal, the Product Backlog items deemed necessary, and how this will be delivered in the Increment, the Developers adapt the Sprint Backlog to provide a real-time picture of the Sprint. 



Together with your Scrum Team, evaluate your Sprint Backlog:

  • When is your Sprint Backlog updated? Only shortly before the Daily Scrum or during it; or throughout the day?
  • How do you ensure the Sprint Backlog shows a real-time picture of the progress towards the Sprint Goal?
  • How is transparency provided at any given moment what the remaining work is for this Sprint? And how is it transparent what work is already finished - with the expected outcomes of it?


I hope you find value in these short posts and if you are looking for more clarifications, feel free to take contact.

If you want to take a deeper dive into the core concepts we are covering in this blog series, then surely check out our Professional Scrum MasterY workshop. We have some scheduled in the coming period.

Don't want to miss any of these blog posts? Have the professional Scrum foundations series weekly in your mailbox.


How does your Sprint Backlog support Adaptation?

What did you think about this post?