One of the fundamental goals of Agile was to prevent management from setting artificial expectations and "holding the engineering team hostage".

But yet agile teams frequently uses the term "sprints" to refer to iterations. So management asks everyone to sprint for two weeks, and then sprint again, and then sprint again. And pretty soon everyone wants to vomit.

I propose that we in the agile community should stop calling our iterations sprints, and instead call them milestones. Because businesses aren't mad 100 yard dashes, they are marathons. And the consistent, patient cadence of a marathon runner is a more appropriate analogy. As a extra benefit, the term milestone reinforces the concept that end the end of an iteration something should have been achieved.