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

F1 - Double-check and hand over the final output


The first thing we need to do in the Project Closure activity group is double-check to ensure the final output of the project is complete and matches the expectations.

Project Manager Hat


Are all the cards on the Integrated Project Board closed?

Creator Hat


Is everything working the way it should from a production point of view?

Investor Hat


Have we achieved the project goal?

Have we satisfied the business expectations?

User Hat


Have we satisfied the requirements and the users' needs and expectations?

If we need to do more before ending the project, you should return to C1, and otherwise, to F2.

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

Sometimes, a limited set of unfinished cards on the board might be closed by transferring them to a maintenance team. In these cases, they should be marked as “transferred” and moved to the “closed” column.

Creator Hat


Do we need to prepare any additional information for the maintenance team?

When there’s a customer, the following considerations are important:

Project Manager Hat


Do we need approval or an official handover before ending the project?

Have we properly documented the closing approvals and similar documents?

When working with external customers, it’s a good idea to document key communications for future reference.


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 micro.P3.express 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:




micro.P3.express is non-proprietary, open, and free for everyone.

micro.P3.express is designed for micro projects with 1 to 7 team members. For other projects, it’s best to use the regular P3.express.