Sprints & cycles
The tool organises work into fixed time periods, such as two weeks, with a set list of tasks that carry over or close when the period ends.
On this pageWhat it is
What it is
Sprints, also called cycles, split work into short periods of equal length. At the start the team picks the tasks it will finish in that period, and at the end unfinished tasks are moved to the next one or sent back to the backlog. The tool usually shows how much was planned, how much was completed and how fast the team is moving. Linear calls this feature cycles.
Why it matters
A fixed rhythm gives a team a regular moment to decide what matters most, and stops long to-do lists from growing without limit. For the business it makes progress predictable and easy to review. It suits teams that build software or deliver a stream of similar work. It adds little for a one-person team or for work driven by incoming requests, where a simple board is often enough.
What to check
- Ask whether unfinished tasks roll over automatically or have to be moved by hand.
- Check whether the period length can be changed, and whether cycles can start by themselves.
- Test the reporting, and see whether it shows planned against completed work.
- Ask whether the feature can be switched off for teams that do not work this way.