Scrum framework clearly specifies that the scope of a Sprint cannot be changed once the Sprint begins. If the required change is so important that the result of the Sprint would be worthless without it, then the Sprint should be terminated. If not, then change is incorporated into a later Sprint. Saving Changes...
What this means is simply that once you have committed tasks to a Sprint and have started it, there can be no changes or addition of tasks. The Sprint has to run it's course with initially planned work and only after it is finished, you can plan again.
In an event that there is an immediate need to add tasks to the current Sprint or it would yield no value, you can terminate the Sprint early and plan a new one with additional tasks. Saving Changes...
thank for your answer, I confuse where I plan for the task after terminate Sprint. Do we need to start from Epic, User Stories or next Sprint. For example, the team is working on Sprint 2 during 6 Sprint. Saving Changes...
If the new task is going to add more business value and cannot wait till next Sprint, then only make a decision to stop the current Sprint. However, whatever work initiated/performed in your current sprint should be completed, tested and released before closing the sprint. Saving Changes...
