# Project Delivery Framework Kit

> A delivery framework for technology projects: six stages, five decisions, four routes, two workbooks, three decks, 12 templates and a guide.

Source: https://ciohelm.com/toolkits/project-delivery-framework-kit · Area: Manage · Price and packs: https://ciohelm.com/llms.txt

In our experience, most projects that disappoint were in trouble before the build started. This kit gives you one way to take technology change from idea to benefit: six stages, five decisions held on evidence, a route for each kind of project, and every template you need, filled in for a worked example.

Excel, PowerPoint and Word files. Yours to use and adapt inside your organisation.

## 18 working files, not a slide pack to read

Every file is editable and comes with a worked example for one fictional company, so you start from something, not from a blank page. Workbooks calculate as you type.

### Project delivery workbook (Excel)

21 sheets that run one project: the artefacts your route and size require, the five decisions with criteria and a calculated readiness, plan, team and RACI, requirements traced to build, tests and defects, data mapping and loads, access and segregation of duties, risks, issues and changes, go-live readiness, a timed cutover, early-life support against service levels, and benefits. A dashboard pulls it together.

### Portfolio intake and business case workbook (Excel)

8 sheets: six weighted criteria with anchored scales, 14 demands scored and ranked against team capacity, an options appraisal, and a five-year business case with NPV, payback and three sensitivities.

### Framework overview deck (PowerPoint)

15 slides to get the framework adopted: the framework on a page, the stages, decisions, routes, sizes, RACI, threads, measures and a 90-day roll-out.

### Project charter deck (PowerPoint)

16 slides for decision D2: problem, objectives, scope, requirements, options, architecture, plan, team, business case, risks and change impact.

### Decision review pack (PowerPoint)

12 slides for a decision meeting, worked through for a go-live decision: criteria and evidence, tests, defects, data, readiness, cutover and conditions.

### Demand request and business case (Word)

A one-page request anyone can complete, then the business case the portfolio board scores.

### Stakeholder and user research guide (Word)

Who to talk to, interview guides by role, how to observe the work and turn notes into findings.

### Current-state assessment (Word)

Process, pain points, systems, data and volumes as they are today, with the evidence.

### Change, training and communication plan (Word)

Impact by group, training needs, the communication calendar and how adoption is measured.

### Kickoff and design workshop guide (Word)

Kickoff agenda and a series of design workshops with inputs, outputs and decisions.

### Functional design specification (Word)

Process, rules, screens, roles and data for each requirement, traced to tests.

### Integration design specification (Word)

Each interface: trigger, payload, mapping, errors, volumes, security and monitoring.

### Test strategy and test summary report (Word)

Test levels, entry and exit criteria, defect rules and the report that goes to the go-live decision.

### Cutover and rollback plan (Word)

A timed runbook with owners, go / no-go points, rollback triggers and communication.

### Service handover pack (Word)

What the support teams receive, the exit criteria for early-life support and sign-off.

### Change request impact assessment (Word)

Scope, cost, time, risk and benefit impact of a change, with a recommendation.

### Benefits and lessons review (Word)

Benefits against the business case and lessons that change how the next project runs.

### Delivering projects that land (Guide)

How to use the framework, scale it, hold decisions well and avoid the common failures.

## Project delivery workbook, sheet by sheet

The workbook carries the method: scores, choices and plans calculate as you type, and the dashboard and deck figures come from it. Click any image to see it full size.

**Dashboard**: Stage, next decision and its readiness, tests, defects, risks, money and support.

**Decisions**: Five decisions with written criteria and a calculated readiness and recommendation.

**Requirements**: Each requirement traced to build items, tests and defects, with its proof status.

**Readiness**: Go-live criteria checked against live figures from the workbook.

## Decisions held on evidence, not on enthusiasm

Each decision has written criteria, and the workbook calculates its readiness from the registers: requirements proven by passing tests, defects open by severity, data loads within tolerance, readiness items, risks with responses. The sample project goes live with two conditions, and the evidence shows why.

## The method, step by step

### Weeks 1-2 · Adapt

Name the decision-makers, set the routes and sizes for your organisation, adjust the criteria.

### Weeks 3-4 · Agree

Present the framework overview to the executive committee and agree the measures.

### Months 2-3 · Pilot

Run two projects through it, one standard and one small change; keep what helps.

### Month 4 · Default

Make it the way every new demand is handled, and report the measures twice a year.

### Who it is for

- CIOs and heads of IT who want projects to land, not just finish
- PMO and delivery leads setting up or refreshing a delivery method
- Project managers and product owners running a package, SaaS or custom build
- Advisers setting up delivery governance for a client (one licence per client organisation)

### What you need

Excel, PowerPoint and Word, or compatible software. About a month to adapt the framework, then a pilot on two projects.

### Free guides on this topic

- [Technology business case: a structure finance will recognise](https://ciohelm.com/guides/technology-business-case)
- [IT steering committee that decides](https://ciohelm.com/guides/it-steering-committee)

## Questions about the kit

**Does it replace agile or our project method?**

No. It sets the five decisions and the evidence each needs. Between decisions, teams organise the work as they choose, and the agile product route keeps sprints and backlogs.

**Is it too heavy for small changes?**

No. A small change needs ten artefacts, most of them one page. A large project needs all thirty-four. The workbook shows what your route and size require.

**Does it follow PRINCE2, PMBOK or SAFe?**

It is compatible with them and does not require any. It focuses on what goes wrong most often in technology projects: weak business cases, late scope, thin testing, risky cutovers and benefits nobody tracks.

**Can I use it for one project only?**

Yes. Start with the project delivery workbook and the templates for your current stage.

**Is it legal or financial advice?**

No. The templates are practical starting points for management decisions. Have policies and contracts reviewed against the law that applies to your company.

**Who can use it?**

You and your colleagues, inside your own organisation. Advisers need one licence per client organisation. Please do not resell or republish it.

## Working files from an experienced CIO, ready for your next meeting.
