Translations:Requisitos ágiles/2/en

Size levels

Agile project management handles requirements at four size levels, from largest to smallest:

• Theme. A collection of related epics that together describe an entire system or subsystem. It is the highest level of abstraction: too large to estimate directly, it serves as a strategic grouping.
• Epic. A user story that, because of its large size, the team breaks down into stories of a more suitable size to be managed within a sprint. It cannot go directly into the Sprint Backlog: it must be split first.
• User story. The main work item of the sprint. It expresses a user need in a format that everyone involved can understand: the team, the Product Owner, and the stakeholders. It must meet the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable.
• Task. The technical breakdown of a user story into smaller work items. Tasks are managed by the developers during the sprint and usually take no more than one working day.