Projects and Milestones

A defect matters to the project that must absorb its correction. The project records its organization, owner, delivery method and planned dates. Work packages organize the tasks within that scope. Milestones describe the dated checkpoints the team must meet. Together they let the Project Manager discuss a correction alongside the delivery commitment it affects.

The project can be Planned, Active, On Hold or At Risk while work is underway. Completed and Cancelled record its eventual delivery state. Work packages carry their own progress, including blocked scope. Keep the reason for a delivery concern in the project summary, task description or milestone notes so the status remains understandable to the next reviewer.

• Project scope. Identify the client or internal organization and the owner accountable for delivery. Record the delivery method and budget context, then agree the start and end dates. Keep the summary focused on the work the team is expected to deliver and the conditions affecting that commitment.
• Package schedule. Place tasks inside the relevant work package and review its dates against the project dates. Read estimated hours alongside the effort on the underlying tasks. If corrective work interrupts the package, record the blocked position and the action needed to resume delivery.
• Checkpoint assessment. Give each milestone a name, due date and owner. Pending means the checkpoint still needs its outcome assessed. Mark it Met or Missed based on the actual result and explain that decision in the notes. Resolving a defect does not by itself establish that the milestone was achieved.

Agree how the team defines a work package and what evidence establishes a milestone’s result. Decide who may change a delivery date and what explanation is needed when scope changes. Confirm that task project references agree with their parent work packages before importing existing plans or using project totals in a management discussion.

Choose the operating review that examines At Risk projects and missed checkpoints. The Project Manager should be able to name the unresolved defect or delivery concern, the owner taking action and the evidence needed to change the assessment. Delivery Lead can then use the same context to consider staffing or scope decisions.

The checkout project has a planned acceptance checkpoint. Its discount defect creates corrective work in the checkout package. Project Manager assigns the fix, checks the package dates and discusses whether the milestone can still be met. The task due date provides a working expectation; the milestone remains Pending until its actual acceptance conditions are assessed.

After QA verifies the correction, Project Manager reviews the remaining package work and supporting decision evidence. If the checkpoint is achieved, record Met with an explanation. In a separate rehearsal, the correction arrives too late and the checkpoint is Missed. Preserve the original delivery context and describe the next action. Closing the defect should not silently change either the milestone result or the project’s final state.

• Active Projects — Active delivery scope with owners, dates and effort context.
• Work Package Schedule — Open packages with start and end dates for planning corrective work.
• Milestones At Risk — Pending and Missed checkpoints whose dates and notes need review.

Use project delivery review alongside fix and verification when a defect affects a checkpoint.