Skip to main content

Sprint Backlog

Last post 03:01 pm January 10, 2017 by Jayaram Hegde
8 replies
10:50 pm January 3, 2017

Hi

I am new to this forum and Agile Process. I have a doubt in Agile Practice which would like to ask. which is as below-

First of all Scrum product backlog is created by product owner then items are picked from that and moved to sprint backlog during sprint planning and then sprint start.
Id this a correct sequence?

Scrum Product Backlog---> Sprint Backlog---> Sprint Starts.................???????


and if some items are not completed in current sprint then those items are moved to Sprint Backlog again?

Thanks & Regards
Vivek Gupta


11:19 pm January 3, 2017

The Sprint starts just before Sprint Planning, which is the very first event to be held in the Sprint. You could however say that development starts immediately after Sprint Planning.

Items not completed during a Sprint ought to be re-estimated on the Product Backlog so that it accurately reflects the work that is believed to remain.


03:47 am January 4, 2017

It is worth mentioning that the Product Backlog doesn't have to be completely finished before starting a sprint. Product backlog is living document. Also, sprint backlog can also be changed during the sprint.


05:50 am January 4, 2017


If incomplete items goes back to Product Backlog then what is the role of sprint backlog?

When does sprint backlog comes in picture of Scrum cycle?


12:23 am January 5, 2017

> If incomplete items goes back to Product Backlog then what is the role of sprint backlog?
>
> When does sprint backlog comes in picture of Scrum cycle?

Based on your reading of the Scrum Guide, what do you think a Sprint Backlog is for?


11:19 pm January 8, 2017

As per my understanding, Sprint Backlog contains all tasks to be completed in the current Sprint.

If for any reason, story does complete in the spirint then it will move back to product backlog for reestimation/replanning.
And current sprint finishes.


06:33 am January 10, 2017

Do you think that the Sprint Goal might be related to the Sprint Backlog, and give it purpose?


02:50 pm January 10, 2017


During every sprint Development team pick the top items (priority items) from Product Backlog .

Sprint backlog is the refined Product Backlog item articulated by the Development team. During Sprint planning Sprint backlog is defined but it gets refined during the sprint.

Sprint backlog includes every single task which development team has to perform til the end of sprint. As and when requirements/ changes are understood Sprint backlog would be added with more engineering tasks (regression test scenario, database update etc.)

In short Sprint Backlog belongs to development team and they have the complete ownership of adding/removing tasks into it after negotiation with Product owner.


03:01 pm January 10, 2017

Sprint Backlog is the plan of development team for one complete sprint. It will have all engineering tasks refined to a day or hours (hours is the best measure).

Every day Development team inspects their progress towards sprint goal in Daily Scrum. During this team inspects & adapts the Sprint backlog (which is the plan of team). So everyday Sprint backlog gets modified.

During end of the sprint, Sprint review is held in which Development team demonstrate the product backlog items developed and gets the feedback from Stakeholders & Product owner. Depending on the feedback, Product backlog would be added with new items.

Unfinished items at the sprint review are re-estimated and added back to product backlog.


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.