Scrum Rule: No Additional Requirements Can Be Added to a Sprint!


The rules of Scrum are simple and complete, but it’s easy to stray from the plan that Scrum has so clearly laid out. Part of the role of a ScrumMaster is to teach and coach on Scrum – and make sure that the framework is being followed.  It’s simple but not easy. There is always the temptation to go back to old habits and make exceptions to the rules. 

A common challenge occurs when the Product Owner wants to add to the sprint. So we’ll start here with this rule of Scrum: Once a sprint begins, you cannot add requirements or stories to the backlog

This is a rule because in order for Scrum to work, we need to have our time boxes and our sprint backlog. The sprint backlog is the agreed upon amount of work to be completed in the sprint, in the form of specific requirements that have been estimated. The time box is the amount of time that we have agreed to the sprint – 2-4 weeks. 

Scrum makes it easy to react to changing business needs. At the beginning of each sprint the Product Owner requests that we work on the highest priorities first and in turn we deliver the most value up front. So what do you do when you are one week into a four week sprint and your Product Owner tells you she forgot to add a ticket regarding a critical piece of functionality? 

Well in order to follow Scrum, you tell her to put it in the backlog and she can prioritize this for the next sprint. Your product Owner may argue that it can’t wait, and that she would gladly trade two other tasks for this one task. It sounds tempting because not only do you want to appease your Product Owner, but you also see the value of this new requirement. But here’s the issue: the team has not even seen this new requirement, it’s not been estimated, it’s missing the critical exercise during the Sprint Planning meeting, where we can ask questions and make suggestions. Even adding the smallest ticket derails the team, the velocity shifts and since these rules are in place, the integrity of the process also diminishes. 

But what if this proposed new requirement MUST be done immediately? Then you stop the sprint and you address this new emergency; have a Sprint Planning meeting and start over! This means that the sprint you were working on is over and anything that was in that sprint returns to the Product Backlog. In most cases this won’t happen, the new requirement isn’t critical enough for the Product Owner to agree to stop the sprint, but it happens and this is the solution. 

I’m curious what other challenges the readers have faced with following Scrum instead of falling back into old habits. Please share in the comments section below!

This is the sixth in a series of posts about Scrum. For the first, please see The Three Elements Of Scrum.




2017-03-31T06:20:02+00:00 Categories: Agile, Project Management|

About the Author:

Elizabeth Raley joined CivicActions in 2010 as an Agile Project Manager and Quality Assurance guru and became Director of Professional Services in 2014. She excels at bringing balance, facilitating change, encouraging growth, and empowering people.

Elizabeth uses her Agile coaching and people skills to keep CivicActions’ team members present and productive, and her project management skills to help keep projects running transparently and smoothly. As the PM on a collaboration platform project for a large federal agency, she has led a team of 10+ engineers and user experience professionals through countless successful releases. Other projects that have benefited from Elizabeth’s enthusiasm and attention to quality include the Department of Defense, the City of Los Angeles, C2ES, Denver Public Library, EatFresh (San Francisco Human Services Agency), FosterClub, GlobalMDP Program (Columbia University), Netpop, and SACNAS.

Elizabeth is also on the steering committee of Agile Government Leadership (AGL), which is a community-powered network of agile professionals working to bring an iterative, user-focused approach to government project management. There she works with other members of the committee organizing and strategizing, creating course content and reaching out to other leaders in the agile community to participate and share their knowledge in order to propagate agile in government.

Prior to working at CivicActions, Elizabeth spent five years at the software company Casting Networks as Director of Project Management. There she helped form the PM and QA group along with introducing and implementing Agile methodologies.

Speaking about Agile is always of interest to Elizabeth and she has been fortunate enough to do so at the California Technology Forum 2016, FedScoop’s Lowering the Cost of Government w/ IT Summit 2016, Drupal GladCamp 2014, the Community Media Drupal Summit 2012, and Drupalcon Chicago 2011. She also moderates a monthly webinar, AGL Live.

Elizabeth earned her BFA at Wayne State University and is also a certified ScrumMaster. She lives in Los Angeles and spends her free time practicing yoga, reading the funnier side of the internet or hanging out with her favorite people: her family.


    What if it is last day of sprint and still some user stories are left and team is stuck with some issue.

    • Raheel Arif

      those remaining tasks will be added back to product backlog

  • It is a general tendency to ignore scrum rules, this article explains one of those instances where users commonly ignore the scrum rule by adding stories even after the sprint has begun