Task

Photo of Jan Neudecker
Jan Neudecker
•
1 min. reading time

Tasks are not defined in the current Scrum Guide, but many Scrum Teams still use them as a way to break down Product Backlog Items (PBIs) into smaller, actionable pieces during Sprint Planning.

Earlier versions of the Scrum Guide (2010) described tasks as part of the Sprint Backlog. Today, Scrum is more flexible and it's up to the Developers to decide how they organize their work and does not use the term anymore.

As part of the "how" in Sprint Planning, Developers create a plan for delivering the selected PBIs. This may include identifying tasks, technical steps, or sub-activities that help structure and coordinate the work.

Tasks can support

  • making work more transparent

  • sharing responsibility

  • tracking progress toward completing a Sprint Goal

  • Generate common understanding

But it's important to remember:

  • Tasks are not Product Backlog Items

  • Tasks are not tracked outside the team

  • Finishing all tasks does not mean an item is Done---only meeting the Definition of Done qualifies the work as part of the Increment