t is for...


In Scrum and Extreme Programming, a unit of work, estimated in hours. During the iteration planning meeting, user stories are decomposed into tasks. In his book, Agile Software Development with Scrum, Ken Schwaber writes, “Tasks should have enough detail so that each task takes roughly four to sixteen hours to finish.”

In practice, many Agile practitioners vary from this formula, by preferring more granular tasks, or more abstract sizing units than hours(e.g., story points). Some do not decompose stories into tasks at all, preferring to add user stories directly to their task board.




Agile Software Development with Scrum by Ken Schwaber and Mike Beedle

Iteration Planning on www.extremeprogramming.org.

Posted in t | Leave a comment

Task Board

Also Scrum Board

A type of information radiator that presents, at minimum, “to do” “doing” and “done” columns for organizing a team’s work . Some teams include their backlog as a column on the task board, while others limit it to work to be performed during the current iteration. Ideally, the task board is a physical thing, consisting of notecards or sticky notes affixed to a wall, although distributed teams may use an online task board application.

In Scrum, the Scrum Board is populated with tasks for the current sprint, while other Agile teams may populate it with User Stories.


The term Task Board derives from Scrum.

Posted in t | Leave a comment

Task Complete Definition

See Definition of Done.

Posted in t | Leave a comment

Timebox, Timeboxing

See Iteration and Iterative Development.

Posted in t | Leave a comment