The Scrum Master explains to Developers that changes, when they are the result of feedback provided by customers or stakeholders, are expected and beneficial. Is the Scrum Master right?

During the Retrospective, the Developers of a Scrum Team complain about the changes they have to make to the features they have already developed as a result of the Sprint Review meetings. The discussions of the Sprint Review cause about 35% of re-work and the code to be rewritten.

The Scrum Master explains to Developers that changes, when they are the result of feedback provided by customers or stakeholders, are expected and beneficial. Is the Scrum Master right?
A . NO
B. YES

View Answer

Answer: B

Explanation:

"Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage." In Agile we want continuous feedback to know if we are on the right track and producing the right outcome. Many times, some team members have the idea that everything could have been specified better from the beginning and avoid rework, but many times that is not possible, many products need a lot of discovery. Only when users interact with the working product can they better understand it and see what could be added or changed to better solve their problems and improve their bottom line. With Scrum, the team should acknowledge that rework will happen, and they should plan for it in a controlled manner. Redoing, reworking, refactoring is a necessary part of software development to avoid code becoming unusable, undesirable, and even un-maintainable over time. Stakeholder feedback is key to understanding the Product, its use, and maximizing its value. The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.

The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.