Back to Forum

Who defines the content of a Sprint

Last post 03:59 pm September 27, 2018 by Renan Duarte
3 replies
Jordi Rodriguez
11:48 am May 8, 2018

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

Joshua Render
12:57 am May 9, 2018

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.

 

Filip Łukaszewski
09:55 am May 9, 2018

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...

Renan Duarte
03:54 pm September 27, 2018

thanks a lot, solved my doubt

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.