Cycles & Sprints

A cycle is a container for a block of time — usually one or two weeks. Tasks scheduled into a cycle should be realistic to finish by the end date. The cycle is where retros happen.

• Start date — when the cycle begins
• End date — when it closes
• Status — upcoming / active / completed

Create the cycle, then drag tasks into it by setting cycleId on each task. The Cycles page shows a gantt view out of the box so the team can see overlaps at a glance.

When a cycle completes, move it to completed and use the embedded doc area to capture what went well, what didn't, and what to change next cycle. Based doesn't mandate a format — you own the template.