Project Initiation Monthly Initiation Weekly Management Daily Management Monthly Closure Project Closure Post-Project Management Appointthe sponsor A01 Appoint theproject manager A02 Appoint thekey team members A03 Describethe project A04 Identify and planthe deliverables A05 Identify risksand plan responses A06 Have project initiationpeer-reviewed A07 Make ago/no-go decision A08 Kick offthe project A09 Conduct afocused communication A10 Revise and refinethe plans B01 Have the monthlycycle peer-reviewed B02 Make ago/no-go decision B03 Kick off themonthly cycle B04 Conduct afocused communication B05 Measure andreport performance C01 Plan responsesfor deviations C02 Kick off theweekly cycle C03 Conduct afocused communication C04 Manage risks, issues,and change requests D01 Acceptcompleted deliverables D02 Evaluatestakeholder satisfaction E01 Capture lessons andplan for improvements E02 Conduct afocused communication E03 Hand overthe product F01 Evaluatestakeholder satisfaction F02 Have the closing activitygroup peer-reviewed F03 Archive theproject documents F04 Celebrate! F05 Conduct afocused communication F06 Evaluatethe benefits G01 Generatenew ideas G02 Conduct afocused communication G03

G02 - Generate new ideas

This management activity belongs to the post-project management activity group: a 3- to 6-month cycle of activities that start after the project ends and continues for 1 to 5 years. This activity group may be merged with that of other finished projects in a central portfolio management system.

The same person who was the sponsor for the project is responsible for this cycle, unless this responsibility is transferred to someone else.

After evaluating the benefits (G01), the sponsor should check to see whether there are any ways of increasing them. The result may be small activities assigned to the operational teams, or major changes that can become new projects in the future.

Purpose

The main work for the project is done, and you deserve to benefit from it. However, some potential benefits are not realized automatically unless you take extra ad hoc actions after the project closure, and we don’t want to miss this opportunity.

On the other hand, evaluating the benefits of previous projects is a great source of ideas for future projects, and it’s best done in a structured way.

Common pitfalls

Consider the following to avoid some of the commonest problems in this area:

Principles

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



⊚ Download the manual in PDF

⊚ Download the diagram


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 approximately 1 to 7 team members.