Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

Change Management

Last post 06:06 am August 20, 2015 by Jitesh Dineschandra
5 replies
12:02 pm August 8, 2015

How to manage requirement change in Sprint?

11:28 am August 10, 2015

Can you please be more specific?
Describe the situation you are in.
Is it only a detail or is the Sprint Goal affected?

01:07 am August 15, 2015

Want to understand that should we accept change during the sprint execution and how to deal it if any requirement change in story as SM?

08:46 am August 16, 2015

During the Sprint:
•No changes are made that would endanger the Sprint Goal;

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.

02:24 am August 18, 2015

This means: Yes we as SM can accept change as long as the Sprint Goal is not affected and the DT and PO agree on it.

06:06 am August 20, 2015

Whats your situation/context Sushil?

Does the team have a Definition of Ready in place which allows the team to express the required quality of the user stories and supporting documents before committing to a sprint goal?

This should help reduce this "change" behaviour, rework and back and forth communication during the sprint timebox and help the team commit to a clear and unambiguous sprint goal at sprint planning.