Change Requests During a Sprint

  • Pradyumn Sharma
  • August 22, 2017


You are working on an agile project with short sprints. In the middle of a sprint, the Product Owner, or some other end user, asks you for some new feature or change to an existing feature urgently. How do you deal with this situation?
Normally, one should convince the customer that it is not a good idea to change the scope of a sprint, once it has begun.
At the start of a sprint, during the Sprint Planning Meeting, the Product Owner would have explained the highest priority stories from the Product Backlog. The team would then have examined those stories in greater detail, estimated the effort involved, and then committed to a set of stories (the Selected Product Backlog).
Suddenly, in the middle of the sprint, if the requirements are to be changed, it disrupts the team’s momentum, and makes the process chaotic.
The Scrum Approach
The Scrum methodology strongly advocates against allowing such changes in the middle of a sprint. It recommends that we should ask the Product Owner to add those requirements as the highest priority stories to the Product Backlog, so that those can be taken up in the very next sprint. But until then, sorry, the customer has to wait.
In the extreme cases, if the Product Owner simply cannot afford to wait till the end of the next sprint to get the “urgent” requirements implemented, the current sprint can be “terminated”, a fresh Sprint Planning Meeting can be held with the changed priorities in the Product Backlog, and then a new sprint begins. Find more here about locksmith in dublin.
The Extreme Programming (XP) Approach
Sometimes, however, there may be a compelling reason for a customer to ask for some feature or change urgently, and terminating the entire sprint for that and starting afresh may appear to be an overkill. For example:

  • A statutory body (like a tax authority, or a compliance committee) may have demanded some information that needs to be submitted to them within the next couple of days, and the penalty for not submitting the same in time may be huge.
  • An internal audit or governance requirement, such as analysis of some fraud or non-compliance scenario that cannot wait until the end of the next sprint. Check out super cleaning service louisville.

Extreme Programming takes a more pragmatic approach to deal with such requirements. It suggests that it is okay, in such situations, to accommodate changes to the scope in the middle of an iteration, provided:

  • The team makes an estimate for the new requirement, and
  • The customer agrees to remove some other stories from the Selected Product Backlog that are not less than the estimated effort for the new story, and the team has not yet started working on those.

So, for example, if the new, urgent requirement is estimated to take 15 hours of effort, some other stories worth 15 or more hours of effort (that the team has not already begun working on) need to be taken off the Selected Product Backlog.
Having said that, such adjustments to the selected scope for a sprint should only be an exception, and not a norm.

25 responses to “Change Requests During a Sprint”

  1. john newmann says:

    N0sZyN Major thanks for the blog post.Really looking forward to read more. Keep writing.

  2. You obtained a really useful blog I ave been here reading for about an hour. I am a newbie as well as your achievement is really considerably an inspiration for me.

  3. Some truly prize blog posts on this internet site , bookmarked.

  4. Nice blog here! Also your website loads up very fast! What web host are you using? Can I get your affiliate link to your host? I wish my web site loaded up as quickly as yours lol

  5. Thanks-a-mundo for the article post.Thanks Again. Much obliged.

  6. there are actually many diverse operating systems but of course i ad nonetheless favor to utilize linux for stability,.

  7. Thanks so much for the article.Really looking forward to read more. Keep writing.

  8. you can also Nice blog here! after reading, i decide to buy a sleeping bag ASAP

  9. I think this is a real great article.Really thank you! Great.

  10. It as really a great and helpful piece of info. I am glad that you shared this helpful info with us. Please keep us up to date like this. Thanks for sharing.

  11. Thanks a lot for the blog article.Really thank you! Really Cool.

  12. name says:

    This very blog is obviously awesome and also factual. I have picked up a bunch of useful things out of it. I ad love to come back again soon. Thanks a bunch!

  13. I really liked your article post.Really looking forward to read more. Fantastic.

  14. Well I definitely enjoyed reading it. This post provided by you is very constructive for correct planning.

  15. Title here are some links to sites that we link to because we think they are worth visiting

  16. sex toys says:

    You can certainly see your enthusiasm in the paintings you write. The world hopes for more passionate writers like you who aren at afraid to mention how they believe. Always go after your heart.

  17. sex toys says:

    very nice post, very nice post, i certainly love this fabulous website, go on it

  18. lingerie says:

    Looking around I like to surf around the internet, regularly I will go to Stumble Upon and follow thru

  19. lingerie nyc says:

    Thanks-a-mundo for the article.Really thank you! Fantastic.

  20. nyc lingerie says:

    interest. If you have any suggestions, please let me know.

  21. nyc sex toys says:

    Really appreciate you sharing this blog post. Will read on

  22. It is actually difficult to acquire knowledgeable folks using this subject, but the truth is could be observed as did you know what you are referring to! Thanks

  23. Say, you got a nice blog post.Really looking forward to read more. Will read on

  24. Really appreciate you sharing this blog post.Really thank you! Much obliged.

  25. Dispensary says:

    Thanks so much for the blog post.Really thank you! Awesome.

Leave a Reply

Your email address will not be published. Required fields are marked *

© 2017 Pragati Software Pvt. Ltd. All Rights Reserved.