Checkpoint documents:
Other documents:
|
This milestone marks the point where the detailed technical requirements
of the project, as seen from the user’s viewpoint have been identified.
This checkpoint document is derived from the Life
Cycle Document.
|
Question
|
OK
|
Issue
|
| How have the outstanding issues or exception items from the previous
phase been resolved? |
|
|
Do we have a statement of requirements that the project team and lab
management clearly understand?
-
What are the value proposition and product positioning?
-
Are the target markets defined, segmented, and otherwise identified sufficiently
for the project team to validate the specifications developed during the
next phase?
-
Are the benefits to customer, the market and HP articulated sufficiently
to allow the project team to develop a vision of the final product?
|
|
|
| What are the existing customer commitments for the proposed product? |
|
|
What are the measurable FLURPS+ objectives for the proposed product?
-
Do we understand the customer use model for the product?
|
|
|
| What are the applicable standards? |
|
|
What alternative solutions have been considered?
-
What is the final solution chosen for the project? What are its pros
and cons?
-
What prototypes have been developed and what was learned? Have the
prototypes tested and proven all the critical technologies required for
the project?
|
|
|
| What risks have been discovered, or not been eliminated by the investigation? |
|
|
| Is there a life cycle chosen and a project plan in place proceed? |
|
|
| What is the preliminary plan for user test? |
|
|
| What are the interdependencies that are critical to project success? |
|
|
What is the plan to complete the next phase?
-
What are the required resources and skills needed to complete the proposed
product in the necessary timeframe?
-
What external resources are available to optimize our investment and meet
the window of opportunity?
|
|
|
| What is the plan for the phase retrospective? |
|
|
| Have all the deliverables for this milestone been reviewed by the appropriate
stakeholders? |
|
|
| Do the project manager, project team, and stakeholders feel comfortable
with the commitments being made? |
|
|
| Should we proceed with this project, or are there better uses of our
resources? |
|
|
|
Deliverable Description
|
Required
|
Done
|
| Final PDS |
|
|
Preliminary Project Plan
-
Life cycle definition
-
Preliminary schedule
-
Plan for identifying and managing major dependencies
-
Resource/staffing estimate and training plan
-
Plans to reach next milestone
|
|
|
| Line-item analysis of requirements document |
|
|
| Preliminary external specification |
|
|
| Preliminary quality plan |
|
|
| Summary of solution alternatives considered and description of
the solution chosen |
|
|
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. |
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 |
|
