← All decks

Project Delivery Patterns

Deliver projects on the date you promised.

Methods for taking a project from a promise to a finished, handed-over result, in software or any other field. For project managers and team leads, the cards cover agreeing scope, breaking the work down, finding what really sets the date, tracking risks and dependencies, reporting status honestly, controlling change, rescuing a slipping project and closing it on purpose.

48 cards · 8 suits · 5 recipes · 2 missions

What's inside

• Define6Is it clear what done looks like?
• Break Down6Can you hand the work out in pieces?
• Schedule6Have you found what really sets the date?
• Risk6Does every serious risk have an owner?
• Report6Would your status survive a hard look?
• Change6Can you say yes to change without losing control?
• Recover6Is the plan honest about where things stand?
• Close6Have you finished on purpose and handed over?

A few cards

Define

Project On A Page

One sheet that says what the project is for, what it costs, when it ends and who owns it.

Schedule

Precedence Diagram

Draw which tasks must finish before others can start, and the real plan appears.

Report

Colours With Rules

Write down what red, amber and green mean, so nobody can negotiate the colour.

One card in full

Recover

Health Pause

Before you replan a struggling project, stop for a short, honest look at where it really stands.

When a project starts slipping, the reflex is to push harder or produce a new plan by Friday. Both build on the same misunderstanding that caused the slip. A short pause for an honest assessment costs a few days and saves the next plan from failing the same way.

How to use it

1. Agree a short window, typically three to five days, and tell the sponsor what you are doing and why.
2. Collect facts: deliverables actually accepted, spend to date, open issues, and the forecast trend from the Milestone Trend Chart.
3. Interview people one to one, including the quietest. Ask: "What is really going on? What would you change?"
4. Bring in one person from outside the project to read the evidence with fresh eyes.
5. Write a two-page finding: where you stand, the three biggest causes, and what must be true for any new plan to work.
6. Only then start replanning.

Example

A hypothetical software team three months late takes a four-day pause. The interviews reveal that the test environment has been broken for six weeks and everyone assumed someone else had reported it. Fixing that becomes the first line of the new plan.

Watch out

• Letting the pause become an inquiry about who to blame. People will stop telling you the truth.
• Pausing for weeks. A short stop gives clarity; a long one gives up momentum. Follow it with Re-Estimate From Zero and Reset Conversation.

Recipes

• Bring It Back On Track: Recover a late or over-budget project: pause to see where it stands, re-estimate what remains, find what sets the date, lay out the levers, compress where it pays and agree one new plan with the sponsor.
• Plan From Outcome To Date: Break the outcome into owned work packages, check nothing is missing, link them in order, find the chain that sets the finish and give the date as a range.
• Say Yes To Change Safely: Handle changes without losing control: fix a baseline, capture each request on a page, price it before deciding, route it to the right approver, count the small additions and reset the plan in the open.
• Start A Project Right: Open a project with one agreed page: its purpose, who pays and who runs it, what is in and out, how finishing will be checked, which constraint bends first and who it affects.
• Status Nobody Doubts: Make status reports trustworthy: colours with written rules, a check on every green, progress counted in finished items, a chart of forecast drift and problems raised with options.

Missions

• Build a risk register that works: from a vague sense that "something will go wrong" to a RAID log where every serious risk has a score, a response, an owner and a tripwire, and every outside dependency has a date and a fallback.
• Close a project properly: from "it's shipped, everyone's moving on" to a signed acceptance, a handover pack, a close-out list with nothing open, three template changes from the lessons and a date for the benefits review.

Related decks

Operations & Process Patterns

Make recurring work run smoothly across teams.

56 cards

Security Awareness Patterns

Spot the scam and report it fast.

63 cards

Contingency Planning Patterns

Keep running when a person, site or system fails.

49 cards

← All decks