Can work be added during a sprint?
- You should never add work during a sprint
- If the Product Owner wants it then put it in
- As we understand the work we adjust our view of the work to reflect what it takes to do the job
- This is really a question of granularity. If the adjusted work is in small bits then yes, as the bits get larger we risk loosing rhythm and consistency.
- Our sprint plan should have nailed it. Changes during the sprint is a sign of sloppy planning.
Comment: Changes to work forms an interesting tension. At a fine grained detailed level it changes all the time. Each person’s individual to-dos often change to reflect their understanding of what it takes to get the job done. As the level of granularity increases to task then it is a change to the team’s plan. If the number of changes is significant and adds up to more than one story’s worth of work then you better stop and adjust your plan, usually you want the product owner in on that discussion. And if there are several new stories that were suddenly found and are so important they must be done right now, then call a stop and reset your entire sprint with a sprint planning session. Generally, the commitment by the team to the sprint should not change. Note: definition of team makes this an interesting discussion. Bottom Line: The goal here is to help the team get better at expressing work they can do and following through on a commitment.