Who defines the content of a Sprint
Hi all, just reading "The Scrum Guide" and I have this doubt:
- on page 7, about the Development Team: "The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. A “Done” increment is required at the Sprint Review. Only members of the Development Team create the Increment."
- on page 10, about the Sprint Planning: "The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team."
Who creates the content of one sprint, the DevTeam only, or the entire Scrum Team?
TIA for your help,
J
The development team has final say on what they can and cannot do within the Sprint. The development team needs to commit (It is a very formal way of having the development team state that they can do what has been selected for the Sprint)
However, they work together to try to figure out should be included. If you recall, the Product Backlog is arranged by the Product Owner, the development team is supposed to choose the higher priority/valued items for their Sprint Backlog. It is more of a how much can they do that they commit to.
Then you get down to changes during the Sprint, that is usually a negotiation between the Product Owner and the Development Team.
So to answer the questions - "Who creates the content of one sprint, the DevTeam only, or the entire Scrum Team?".... This plan is created by the collaborative work of the entire Scrum Team.
One problem I see here "Only members of the Development Team create the Increment." The Increment is the end result of the Sprint(s) and is not actually part of choosing what they do during the Sprint. They are two different things. One is what they are going to be working on, the other is what they have already worked on.
Just one comment Joshua, one could say teams nowadays only maybe "commit" to a sprint goal, but the work they plan to do during a sprint is just a forecast. "A very formal way of having the development team state that they can do what has been selected for the Sprint" is no longer in place, now it is "just" forecasting. People will approach the sprint goal with commitment, but still...
thanks a lot, solved my doubt