Understanding and Apply Scrum [P5]: Scrum Artifacts - Myth 2: The sprint backlog can't change during the sprint

Question 1

In short, can the sprint backlog change during the sprint? Why?

Answer 1

Yes - a Sprint Backlog is flexible, as long as changes do not distract from the focus on the Sprint Goal.

While the Sprint Goal is set in stone, the Sprint Backlog is a forecast of the work needed to achieve the goal

Question 2

Is the sprint goal fixed?

Answer 2

Yes

Question 3

Is the sprint backlog fixed?

Answer 3

No

Question 4

Why is the sprint backlog flexible?

Answer 4

• can’t create a detailed plan for the future
• new insights or impediments emerge as the Dev Team works through the sprint backlog
• e.g. new technology they pick up doesn’t work out as expected or key feature that is needed to achieve goal is missing

Question 5

What does the dev team do if they need to change the sprint backlog?

Answer 5

re-negotiate with the PO

Question 6

What acts an opportunity to inspect and adapt their sprint backlog?

Answer 6

daily scrum

Question 7

In the context of the sprint backlog, why was the word “commitment” replaced by “forecast”?

Answer 7

want to highlight that unexpected issues and insights are likely to emerge during development

Question 8

What does the team commit themselves to?

Answer 8

• Fulfil the Sprint Goal;
• Delivering working, high-quality and usable software that meets the expectations of the customers and users;
• Working only on the Product Backlog items with the highest value;
• Focus on continuous improvement, learning, and technical excellence;
• Continuously inspect and adapt, by which empiricism is supported;
• Collaborate with all the business people involved;
• The values and elements that build the scrum framework

Question 9

What is the input and the output of a sprint?

Answer 9

• input - sprint backlog
• output - sprint goal

Question 10

What should we aim to do in relation to the input and out of a sprint?

Answer 10

reach our desired outcome (sprint goal) with the least amount of input (sprint backlog)

Question 11

What was we embrace when it comes to the sprint backlog? How?

Answer 11

• its emerging nature
• encourage Dev Team to change, modify and improve it during the sprint
• add new work to backlog as needed
• remove work that becomes unnecessary
• Dev Team is responsible for applying sprint backlog changes and inform PO if necessary