Project Initiation Monthly Initiation Weekly Management Daily Management Monthly Closure Project Closure Post-Project Management Appoint the sponsor A01 Appoint the project manager A02 Appoint the key team members A03 Describe the project A04 Identify and plan the deliverables A05 Identify risks and plan responses A06 Have project initiation peer-reviewed A07 Make a go/no-go decision A08 Kick off the project A09 Conduct a focused communication A10 Revise and refine the plans B01 Have the monthly cycle peer-reviewed B02 Make a go/no-go decision B03 Kick off the monthly cycle B04 Conduct a focused communication B05 Measure and report performance C01 Plan responses for deviations C02 Kick off the weekly cycle C03 Conduct a focused communication C04 Manage risks, issues, and change requests D01 Accept completed deliverables D02 Evaluate stakeholder satisfaction E01 Capture lessons and plan for improvements E02 Conduct a focused communication E03 Hand over the product F01 Evaluate stakeholder satisfaction F02 Have the closing activity group peer-reviewed F03 Archive the project documents F04 Celebrate! F05 Conduct a focused communication F06 Evaluate the benefits G01 Generate new ideas G02 Conduct a focused communication G03

A07 - Have project initiation peer-reviewed

This management activity belongs to the Project Initiation group. This group of activities are run at the beginning to prepare us for the project.

At this point, initiation is almost done, and it’s time to ask another project manager in your organization to help you by peer-reviewing your management activities. You should add the result to the Health Register.

If the score is too low, you may need to spend more time on the previous management activities before moving on to the next ones, but more importantly, you need to find the root cause and see how you can prevent low scores in the future.

Health Register template

Purpose

The main purpose is to pause and check whether your management activities are OK. Having an external person check your work is beneficial because you may be too close to the work to see some of the issues. Furthermore, this is an opportunity for people who manage different projects in the organization to see each other’s work and learn more in the process.

Common pitfalls

A common risk is that the person reviewing your work may hesitate to point out problems, fearing that it may be taken personally. It’s up to you to create a relationship that ensures them they can be comfortable and honest.

Principles

The following principles play a significant role in this management activity:



⊚ Download the manual in PDF

⊚ Download the diagram

⊚ Subscribe to the announcement emails

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 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:




It's best to use micro.P3.express instead of the regular P3.express if you have micro-projects with 1 to 5 team members.