Skip to main content

During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?

Last post 04:41 pm May 29, 2020 by Ahmed ROMDHANI
8 replies
09:25 am July 22, 2013

Please help me with the following question:

During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?
A: As soon as possible after they are identified.
B: During the Daily Scrum after the Development Team approves them.
C: When the Product Owner identifies a new work.


10:03 am July 22, 2013

Not tending to something?

Who owns the sprint backlog in your opinion, and who is, considering this, allowed to change the content?

And from the timely perspective, when should communication about a new situation be started in your opinion?

BR,


11:54 am July 22, 2013

It can't be C, because the Product Owner is not in a position to add work to the Sprint Backlog. Only the Development Team can do that, because they wholly own that backlog. Once a PO identifies new work, he or she can add it to the Product Backlog and request that the Development Team estimate it. It can then be brought into a future Sprint Planning session.

B is a plausible answer. The Daily Scrum is an inspect/adapt opportunity and it can certainly lead to the team revising their Sprint Backlog. However, it is not the *only* opportunity for them to do so. The Development Team can and should update their Sprint Backlog on an ongoing basis.

Therefore the best answer is probably A, although for better clarity I think it should really say "As soon as possible after they are identified by the Development Team".


12:06 pm July 22, 2013

Thank you very much for your answers. This helped me much.

Greetings,
Mark


06:08 pm March 29, 2019

So, would as soon as possible after identification?


02:59 pm December 2, 2019

A: As soon as possible after they are identified.


11:00 am December 6, 2019

Eventually stories should't be introduced during the sprint (Hard Rule in Scrum). But to answer your question, B. Only team can decide/approves  


04:43 pm December 6, 2019

@Shiva Kumar Gosul, the following is the 4th paragraph of the Scrum Guide section where the Sprint Backlog is described (emphasis added by me). 

As new work is required, the Development Team adds it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnecessary, they are removed. Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team. 

Can you point me to somewhere that supports your "Hard Rule in Scrum"? 

Correct answer is A: As soon as possible after they are identified.


05:44 am May 29, 2020

First of all the responsible to make change on  the sprint Backlog is the develop team.

Second , develop team make a changes to the Backlog during the sprint  "Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less. The Development Team self-organizes to undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint."

Conclusion :  A: As soon as possible after they are identified.

 


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.