Project Initiation Weekly Initiation Daily Management Weekly Closure Project Closure Post-Project Management Identify the high-level decision maker(s) A1 Understand and distribute the hats A2 Select tools and create a project repository A3 Create a common understanding A4 Have Project Initiation peer-reviewed A5 Make a go/no-go decision A6 Conduct a focused communication A7 Revise and refine the common understanding C1 Have the Weekly Initiation peer-reviewed C2 Make a go/no-go decision C3 Conduct a focused communication C4 Manage follow-up items D1 Close completed deliverables D2 Measure and report performance E1 Evaluate stakeholder satisfaction E2 Capture lessons and plan for improvements E3 Consider swapping hats for the week E4 Double-check and hand over the final output F1 Evaluate stakeholder satisfaction F2 Have the Project Closure peer-reviewed F3 Consider swapping hats for Post-Project Management F4 Archive the project documents F5 Celebrate! F6 Conduct a focused communication F7 Evaluate the benefits G1 Generate new ideas G2 Conduct a focused communication G3

D2 - Close completed deliverables

Custodians add comments to their deliverable cards on the Integrated Project Board, and eventually, move them to the “to-review” column when they are completed. Then, it’s time to make sure each deliverable is really complete before moving it to the “closed” column, because we can only reduce risks and create a comfortable environment if what we call complete is really so, and we’re sure that not many of them will require extra work in the future.

Creator Hat

Is creating the deliverable really completed?

Investor Hat

Is the deliverable compatible with our goals?

User Hat

Is the deliverable compatible with user needs and expectations?

When it’s agreed that everything is fine with the deliverable, it should be moved to the “closed” column.

Project Description Deliverables and Follow-Up Items Queued In-Progress On-Hold To-Review Closed Why this project? Requirements Targets and forecasts Stakeholders

If the project has an internal or external customer, it’s a good idea to show them the completed deliverables for feedback and an unofficial, preliminary approval. This will make Project Closure a lot easier and reduces the risk of rework.

Project Manager Hat

Are we working on too many deliverables at the same time?

Having too many in-progress deliverables increases the risk of rework. Instead, we should focus on completing deliverables before moving on to new ones. The Project Manager hat is responsible for encouraging everyone to do so.

Don’t forget the usual concern:

Project Manager Hat

Are the documents clear and easy to understand?

Downloadable manual in PDF
Standard slide deck for trainers
Activity List (+)

Thanks for sharing your opinion with us. Please note the following:

  • Please write it briefly and clearly.
  • Feel free to write in any language you prefer.
  • If you have multiple suggestions, please submit them separately.

If your suggestions inspire a positive improvement, we’d be happy to credit you as a contributor (if you provide us with your name and email address in this form).

To distinguish you from random bots on the Web, please enter the number of activity groups below.

If you like, you can share your name and email address with us, in case we need to talk to you about your comment, or give you credit as a contributor: is non-proprietary, open, and free for everyone. is designed for micro projects with 1 to 7 team members. For other projects, it’s best to use the regular