An Implementation Plan describes the intended approach to carrying out work or a change. It gives the planned activities, instructions, timing, and coordination a named reference that users can review.
When to use it
- Use it when the approach to implementation needs an explicit managed record.
- Use it when instructions and schedule information should be reviewed before or during execution.
Key information
- Plan identity: implementation plan ID, name, description, and summary.
- Approach: instructions, notes, and implementation priority.
- Tracking: estimated dates, due date, estimated effort, and completion percentage.
Common relationships
- Attachment associates the plan with related managed work or information records.
- Baseline can connect the plan to a reference point for its information.
Working with this record
Describe how the work should be carried out and what must be checked along the way. Keep planned dates distinct from actual progress. Use related work records to track individual activities where separate responsibility or completion is needed.
Example
Seal Change Implementation Plan describes the intended drawing update, review, and introduction of the redesigned seal. It provides the approach for the team to follow while the Change Order and Change Tasks coordinate the implementation work.
Choosing the right type
Choose Implementation Plan for the described approach. Choose Change Order for change coordination and Task or Change Task for a specific assigned activity. A plan can guide execution without replacing the individual work records.
