Product owner and the Sprint Backlog (yes Sprint Backlog)
Hi.
I'm not sure if this is a tricky question (or a typo) in a feedback I received about PO topic, but I think it may worth the discussion:
What is the PO role in managing the Sprint Backlog?
It is stated in the Scrum Guide that the PO is responsible of the Product Backlog and describe a list of tasks related to Product Backlog management. Therefore, there's nothing the PO does to manage the Sprint Backlog.
I think that he may be informed of decisions the Development team make about the Sprint Backlog if the Development team agrees to do so. Besides, the PO can always see these decisions in the Sprint Backlog itself due to transparency.
Am I missing any special situation where a PO has to be involved in managing the Sprint Backlog?
Thanks!
Taking a couple of quotes from the Scrum Guide
The Product Owner is the sole person responsible for managing the Product Backlog.
The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a "Done" Increment.
Only the Development Team can change its Sprint Backlog during a Sprint.
As you said, the Product Owner is responsible for the Product Backlog. As the statements above imply, the Development Team is responsible for the Sprint Backlog.
The Sprint is a timebox used to reach the Sprint Goal and create a potentially releasable increment of value. The Sprint Backlog illustrates the work that needs to be done in order to accomplish those goals. The Daily Scrum is used to manage the Sprint Backlog based on information that is discovered as work is done. Since the entire Scrum Team craft and agree to the Sprint Goal, the Product Owner and Scrum Master need to be included in discussions that impact to the ability to reach the Sprint Goal. These discussions could involve changes that are made to the Sprint Backlog. But only the Development Team modifies the Sprint Backlog.
So to summarize, the Product Owner is not involved in managing the Sprint Backlog. They are involved in the crafting of the Sprint Goal which influences the makeup of the Sprint Backlog. They are a stakeholder in achieving the Sprint Goal. So they are an interested party to how the Sprint Backlog is managed but they are not an active participant in that activity.
Awesome! Daniel, Thank you very much for the clarification and detailed response.
What would happen in a case that the DEVs are not able to reach the Sprint Goal?
This would be of interest to the whole Scrum Team.
What are the options for the PO, as the stakeholder for reaching the Sprint Goal in that case?
If during the Sprint it is discovered by the Developers that the Sprint Goal is in danger, the Developers should involve the entire Scrum Team in discussions about the situation. The Sprint Goal is created by the entire Scrum Team so they should all be involved in discussions when it is in danger.
Those discussions should focus on how to recover the ability to satisfy the Sprint Goal. The Developers are still responsible for the Sprint Backlog so they are the ones that will make adjustments based upon input from the Product Owner.
I want to point out these statements from the Scrum Guide about the Sprint Backlog (emphasis added by me)
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum.
The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog. As the Developers work during the Sprint, they keep the Sprint Goal in mind. If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.
Since the Sprint Backlog is owned by the Developers, they are the ones responsible for any modifications.
What would happen in a case that the DEVs are not able to reach the Sprint Goal?
This would be of interest to the whole Scrum Team.
What are the options for the PO, as the stakeholder for reaching the Sprint Goal in that case?
Firstly, work with the Developers on improving their options for meeting the Sprint Goal. The whole team has committed to its achievement.
If the Sprint Goal is obsolete and it is no longer appropriate for the Developers to even try to satisfy it, then the Product Owner may choose to cancel the Sprint and the team can replan to achieve something more worthwhile.