{"id":5003363,"date":"2015-12-17T00:09:52","date_gmt":"2015-12-17T08:09:52","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&p=5003363"},"modified":"2022-08-30T12:10:05","modified_gmt":"2022-08-30T19:10:05","slug":"timebox","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/timebox\/","title":{"rendered":"Timebox"},"content":{"rendered":"
\n
\n

A timebox is a previously agreed period of time during which a person or a team works steadily towards the completion of some goal. Rather than allow work to continue until the goal is reached, and evaluate the time taken, the timebox approach consists of stopping work when the time limit is reached and evaluating what was accomplished.<\/p>\n

Timeboxes can be used at varying time scales. The\u00a0\u201cPomodoro technique\u201d<\/a>\u00a0organizes personal work around 25-minute timeboxes. In a completely different domain\u00a0\u201cspeed dating\u201d<\/a>\u00a0is known for its seven-minute timeboxes. Time scales ranging from one day to several months have been used.<\/p>\n

The critical rule of timeboxed work is that work should stop at the end of the timebox, and review progress: has the goal been met, or partially met if it included multiple tasks?<\/p>\n

Origins<\/h2>\n

Timeboxed\u00a0iterations<\/a>\u00a0are a distinctive feature of the early Agile approaches, notably\u00a0Scrum\u00a0<\/a>and\u00a0Extreme Programming<\/a>, but they have an earlier history:<\/p>\n