What is NOT allowed during a Sprint?

Reducing quality standards during a Sprint is not allowed, as it compromises the integrity and effectiveness of the product being developed. Scrum emphasizes delivering a potentially shippable increment of high-quality work at the end of each Sprint. Maintaining high-quality standards is crucial for the team's credibility, customer satisfaction, and the long-term sustainability of the product. Lowering these standards can lead to technical debt and a degradation of the product's overall value.

In contrast, adjusting the scope based on new insights is permissible as the team learns more about the work and its requirements during the Sprint. It promotes responsiveness and adaptability, which are key principles of Scrum. Changing the Sprint Goal can be done if there’s a compelling reason, ensuring that the team stays aligned with the project's overall direction. Clarifying requirements is a normal part of the development process within a Sprint, as teams often need to refine their understanding to deliver the best possible outcome.