# IADVT timeline — deliverables, owners and approvals

AEVUS · November 15, 2026

Recommended roles for the teaching example. Assign actual people and decision rights before execution. The timeline represents a logical sequence, not a dated schedule or a record of completed approvals.

| Stage | Deliverables | Recommended owner | Review / approval owner | Checkpoint |
| --- | --- | --- | --- | --- |
| Intake | Project brief; Stakeholder map; Acceptance criteria | Project manager | Sponsor | Scope approval |
| Assess | Options decision; Access matrix; Risks & dependencies | Project manager | Sponsor | Approach approval |
| Develop | Delivery backlog; Change record; Increment handoff | Engineering lead | Product owner | Increment acceptance |
| Validate | Validation matrix; Findings & limits; Readiness decision | QA lead | Release authority | Release authorization |
| Transition | Release checklist; Operating handover; Benefits review | Service owner | Service owner | Handover acceptance |

Start with the need statement. Follow Intake → Assess → Develop → Validate → Transition.

## Stage aims and checkpoint decisions

### I / Intake

Capture the needs, users, outcomes, and constraints.

Agree the problem, intended outcome, boundaries and acceptance criteria before committing to delivery.

### A / Assess

Review the current state, gaps, risks, and options.

Approve the recommended approach, access boundaries, dependencies and resource assumptions. Escalate unresolved constraints before implementation.

### D / Develop

Design and build a practical solution in increments.

Review the working increment against agreed acceptance criteria. Route material scope or authority changes to the sponsor before proceeding.

### V / Validate

Test against agreed needs and confirm readiness.

Review the test and acceptance evidence, unresolved findings and proposed release. Obtain explicit authorization from the designated release authority; passing tests alone do not authorize Production.

### T / Transition

Prepare for release, support, and operational handoff.

Accept operating documentation, support and escalation responsibilities, open actions and benefit-review ownership before closing delivery.

## How to use the timeline

The stage owner coordinates the work and its evidence; the review/approval owner makes the checkpoint decision within assigned authority. One person may hold multiple roles if the organization explicitly agrees those responsibilities. Assign actual people, substitutes and escalation routes in the project brief. Rework a stage when its evidence does not support the decision.

This is an original recommended role map for the retrospective AEVUS AI Playbooks teaching example. It does not document historical assignments, completed sign-offs, PMI endorsement or release authorization for another project.

For background on sponsor responsibilities: [PMI project sponsorship](https://www.pmi.org/learning/library/duties-effective-project-sponsor-responsibilities-4469). The specific IADVT mapping is an AEVUS teaching design, not a PMI-prescribed structure.
