A Sprint Calendar


During the Sprint:

  • No changes are made that would endanger the sprint goal
  • Quality goals do not decrease
  • Scope may be clarified and re-negotiated between the product owner and development team as more is learned
Each sprint may be considered a project with no more than a one-month horizon. Like projects, sprints are used to accomplish something. Each sprint has a definition of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product.

Sprints are limited to one calendar month. When a sprint’s horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase. Sprints enable predictability by ensuring inspection and adaptation of progress toward a sprint goal at least every calendar month. Sprints also limit risk to one calendar month of cost.