Sprints are the container for scrum events.
A month or less in length—usually two weeks. Sprints start back-to-back with one another. Planning defines what gets accomplished during it, retrospective terminates it. A sprint seeks to achieve the sprint goal and changes that affect the goal should be resisted. Scope should be negotiated with product owner if new information comes to light regarding scope. Product owner can cancel the sprint if the goal becomes obsolete. A sprint should be considered a small project. Sprints optimize for reassessing priorities and reducing the wasted value potential of work-in-progress work.