do NOT, under any circumstances start revising the foundation of the sprint
A Google Design sprint gone wrong (and what it taught me)

Solid advice, thanks for sharing, although I’d add one caveat.

Changing “it” is possible if the Product Owner really wants, but it comes at a high cost: The immediate end to the Sprint itself. Adopting this Agile/Scrum practice ensures there’s flexibility to react to unexpected events, but also makes it a significant enough burden to dissaude anyone from doing it often.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.