Definition
Cycle (Sprint)
A cycle — often called a sprint — is a fixed, repeating time-box, usually one or two weeks, during which a team commits to a focused set of work and aims to finish it. Cycles create a regular cadence for planning, focus, and review, turning an open-ended backlog into shippable increments.
Key takeaways
- A cycle (or sprint) is a fixed, repeating time-box — usually one or two weeks — that a team commits a focused set of work to.
- Cycles trade Kanban's continuous flow for rhythm and predictability, turning planning into a habit rather than an event.
- Consistent cycle length is what makes velocity meaningful — you can only average completed work per cycle if every cycle is the same size.
- Unfinished work rolls forward to the next cycle rather than being abandoned, and the cadence creates a natural review checkpoint.
The terms cycle and sprint describe the same idea: a short, time-boxed interval with a clear start and end. At the start, the team pulls a realistic slice of the backlog into the cycle. During it, the team protects focus and resists scope creep. At the end, unfinished work rolls forward and the team reflects before the next cycle begins.
Cycles trade the pure continuous flow of Kanban for rhythm and predictability. The fixed cadence makes planning a habit rather than an event, gives stakeholders a reliable beat to sync with, and produces a natural checkpoint for measuring velocity — how much the team reliably completes per cycle.
Healthy cycles are short enough to limit how wrong a plan can be, and consistent enough that velocity becomes meaningful. Many teams blend approaches: cycles for cadence, with a Kanban board and WIP limits managing flow inside each one.
Planoda treats cycles as first-class: work auto-rolls to the next cycle when unfinished, and burndown and velocity charts are generated automatically from the cycle's scope.
Related terms
- KanbanKanban is a visual workflow method that maps work onto a board of columns representing stages — typically backlog, in progress, and done. Cards move left to right as work advances. It emphasizes continuous flow, making bottlenecks visible, and limiting work in progress rather than committing to fixed time-boxes.
- SprintA sprint is a fixed, repeating time-box — usually one to four weeks — during which a Scrum team commits to a focused set of work and aims to ship a usable increment. It is the Scrum term for the iteration other frameworks call a cycle, giving the team a regular cadence for planning, focus, and review.
- BacklogA backlog is the ordered list of all work a team has identified but not yet started — features, bugs, improvements, and ideas. It is the team's single source of pending work, prioritized so the most valuable or urgent items sit at the top, ready to be pulled into a cycle or onto a board.
- VelocityVelocity is the average amount of work a team completes per cycle, measured in issues or story points. By tracking it over several cycles, teams forecast how much they can realistically take on next. Velocity is a planning aid for a specific team over time — never a target to maximize or a way to compare teams against each other.
- BurndownA burndown chart tracks remaining work against time over a cycle, sloping from the total scope down toward zero as items are completed. It shows whether a team is on pace to finish what it committed to, making slippage visible early. The ideal line falls steadily; a flat line warns that work is stalling.