Definition of Sprint Backlog from Product Backlog
Hello,
I'm currently training for the PSM I Assessment and still have 2 questions left that I can't clarify with the Scrum Guide or Forum:
1) What are the definite criteria for the choice of Product Backlog Items that go into a Sprint Backlog during Sprint Planning and who is accountable (according to the Guide the Dev. Team is accountable for the number only)?
Imagine this virtual Product Backlog:
Order No. Descr. Estimate Value
1 abc 18 15
2 bcd 15 10
3 efg 5 7
4 ghi 10 9
...
The development team assumes to perform 20 'virtual estimate units' in the upcoming sprint.
Are they
a) forced to take items from top of the list until their capacity is reached (i.e. PBI no. 1 only, generating a value of 15)
b) forced to take items that create maximum value (i.e. no. 2 + 3 with a value of 17)
c) free to choose either PBI 1 or PBIs 2 + 3 or even a combination of lower prioritized PBIs?
2) I know only the Development Team members are mandatory at the Daily Scrum and the Scrum Master is optional if needed. But what about the Product Owner or even other Stakeholders? Are they allowed to attend?
Thank you very much in advance!
HI,
As per Scrum Guide page no 12: The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
Scrum Guide is a guide not a prescription on criteria for doing it (ex: value, user experience) and left it to product owner to make a decision based on its priority. Again it depends upon the nature and type of individual organization (product based,service based, banking, production industry etc.)
On the second question, noone forces to Dev team as to how much stories they think can delviery within the Sprint. The need to be self organized and should commit to stories they can deliver. PO would negotiate with them and question but cannot forced them to deliver more as long as Dev team can justify why they can't pick up more. With more and more sprints done and if the story points estimated, will give the team idea of their velocity and potential to delivery.
Sorry, on the second question, no PO and other stakehodlers should not attend that as it will just be hindrance to Dev team's work. Scrum Master should help to avoid this situation.
> ...according to the Guide the Dev. Team is accountable for the number only
No, the Guide says that only the Dev Team can decide the number of items selected. That isn't the same thing. The Guide also says:
"Only the Development Team can assess what it can accomplish over the upcoming Sprint."
Therefore no-one can force any work of any type onto the Dev Team at all. They must plan and affirm any forecast of the work they will do to meet the agreed Sprint Goal.
> But what about the Product Owner or even other Stakeholders? Are they
> allowed to attend?
Only Dev Team members may participate in the Daily Scrum. Others cannot attend if that would mean they were participating in some way, even if it was just by exerting some sort of influence.
Ian,
do you suggest that Product Owner's presence on Daily Scrum is already a participation, even though he is not allowed to speak?
Seems reasonable and at the same time would be pretty hard to measure and to prove that it's the case, imho, even when team would claim that 'it's ok'.
Ultimately it comes down to the Development Team. If they want a non-team member at their Scrum, then they are overriding a Scrum practice. This must be made clear. And if they insist "it's OK" to their Scrum Master when it really isn't, then there's a problem of openness and trust that needs solving first.
By "it's OK" I didn't mean the lack of trust. Rather lack of understanding that it changes the team dynamic like for example trying to please PO in some way.
To make it clear - you primarily coach your Scrum Teams to use Daily Scrum only for Development Team and Product Owner can't be present?
I coach that the Product Owner *shouldn't* be present if he or she isn't also a Dev Team member, because there is a strong possibility that this would amount to participation, however subtle.
Makes sense, thanks.