The purpose of this document is to describe the process for a major revision or creating a new object. The top level party should hold on to this document and use it to organized the development of the object. During the process please write on the document improvements and alterations.

Step 0: Kick-off Development Cycle

The kick-off is essential to inform everyone that the object is now in-flight for a development cycle.

Step 1: Kick-off Meeting

The purpose of this step is to identify and start coordinating development of all sub and co components of this top level object.

Step 2: Sketch Session

A sketch sessions should be conducted for mid to large-sized projects or problems where the requirements and solutions are still ambiguous. Sessions include the lead stakeholder (client), product owner, domain experts, designers and facilitators. The group works together on diverging ideas around the problem space, then pair the ideas down to ones that are actionable.

If the object owners decide a sketch session would be helpful have a sketch session. If the problem and/or solution is ambiguous then a sketch session is recommended - otherwise if the solution is unambiguous probably not needed.

Step 3: Define a six digit alpha code

If necessary define a new six digit alpha code. Part numbering scheme will probably change copy from other document

Step 4: Product Lifecycle Update / Testability

Every finished goods object we produce includes an informal product lifecycle narrative document. The goals of the object should be reflected in the testability of the object. For each goal we should have at least one test. Each time we start a design process loop on a new or existing object we need to update the PLM narrative with answers to questions similar to:

Step 7: Coordinate the sub-components and co-components development

This is the actual development of all the sub and co components of the top level device. This step could take a very long time depending on the scope of the project. During this time the top level party of this device is responsible for fostering communication between all the sub and co component top level parties so development is as seamless as possible.

Step 8: Verify all released Sub-components and Co-Components

The purpose of this step is to verify that the top level party of this object has all the parts they need to do a top level release.

Step 9: Create the Production Package

Step 10: Release Top Level

We need a barebones checklist - ask calla

Step 11: Post Release Review (ProdMgr)