All modules

Project Management

Sprints

Time-boxed planning cycles with active sprint, backlog, and retrospectives.

What it is

Containers for Task Board tasks scoped to a date range. One sprint is "active" at a time. When you complete a sprint, an auto-snapshot of the entire GDD fires (free version-history bookmark) and you can record a retrospective.

When to use it

  • Running 2-week scrum-style sprints with a defined goal.
  • Carrying unfinished tasks forward to the next sprint without losing context.
  • Tracking velocity over time.
  • Recording a retrospective so the team doesn't repeat the same mistakes.

How to use it

  1. 1Click "+ New Sprint" — name, start, end, goal.
  2. 2Add tasks via Task Board; they're scoped to the currently-active sprint.
  3. 3When complete, click "End Sprint" — incomplete tasks move to backlog, a snapshot is auto-saved.
  4. 4Write a retrospective and a new sprint goal before starting the next one.

Tips you should know

  • Only one sprint can be "active" at a time — ending one auto-activates the next if it's queued.
  • Auto-snapshots from sprint completion count against your version-history limit (Pro 20, Team unlimited).
  • Tasks carried over keep their original creation date — velocity counters dedupe correctly.
  • Goal field is mandatory for new sprints — feature, not bug; sprints without goals turn into chaos.

Related modules