Selection of the Product Backlog Items for the Sprint Backlog - In Detail
Hi all,
I just read some addtional info regarding the item selection of the development team from the product backlog for the next sprint.
I know that the sprint goal and the order of the product backlog by die PO is the guidance for the development team which items to take in their sprint backlog (in addition with the estimates). However in my source it is stated that no one can force the development team which items to take, the PO can just make suggestions.
In my opinion this could lead to some conflict between the PO and the dev team.
So Iam asking the ones who know the process in detail:
How exaclty is the selection of the product backlog items for the next sprint executed by the development team?
More specified: For example there is also the risk for the PO that the dev team does not take the items on the top of the (his) product backlog and therefore the delivered value of the increment could be at risk.
Thanks for you answers.
Development team uses priorities set by PO as guidance to plan the sprint. At the end it is development team who decides what they can work in a sprint.
If there is going to be conflict between the PO and DEV team on priorities then it is a good conflict. Both has to sit together, discuss and get on to same page. Reasonable people will come to an agreement after reasonable conversation.
But if the conflict doesn’t get resolved for various reasons like political then there is a bigger problem (organizational dysfunction) that has to be addressed.
In my opinion this could lead to some conflict between the PO and the dev team. (...) For example there is also the risk for the PO that the dev team does not take the items on the top of the (his) product backlog and therefore the delivered value of the increment could be at risk.
I agree with Raghuram's comment about conflict. Adding to that, a good PO will spend time with the Development Team during Backlog Refinement to ensure mutual understanding of PBIs, possible objectives for future sprints etc. If time is invested in this activity, then there would not be any major conflict during Sprint Planning, as the team would be already aligned on most things. If there are conflicting ideas during refinements, then there is still time to discuss and agree on a shared vision or solve it in other ways.
Agree with everyone above. The following is the entire section on Scrum Values from the Scrum Guide
Scrum Values
When the values of commitment, courage, focus, openness and respect are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone. The Scrum Team members learn and explore those values as they work with the Scrum events, roles and artifacts.
Successful use of Scrum depends on people becoming more proficient in living these five values. People personally commit to achieving the goals of the Scrum Team. The Scrum Team members have courage to do the right thing and work on tough problems. Everyone focuses on the work of the Sprint and the goals of the Scrum Team. The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work. Scrum Team members respect each other to be capable, independent people.
If those values are present in a Scrum Team, the act of ordering a Product Backlog should be extremely easy and conflict during Sprint Planning will be minimal.