Back to Forum

Change Management

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

How to manage requirement change in Sprint?

Ludwig Harsch
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?
etc

Sushil Agarwal
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?

Ching-Pei Li
08:46 am August 16, 2015

http://scrumguides.org/scrum-guide.html#events-sprint

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.

Ludwig Harsch
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.

Jitesh Dineschandra
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.

Jitesh

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.