1.0 Title
2.0 Purpose: To monitor the "stories" which are the "tasks" developed in the pm201a and the pm201b meetings. This allows a KanBan task monitoring and completion approach to getting the project done.
The storyboard should be done at the "keycode' level - which has both work orders and the ISEL as its parent.
3.0 Usage: Used for all HRI projects. Unique to HRI for engineering, but not software development.
4.0 Frequency
5.0 References:
This was from ALM Expo 2010
6.0 Responsibility
7.0 Ownership
8.0 Effort
9.0 Risks
10.0 Contents
10.1 Stories = tasks = deliverables
What is a "story" in a software project is part of a CDID in the hri07e pm201 series. In fact it may be a single keycode. Each keycode has an iteration (as in Scrum) and is published at some point - with an estimate of its probability of being within the final value. These ranges are co-published in the data sheet for the configuration item being designed.
11.0 MetaData
12.0 File Handling Policy
13.0 Procedures
14.0 Tutorials