Delivery exceptions

An exception is useful when the team can identify the work it affects and the person who will act. Issues carry a project, severity, owner and delivery state. Milestones retain their due date and outcome, while risks record probability, impact, mitigation and ownership. Use those records to explain why a task or project needs attention.

Exception Triage brings overdue tasks and milestones together with fixed-but-unverified issues and leading open risks. The queue shows the owner, age and a direct path to the record. The Project Manager can use that starting point to discuss the next action with the responsible person and return to the capacity plan when commitments need to change.

• Issue intake. Set an existing issue to Open with its severity to request triage. The triage action moves an eligible issue to Triaged and records an operation receipt. Missing severity or a state other than Open blocks the action and records the failed attempt.
• Verification follow-through. Keep Fixed issues visible until the QA Engineer examines the result and records verification under the team’s procedure. A fix awaiting review can still affect the next delivery decision.
• Milestone and risk ownership. Review pending or missed dates with the milestone owner. For resource concerns, record the risk and mitigation so the Delivery Lead can discuss the capacity consequence with the project manager.

Agree how the team assigns severity and who follows an issue after triage. Define what evidence the QA Engineer needs to verify a fix and who may close the issue afterwards. Keep the triage action and the later verification procedure clear so staff know which action is being recorded.

Define the meaning of milestone Met and Missed, including who updates the outcome after a review. Agree how probability and impact are used when discussing risks. Use the recorded score and rating with their underlying inputs, and settle the scoring convention during setup before making comparisons between projects.

A blocked extraction task puts a Friday milestone at risk. The developer raises an Open issue with High severity and the correct project. Triage moves it to Triaged and records the execution result. The manager assigns follow-through and records the resource concern with a mitigation that can be discussed at the planning review.

When the fix is ready, leave the issue at Fixed until the QA Engineer checks it. Ask the reviewer to find the evidence and record the appropriate verification outcome. Rehearse an issue with missing severity as well, then inspect the failed receipt. The team should be able to distinguish an intake problem from a fix that still needs examination before the milestone can be treated as met.

• Open Issues — Issues still requiring triage, work or verification, with severity and owner visible.
• Milestones At Risk — Due checkpoints that remain pending or are recorded as missed.
• Exception Triage — The shared queue for overdue work, unverified fixes and leading open risks.

Follow issue triage and verification, then revisit commitments through delivery review and rebalancing.