|
Project name:
|
Example |
|
Owner:
|
Sum Body Else |
| Checkpoint date: | yyyy/mm/dd |
- Project Data Sheet
- Project Plan
- External Specification
- User Requirements
- Internal Specification
- Quality Plan
- Configuration Management Plan
- Memorandum of Understanding
- Official Process Image
| Description: |
This checkpoint/milestone marks the point at which the management team
evaluates the potential worth of the project. This checkpoint document
is derived from the Life
Cycle Document.
| Questions: |
|
|
|
|
| Do we have a statement of the subject and purpose (focus) of the project that the project team and lab management clearly understands? | ||
| Does this project promote the organization mission / vision? | ||
| Do we understand who the partners / stakeholders are for this project? Where partners / stakeholders are involved, what are the plans for managing the relationship? | ||
| What are the criteria for continuing/canceling the project? | ||
| Have all the deliverables for this milestone been reviewed by the appropriate stakeholders? | ||
| Are the key questions to be answered during the Investigation / Requirements phase identified? | ||
| Are there adequate staffing and other resources available to complete the next phase? | ||
| Should we proceed with this project, or are there better uses of our resources? |
| Deliverables: |
|
|
|
|
| Preliminary PDS (purpose, scope, value proposition, preliminary schedule for major milestones), plus feedback mechanism (e-mail at least). | ||
| Preliminary Life Cycle Definition
(using the Life Cycle Document). |
Yes | Yes |
| Plans for reaching next milestone (specifically a resource / staffing plan). |
| Issues: |
These issues should be generated for the various checkpoints and the
ongoing set should accumulated in the project plan.
|
|
|
|
| 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.
|
|
|
|
|
| Authorizing manager: name
(R&D section manager, lab manager, organization manager). |
Yes | date | |
| Stakeholder: name
(project team members - if appropriate). |
Optional | Verbal | date |
| Partner: name
(internal customer - if appropriate). |
Optional | date | |
| Other: name | Optional | Signature | date |