Scrum Sprint

Correct Answer: Inform that changes will be considered for future Sprints, but the current Sprint should stay as initially planned

In Scrum, making major changes to the sprint that are already in progress is discouraged unless it becomes obsolete. The primary reason for this is to respect the commitments made by the Scrum Team at the start of the Sprint. Therefore, when stakeholders propose major changes during a Sprint Review, you should inform them that these changes will be considered for future Sprints. This would not disrupt the current work and would be in line with Scrum's principle of adaptation after a cycle of inspection The other answers are not the Scrum way of handling such a situation. Accepting changes right away would disturb the rhythm of the team as the scope would alter substantially. Ignoring stakeholders' requests is not a healthy practice as it defeats the principles of transparency and openness in Scrum. Lastly, cancelling the current Sprint to accommodate changes would only be considered if the Sprint Goal becomes obsolete, which is not the case with mere proposed changes to the product backlog.

Correct Answer: Clarify the requirement with the Product Owner and continue working without canceling the sprint.

When a Scrum Team realizes they have misunderstood a requirement, the best course of action is to clarify the requirement with the Product Owner and continue working, provided the Sprint Goal is not affected. Re-negotiating the scope may seem like a viable option, but it is not necessary unless the Sprint Goal cannot be met. Conducting an emergency Sprint Review or escalating to higher management are less appropriate actions, as they do not directly address the root cause of the misunderstanding nor leverage the collaborative nature of the Scrum Team and its Product Owner.

Correct Answer: Negotiate with the Product Owner regarding removing or modifying certain sprint backlog items.

According to Scrum principles, the core value is flexibility and continuous communication. When the team identifies that they are unable to complete the planned backlog items, the first course of action is to communicate with the Product Owner and renegotiate the scope of the sprint backlog. This includes possibly removing or modifying certain items. The option of increasing the number of working hours does not comply with Agile methodologies, as Agility promotes sustainable development and respect for team members' work-life balance. Carrying over unfinished items directly to the next sprint without discussing issues and adapting is also not aligned with Scrum's core values. Adding more team members in the middle of a sprint is not a recommended practice, especially since according to The Mythical Man-Month, adding manpower to a late software project makes it later.