It’s probably a little pedantic to argue about terminology used for a time-boxed process to deliver software, but hear me out.

For most teams following an Agile process, that time-box is called a Sprint. It’s meant to convey that the team “sprints” during a short period of time to solve story problems. By the end of the sprint, the team has not only delivered business value, but they are then ready to do it again, and again.

Where’s the problem? Would the term “iteration” generate as much visceral imagery? Does it convey an intended reality or motivate a team to…

Dan Shellman

Broad experience in software development, from testing to development to management. Passionate about improving how we build software.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store