| Main Description | It's either a functional or technical requirement, an enhancement request, a bug or anything else which implementation
brings up value to the Product Owner.
Its general attributes are:
-
estimated value, most oftenly calculated relatively to other items through priorities,
-
estimated development cost,
-
eventually the theme (functional domain) it belongs to,
-
eventually its type (defined by the project, user story, for instance, bug, non-funcitonal requirement),
If the user story technique is used, as well as test-driven development, test acceptance criterias are associated.
A PBI goes through the following states:
-
created
-
estimated
-
planned (associated to a future sprint)
-
associated to current sprint (implementation is ongoing)
-
done
-
|
