Sprints
Plan work into time-boxed cycles with a clear lead.
Sprints group issues into a time-boxed cycle — a week, two weeks, whatever your team runs — so planning has a rhythm and delivery has a deadline.
Running a sprint
Create the sprint
From a project, create a sprint with a name, dates, and a sprint lead.
Fill it
Pull issues in from the backlog — or bulk-add all of an epic's issues at once.
Work it
Issues carry their sprint, so boards and timelines can be viewed through the current cycle.
Complete it
Close the sprint when the cycle ends and deal with what didn't finish.
The sprint lead
The lead isn't just a label: for every issue completed in the sprint, the lead earns the accountable share of the credit. Ownership of the cycle is recognised, not assumed.
Keep sprints honest — a sprint that always rolls half its issues forward is a planning signal, not a failure. Size the next one smaller.
Related
- Organizing work — statuses, labels, epics, and filters.
- Guilds & credit sharing — how sprint leadership earns credit.