When creating custom software, it is critical to understand that software development is repetitive work. We call each  repetition, or Sprint of the process an “iteration”, and the end point of one iteration is the starting point for the next iteration. Product developers understand this repetitive aspect of software development and use it  to closely monitor, adjust and improve required features, interactive models and visual presentation style from one sprint to the next. This repetitive improvement is how sprints are used to gradually bring the value creating power of a product into focus.

Agile Software Development is done in “sprints”

A product developer leads this entire workflow, ensuring that the stories in the sprint backlog are specific and complete enough to be developed, and then determining exactly which items from the backlog to schedule for each weeks sprint. As each sprint is progressing the product developer reviews the completed stories, for acceptance or rejection. At the end of a  sprint, the product developer is able to review the working software with the appropriate stakeholders.