Understanding and Apply Scrum [P6]: Sprint Goal - An introductory video series to scrum: sprint backlog and sprint goal

Question 1

Are we allowed to change to sprint backlog once the sprint begins?

Answer 1

Yes, we can change it so that it aligns more accurately with the sprint goal, the more we know about how we are going to achieve it

Question 2

Who is allowed to change the sprint backlog?

Answer 2

• Devs
• But, PO can attempt to influence the Devs to change the sprint backlog based on their observations (same goes with the reverse for the product backlog - Devs influencing the PO)

Question 3

What does the sprint goal help avoid?

Answer 3

Devs fragmenting into different initiatives - want them to work together

Question 4

What should the team do if the Sprint Goal is at risk of being met?

Answer 4

Reallocate effort

Question 5

Does everything in the sprint backlog need to meet the sprint goal?

Answer 5

Not everything that enters the sprint backlog needs to meet the sprint goal BUT sprint goal must be the biggest focus and priority!!!

Question 6

What is the rare case that the goal gets cancelled?

Answer 6

goal becomes obsolete (e.g. market shift) - at PO’s discretion can the goal be cancelled

Question 7

Who owns the sprint backlog?

Answer 7

Devs alone

Question 8

Who owns the sprint goal?

Answer 8

Devs alone

Question 9

Do the Developers commit to individual product backlog items?

Answer 9

No, they commit to the sprint goal.

They have limited knowledge at the beginning of the sprint so need to be flexible

Question 10

How many sprint goals per sprint?

Answer 10

1 sprint goal per sprint

focus and coherence and commit to the same goal posts