Main Description |
This artifact provides a focal point for the entire team:
-
It provides one list containing all requests for additional capabilities or enhancement for that application. Note
that some of these requests may never be implemented, or be implemented in later projects
-
It provides one list of all the work to be prioritized, estimated, and assigned within the project. The risk list
is prioritized separately.
-
It provides one place to go to for the development team to understand what Micro-Increments need to be delivered, get references to material required
to carry out the work, and one place to go to report progress made.
These are the typical work items that go into this list:
-
Use cases (and references to use-case specifications)
-
Supporting requirements
-
Changes and enhancement requests
-
Defects
-
Development tasks
Work items can be very large in scope, especially when capturing requests for enhancements, such as “Support Financial
Planning” for a personal finance application. To allow the application to be developed in micro-increments, work items
are analyzed and broken down into smaller work items so they can be assigned to an iteration, such as a use-case
scenario for “Calculate Net Worth”. Further breakdown may be required to identify suitable tasks to be assigned to
developers, such as “Develop UI for Calculate Net Worth”. This means that work items often have parent/child
relationships, where the lowest level is a specification and tracking device for micro-increments.
Work Items should contain estimates, see Guideline: Managing Work Items and Guideline: Agile Estimation.
|