Add/Remove user story in current sprint

Last post 05:07 pm October 9, 2020
by Mohamed Lusiz
4 replies
Author
Messages
04:53 am October 8, 2020

Hi everyone body, as my understanding from the scrumguides for the Sprint Backlog, the Development Team could add more or remove unnecessary work. 

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

Beside that in the Sprint section(https://www.scrumguides.org/scrum-guide.html#events-sprint) it also include the idea: 

 Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned

My concern is we have planning to plan the capacity of development team to do, when we re-negotiated with Product Owner, it mean that we will see their capacity could do it or not. However, in the urgent case Product Owner would like to want the Development Team could add 1 more product backlog into sprint backlog to implement it (even though we out of the capacity). Will it conflict with planning when we forecast the capacity of the team? 

05:27 pm October 8, 2020

The key is the word re-negotiated.  If the Development Team feels that there is too much work remaining in the Sprint Backlog to take on an addtitional Product Backlog Items, they should negotiate to have something removed in order to accomodate the Product Owner's request. If they feel that the additional request can be accomodated without any other changes to the Sprint Backlog then it is just a decision on whether they want to take it on. 

To add a passage from the Scrum Guide section on the Sprint Backlog

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.

It is up to the Development Team to decide if they can take on more work.  

06:25 pm October 8, 2020

To put it another way, Scrum is a pull system, whereby the Development Team pulls work onto its Sprint Backlog, as opposed to having it pushed by the Product Owner or anyone else.

This enables proper inspection and adaptation; because it leaves the Development Team in a position to decline to take on extra work, particularly if it would put achieving the Sprint Goal at risk.

This situation is much more transparent, than having a Sprint Backlog which doesn't represent the forecast of the Development Team; and it may trigger further discussion within the Scrum Team about the best way forward (including potentially a renegotiation of the scope of the Sprint, or even the cancellation of the Sprint by the Product Owner).

 

 

07:33 pm October 8, 2020

However, in the urgent case Product Owner would like to want the Development Team could add 1 more product backlog into sprint backlog to implement it (even though we out of the capacity). Will it conflict with planning when we forecast the capacity of the team? 

What relation does that story have to the team's Sprint Goal commitment? Will it improve their chances of meeting the Goal, or put it at risk?

03:01 am October 9, 2020

What relation does that story have to the team's Sprint Goal commitment? Will it improve their chances of meeting the Goal, or put it at risk?

It was a bug and also related to the sprint goal, but we did not think it could be the case that we could add 1 more into current sprint because the capacity somehow can handle but we need to do other stuff such as testing and fixing the issue for the finish user stories.

To put it another way, Scrum is a pull system, whereby the Development Team pulls work onto its Sprint Backlog, as opposed to having it pushed by the Product Owner or anyone else.

This enables proper inspection and adaptation; because it leaves the Development Team in a position to decline to take on extra work, particularly if it would put achieving the Sprint Goal at risk.

Thank you for good input, the story still stick to the sprint goal, but it too late for implementation, because the development team estimate it takes 8 points to implement, beside that I think the scrum master and the team did not courage to much to decline the request from PO and we were convinced by PO... So that I need to improve and enhance to coach the team even it is a request from CEO.
Do you have any more input in this case? 
PS: Thank you everyone for your good input.