Skip to content
dvnt.io

Resources · glossary

Sprint

A closed stretch of work, usually two weeks long, at the end of which something working exists. Its length is fixed: the scope changes, not the deadline.

Also called
  • iteration
  • development cycle
  • Scrum sprint
  1. 01

    Why the length is fixed

    Because a steady rhythm gives you a point of reference: after three cycles you know how much the team really delivers and can forecast the rest. Extending a cycle to fit the scope destroys that one measure.

  2. 02

    What “done” means

    This has to be agreed before the first cycle. Code that is written but not tested and not deployed is not done, and the gap between these definitions can amount to thirty per cent of the project's time.

  3. 03

    What not to do mid-sprint

    Add tasks after it has started. If something is truly urgent, something else has to come out; otherwise the rhythm stops measuring anything and you are back to firefighting.

  4. 04

    How many to plan

    As many as you can see. A plan for twenty cycles ahead is fiction; a plan for three, with a priority list for what comes later, is a plan.

Related terms

  • ScrumA specific form of agile work: fixed cycles of a few weeks, three roles and four recurring meetings. It is the most popular one, so it is often confused with agile as a whole.
  • BacklogAn ordered list of everything still to be built, from most to least important. It is not a collection of ideas; it is an order.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.