Main Page

From P3X Wiki
Jump to navigation Jump to search is a free, extremely simplified project management framework based on PRINCE2® and PMBOK® Guide that you can learn, and start using in your projects in just a few days. Why

Standing on the shoulders of giants: doesn't try to reinvent the wheel. It's primarily based on PRINCE2® and PMBOK® Guide, and benefits from other frameworks such as XP (eXtreme Programming), DSDM®, and Scrum.


  • Down to Earth: is a down-to-earth method you can really use. The fundamental standards are invaluable, but too complex for normal projects that most people just can't use them.
  • Fully Integrated: is a fully integrated package of methodology, practices, and tools. You don't need to worry about finding proper techniques for your project, or find out how you can use normal pieces of software such as Excel to handle PM activities; everything is ready for you.
  • People-Oriented: recognizes that the primary problem in most projects is the human aspects, and therefore addresses them carefully, instead of limiting itself to a mechanical process.
  • Creative Commons: is licensed under Creative Commons: it's free to learn, use, and teach. The framework is community based, and continuously uses the contributions of its members for improvement.
  • 80/20: Perfect is the enemy of good-enough. tries to bring 80% of the perfect PM system by only 20% of the effort. If you aim for the perfect, you'll just give up.
  • Multi-Purpose: is suitable for most small and medium size projects in a variety of industries. Basically, it's for normal projects most of us are dealing with daily.
  • Extendable: uses a minimal core, with optional Addons that make certain parts (e.g. risk management) more advanced. There are also Themes that make is easier to use it in certain industries. Overview[edit] uses a simple Flow you see above. This Flow consists of 37 activities in 7 sections. This page is a quick overview of the Flow, and you can find more information about each activity by clicking on the activity nodes above, or the lists below. is based on gradual planning, instead of upfront detailed planning:

  • A high-level plan is created in the beginning (Preparation section of the Flow)
  • Each month is planned in detail in the beginning of that month (Cycle Planning section of the Flow)
  • The project is managed in monthly Cycles: We start each month by adding details to the existing plan (Cycle Planning section), and end by a few retrospective activities (Cycle Closing section). During the month, there are Weekly Activities for measuring the performance, recovering the deviations, and synchronizing.
  • Daily Activities, mainly for managing RICs (Risks, Issues, and Change Requests).

Besides the cycles, there are three more sections in the flow: Preparation for starting up the project and creating the high-level plan, Closing for ending the project, and Post-Project for tracking the benefits of the project after it’s closed. links[edit]


Preparation starts as soon as you have the idea or offer for the project, and ends with the decision to execute/accept the project, or drop it. Checking the feasibility or possible options for the project happens in this section as well.

Cycle Planning[edit]

Each cycle is a month, and starts by detailing the high-level plan created in the Preparation for the upcoming month. This section shouldn't take more than 3 days.

Weekly Activities[edit]

You can repeat the weekly activities in a certain day of the week (e.g. every Monday). Remember that A17 to A21 should be run in sequence.

Daily Activities[edit]

During Daily Activities; a Project Manager continuously contributes to the project, and teams.

Cycle Closing[edit]

In Cycle Closing section we finalize everything we've done during the month, and prepare for the next cycle.


Closing section, when we're done with the project, or we want to cancel it. In both cases, we need to do a few final things.


Post-Project activities are done by the Sponsor, after the project is finished, when there's no program or portfolio management system to carry on the responsibility. The goal is to keep tracking the benefits of the project. Post-Project activities repeat every 6 months, for 2 to 5 years (depending on the project).