Back to Forum

What Scrum Master should do if requirement changes after four sprints, which causes Rework on work done till date?

Last post 07:54 pm August 24, 2019 by Ian Mitchell
2 replies
SUMIT AGRAWAL
06:51 pm August 24, 2019
Thomas Owens
07:24 pm August 24, 2019

The Manifesto for Agile Software Development says:

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

If there are a new set of needs which may cause changes, it would be treated as anything else - placed into the Product Backlog, refined by the Product Owner and Development Team, and ordered by the Product Owner. The Development Team will work through the revised Product Backlog, delivering the changes, reviewing them with stakeholders at the Sprint Review, and working toward a product that is released by the Product Owner.

My concern is why requirements changes were so drastic so quickly. Was the Product Owner adequately understanding and translating stakeholder needs into Product Backlog Items? Were the stakeholders actively involved in reviewing the product and providing feedback at the Sprint Reviews? It seems highly suspect, but not impossible, that several Sprints of work would be entirely invalidated so suddenly. I'd want to understand why this happened and what can be done to prevent it in the future.

Ian Mitchell
07:54 pm August 24, 2019

What Scrum Master should do if requirement changes after four sprints, which causes Rework on work done till date?

Why did the team fail to inspect and adapt the product in the first three Sprints?

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.