glossary

Sprint

delivery & projectsreviewed by the Forge team · 8 June 2026

A short, fixed block of time - often one or two weeks - in which a team commits to completing an agreed set of work.

For example, an agency runs two-week sprints, planning a focused batch of work at the start and reviewing it at the end. The client sees steady, predictable progress and can re-prioritise between sprints as things change.

Why it matters to agencies: sprints give open-ended or evolving work a rhythm and predictability that suits agency delivery, especially on retainers. They make progress visible, contain scope to a fixed window, and give clients regular, low-risk moments to steer.

common mistakes
  • Over-committing the sprint, so it always slips.
  • No review or retro at the end.
  • Letting scope change mid-sprint.
common questions
What is a sprint?

A short, fixed block of time - often one or two weeks - in which a team commits to completing an agreed set of work.

How long is a typical sprint?

Most are one or two weeks - long enough to finish meaningful work, short enough to stay focused and re-plan often.

How do sprints help agencies manage scope?

Work is committed one sprint at a time, so new requests wait for the next sprint instead of derailing the current one - a natural guard against scope creep.

What is the difference between a sprint and a milestone?

A sprint is a fixed block of time; a milestone is a checkpoint marking completed work, which a sprint might or might not reach.

← back to the glossary
design. build. iterate.

Your client status page, built by Forge.

Forge builds, hosts and runs your client status page - branded, shaped around how your agency works, and live in minutes. No spreadsheets, no code.