• Initiation
• Requirements Complete
• Commit
• Functionality Complete
• QA Complete / Release

• Project Data Sheet
• Project Plan
• External Specification
• User Requirements
• Internal Specification
• Quality Plan
• Configuration Management Plan
• Memorandum of Understanding
• Official Process Image

This milestone marks the point at which the product development, including testing, is complete.  Versions of on-line deliverables for this milestone which are under source control are tagged with an appropriate tag..  This checkpoint document is derived from the Life Cycle Document. 
 

Questions:

 

Questions	OK	Issue
How have the outstanding issues or exception items from the previous phase been resolved?
Have any requirements, specifications or functionality changed since Functional Complete?
Has the product met all QA criteria agreed to at Functionality Complete? Have all the items described in the External Specification and Project Plan been delivered successfully?
Have all the deliverables for this milestone been reviewed by the appropriate stakeholders?
Are the deliverables what the “customer” wanted?
Do the project manager, project team, and stakeholders feel that the product is ready for release?
What is the plan for the phase retrospective?

 

Deliverables:

 

Deliverable Description	Required	Done
Tested Product  All items covered in the External Specification and Project Plan
QA Results Summary, including: Code Stability  Incoming Defect Find/Fix Rate  Defect Density  “Customer” feedback
Postmortem review plan

 

Issues:

These issues should be generated for the various checkpoints and the ongoing set should accumulated in the project plan.
 

Issue	Owner	Resolution
Roses are red, violets are blue, you don't have enough people to make it through.	Buzz Lightyear	Pending.
Grinches are green, Santas are red, if you don't get this done, you'll get shot with lead..	Buzz Lightyear	yyyy/mm/dd: Resolution comments.

 

Approvals:

The approval process is that the people responsible for approving the checkpoint will be informed by email that they should review the materials on the web.  After a timely review, they will mail their approval, with any issues to the project owner.  The issues will be added to the formal issues list.  The reviewer should also specify explicitly whether the checkpoint is approved or disapproved and why.  The owner will, when all approvals have been received, send an email notification.
 

Approvals	Required	By	Approved
Authorizing manager: name  (R&D section manager, lab manager, organization manager).	Yes	Email	date
Stakeholder: name  (project team members - if appropriate).	Optional	Verbal	date
Partner: name (internal customer - if appropriate).	Optional	Email	date
Other: name	Optional	Signature	date