Engagement retrospective
Rebuilds the defect and rework history so the team can establish causes and choose changes.
Improve the practice
The saved work
A retrospective with a specific next action
Improvement action 1 — Nadia, existing named owner: assess the scope-v2 change against the earlier scope-v1 report and record whether a revised internal working product is required. Test: a review must explicitly identify whether the residual-obligation preparation deliverable is represented; it must not imply access, retention, contractual, or client actions.
Improvement action 3 — human correction: Nadia is the accountable lead for the existing residual-obligation preparation dependency; Rowan is the recorded next owner after Elena. Confirm that assignment and its reopened verification state against the current dependency record before preparing the support, access-verification and retention-verification decision fields. The AI preparation omitted that dependency record, so its original missing-owner assertion is unsupported. Test: the handover identifies owners and outstanding verification questions without asserting provider grants, revocations, retention periods, deletion, or receiving-system completion.
A related local example. It shows the stated part of the work, not every step in this design. Read it in saved outputs
- Starts when
- Milestone, defect or case close
- What it works from
- Actual defects, decisions, exceptions and client feedback
- What it prepares
- Candidate lessons and improvement actions
- What your team decides
- Team establishes causes and chooses changes
What this helps your team do
This path has been checked in the fictional local build.
Responsibilities connected
See what each agent is responsible for preparing in this workflow. These are designs and local examples, not a set of independently running agents.
When it stops and asks
Unclear reuse rights, weak demand or a client-specific exception stays a candidate; it is not promoted to firm policy or a launched service.
Supported scope, source access and authority are agreed for each installation.
