Glossar - Details
Backlog Item
From the users perspective, a Backlog Item describes the intended result. The following questions shall be answered: Who? (role), What? (application requirement), Why? (use). Note that the customer (user) is meant with WHO, and not the developer or the implementer. The Backlog Item does not replace the requirement specification but shall be seen as the input for it.
The Backlog Items are roughly defined by Product Owner(s) and are further developed with the Agile Team. These granular working packages are the basis for the features at the Product Backlog.
A good Backlog Item has the following characteristics:
Independent from other Backlog Items
Negotiable in detail
Valuable
Assessable
Testable
Simple, short, precise
Reference Volume (and volume-specific, additional or differing definitions to the standard):
VDA volume "Agile Collaboration", Jan. 2021
From the users perspective, a Backlog Item describes the intended result. The following questions shall be answered: Who? (role), What? (application requirement), Why? (use). Note that the customer (user) is meant with WHO, and not the developer or the implementer. The Backlog Item does not replace the requirement specification but shall be seen as the input for it.
The Backlog Items are roughly defined by Product Owner(s) and are further developed with the Agile Team. These granular working packages are the basis for the features at the Product Backlog.
A good Backlog Item has the following characteristics:
Independent from other Backlog Items
Negotiable in detail
Valuable
Assessable
Testable
Simple, short, precise
Reference Volume (and volume-specific, additional or differing definitions to the standard):
VDA volume "Agile Collaboration", Jan. 2021