# AEVUS Project Delivery Starter

Original AEVUS working template · November 15, 2026

Use for one bounded project. Complete it with the sponsor and delivery team; agree the required level of detail before execution. This is an AEVUS template, not a PMI publication.

Start with the need statement.

- I / Intake: Capture the needs, users, outcomes, and constraints.
- A / Assess: Review the current state, gaps, risks, and options.
- D / Develop: Design and build a practical solution in increments.
- V / Validate: Test against agreed needs and confirm readiness.
- T / Transition: Prepare for release, support, and operational handoff.

Use the working sections below across these five stages. Capture needs in Intake; review the baseline, gaps, risks and options in Assess; plan and review increments in Develop; collect test evidence and confirm readiness in Validate; prepare release, support and operational handoff in Transition.

## 1. Mission and acceptance

- Project / sponsor / delivery owner:
- Problem and people affected:
- Desired business outcome and how it will be measured:
- Baseline and evidence source:
- In scope / out of scope:
- Deliverables and acceptance criteria:
- Who accepts the result:
- Budget authority / available capacity / constraints:

## 2. Milestones and ownership

| Milestone / deliverable | Owner | Target / assumptions | Dependencies | Acceptance evidence |
| --- | --- | --- | --- | --- |
| Complete with the team | Name a person | Agree a date; record uncertainty | Identify required inputs | Link to a reviewable result |

## 3. Risks, assumptions, issues and dependencies

| ID | Type | Description / business effect | Owner | Response / action | Due / review date | Status / evidence |
| --- | --- | --- | --- | --- | --- | --- |
| R-01 | Risk | What could happen? | Named owner | Mitigate, avoid, transfer or accept through the right authority | Agreed date | Current assessment |
| A-01 | Assumption | What must be true for the plan to hold? | Named owner | Validate with a source | Agreed date | Confirmed or unresolved |
| I-01 | Issue | What has already happened? | Named owner | Next corrective action | Agreed date | Resolution evidence |
| D-01 | Dependency | What must arrive or finish first? | Named owner | Coordinate the handoff | Required date | Receiving-side confirmation |

## 4. Decisions and changes

| Decision / change | Options and effect on scope, cost, schedule, risk or quality | Decision owner | Decision / rationale | Date | Communicated to |
| --- | --- | --- | --- | --- | --- |
| Define the question | Include assumptions and tradeoffs | Authorized person | Record an explicit decision | Agreed date | Affected owners |

## 5. Weekly review

- Outcome accepted since last review / evidence:
- Next useful deliverable / owner / target:
- Current forecast and what changed:
- Blocker / decision needed / decision owner / needed by:
- Risks or dependencies that changed:
- Scope, cost, quality or capacity tradeoffs:
- Client or counterpart confirmation:

Do not equate task completion with delivered business value. Separate an estimate, a demonstrated increment, client acceptance and an observed outcome.

## 6. Validation and transition

- Deliverables checked against acceptance criteria:
- Test and user-review evidence:
- Open defects / disposition / authorized acceptance of residual risks:
- Receiving owner / support contact / escalation path:
- Documentation / access / training completed:
- Recovery and operating responsibilities:
- Final acceptance / unresolved actions:
- Benefit-review owner / baseline / review date:

## Official reference

[Project Management Institute — PMI.org](https://www.pmi.org/) provides its own standards, learning and resources. This independent working template does not reproduce the PMBOK® Guide or establish PMI endorsement.
