No Estimates | Glossary

Definition

No Estimates (as as it’s known: #Noestimates) acts as a countermeasure to estimates-driven software development. It requires for the elimination of a procedure of estimates, so that the software development team can do better, more focused work, and with minimal interruptions. Overall it results in a better development cycle, increased efficiency and less waste.

Further Reading

  • “No Estimates: How To Measure Project Progress Without Estimating”(book), by Vasco Duarte.
  • For more on No Estimates, read here and here.

Sprint | Glossary

 

Definition

In product and software development, a sprint is a set time period during which specific work has to be completed and reviewed.

Each sprint begins with a planning meeting, where the product owner , and the development team agree upon the nature of work that is to be accomplished. The development team has the final call on determining how much work can realistically be accomplished during the sprint, and the product owner has the final say on the final criteria that is needed to be met for the work to be approved and accepted.

The duration of a sprint is determined by the scrum master. Traditionally, it lasts 30 days.

Further Reading