• 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 a commitment is made as to the detailed specifications of the product, the cost and schedule for the project. This checkpoint document is derived from the Life Cycle Document. 
 

Questions:

 

Question	OK	Issue
How have the outstanding issues or exception items from the previous phase been resolved?
Do we have a statement of the details of the project that the project team and lab management clearly understands?  What are the problems the customer is trying to solve, from a customer perspective (including decision makers, developers, end users, etc.)?  What are the key customer needs, from a customer perspective? What are the key customer benefits this proposed project will deliver, from a customer perspective?  Is the problem space understood?
What technical or organizational risks have been discovered?  Are the required technologies feasible and available?  What is the synergy and potential conflicts (if any) with any existing or potential HP partner?  Are risks understood and acceptable?
Is the specification of the product (ERS) both complete and stable enough to:  Understand the effort, and accurately estimate the staffing and resources required tocomplete the project? Define the necessary interfaces to partners whorely on those interfaces?  Allow review of the FLURPS by stakeholders for comparison to the previously agreed requirements?  How are the FLURPS objectives related to the customer needs (e.g. QFD analysis)?  Are the FLURPS measurable?
Do the project plans include a quality plan which meets stakeholder and customer requirements?
Are all project dependencies fully understood and committed to by all partners and stakeholders?  What are the current risks attached to these dependencies?
Have all the deliverables for this milestone been reviewed by the appropriate stakeholders?
What is the plan to complete the next phase?  Are the appropriate staff available to work on the project?  Is all necessary training available and planned?  What are the project competencies required to successfully implement this proposed product? What are the resources required to successfully complete this project in the market window?  Is the project schedule realistic, and does it provide for achieving the requirements of the project in time to be ready for the target release vehicle?  What are the risks associated with the schedule?  What is the estimated market window of opportunity for the product?
Is there an effective Configuration Management (CM) plan in place to control change throughout the life of the project?
What are the support strategies, migration, and upgrade strategies?
Do the project manager, project team, and stakeholders feel comfortable with the commitments being made?
What is the plan for the phase retrospective?
Should we proceed with this project, or are there better uses of our resources?

 

Deliverables:

 

Deliverable Description	Required	Done
Project Plan  Committed project schedule and staffing and resource requirements  Report on changes to deliverables previously provided Identification of major dependencies, interfaces, risks and how they are managed Configuration management plan and process in place for specifications, source code, etc. Plans for reaching next milestone
Detailed Technical Requirements
High level design
External specification
Quality plan addressing FLURPS+ Quality goals / release criteria defined Preliminary user test 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