Sprint (Iteration)

They are fixed length events of one month or less to create consistency. A new Sprint starts immediately after the conclusion of the previous Sprint.

All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. The Sprint is a container for all other events.

When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase. Shorter Sprints can be employed to generate more learning cycles and limit risk of cost and effort to a smaller time frame.

During the Sprint:

• No changes are made that would endanger the Sprint Goal;
• Quality does not decrease;
• The Product Backlog is refined as needed; and,
• Scope may be clarified and renegotiated with the Product Owner as more is learned.

ProTip: Choose sprint 1 week length.

BestPractice: Start the sprint on Mondays and finish it on Fridays.

Common mistakes

Planning and all activities are part of the sprint. So, first you must to start the sprint, and after that continue with your activities. Another mistake is to delay the sprint end because you not complete it at 100%. Close the sprint, even if it is uncomplete.

https://www.agilealliance.org/glossary/iteration
https://scrumguides.org/scrum-guide.html#the-sprint