When I talk with fellow developers new to Scrum, I often hear a fundamental misunderstanding about Sprints. These colleagues  are normally used to Waterfall or RUP methodologies. As a consequence, they think of Sprints as very short repetitions of the following phases: requirements (planning meeting), design, implementation, test (sprint review as acceptance).

And this is completely wrong!

Let me tell you why.

Agile, Methodology scrum, Waterfall