# Iterations and Timeboxes

> Why agile teams work in short, fixed blocks of time, often one to four weeks. How a timebox stops work from stretching, and what happens to the rest.

**Course:** [Agile, Scrum and Kanban](https://learn.benibix.com/learn/business-agile)  
**Time:** 9 min

**After this lesson you can:**

- Say what an iteration is
- Explain how a timebox works
- Decide what to do with work that does not fit

## Why agile work runs in short, fixed blocks of time

An iteration is one short, fixed block of time in which a team builds something, checks it and learns. Most last one to four weeks, and two weeks is common. At the end the team looks at what it made. The next iteration starts with what it learned. A six-month project holds about 13 two-week iterations.

Short blocks matter because they make feedback fast. A team that shows its work every two weeks finds a wrong turn after two weeks. A team that shows it once, after six months, finds the same wrong turn after six months, with all the work built on top of it.

Each iteration should end with something that works and can be used. It might be small, like one screen that saves a booking. That piece is called an increment, and each new one adds to the last. Half-built work at the end of an iteration does not count.

A timebox is the rule that keeps the blocks fixed. It is a set amount of time for a task or a meeting. When the time is up, it stops. The time does not stretch to fit the work. The work is cut to fit the time.

That sounds harsh, and it is the point. A deadline that can slide gets slid, again and again. A timebox forces the hard question early. What matters most, so we do it first? Work that does not fit goes back on the list for later.

Timeboxes work on meetings too. A planning meeting with a two-hour box ends after two hours, even if people could talk for four. It makes the room pick what to decide now and what can wait.

The common mistake is stretching an iteration to finish one more thing. Once the length changes, the team can no longer compare one block with the next, and plans built on that rhythm stop working. Keep the length fixed and cut the work instead.

![Four equal blocks in a row along a time line, marked iteration 1 to iteration 4. Under each block a piece is added to a growing stack. A label on the blocks reads iteration, the time. A label on the stack reads increment, what it adds. The title says iterations are the time, increments are what they add.](https://learn.benibix.com/diagrams/agile-iteration-increment.svg)

### Example: Lucy cuts a report to fit

Lucy's team works in 2-week blocks. Eight days in, a sales report is clearly going to take 4 more days than are left.

They do not stretch the block. They ship the report with 3 of its 5 charts, which is what the sales team needed most, and put the other 2 charts back on the list.

**Words in this lesson:** [Iteration](https://learn.benibix.com/term/business/iteration), [Timebox](https://learn.benibix.com/term/business/timebox)

**Question:** A two-week iteration is running out and one task is not done. What does a timebox say to do?

**Answer:** End on time and put the rest back on the list. A timebox never stretches. The block ends on time, the work is cut to fit, and whatever is left goes back on the list to be planned again.

---

Source: https://learn.benibix.com/learn/business-agile/iterations-and-timeboxes
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
