1.0 Title: Use Case Story
2.0 Purpose: To identify a task in a very short statement for use in an "Agile" project
3.0 Usage: This is usually used in the context of a software project but can be adapted to other disciplines as well.
4.0 Frequency:
5.0 References
http://agilezen.com/tour/visualize
6.0 Responsibility
7.0 Ownership
8.0 Effort
9.0 Risks
The Description may be too short to be useful for engineering tasks where the initial identification is usually an aggregate of many smaller tasks - which may eventually become "stories" that can be completed in a "sprint"
10.0 Contents
For manual systems there are tow elements
- a "sticky note"
- a descriptive title for a task (eg "create Login screen")
11.0 MetaData
12.0 File Handling Policy