Note: This is a draft of the second version of Comments are welcome! uses the simple process you see in the diagram above. This process consists of 33 management activities in 7 groups. You can click on any of the activities in the diagram above to open its page, or simply start with the first activity, A01.


Everything done in a project should follow the Nearly Universal Principles of Projects (NUPP). The itself has been designed to comply with NUPP as well.


There’s one management team responsible for the project management activities, with one or more team members, depending on the size and complexity of the project. The project manager is the head of this team, accountable for the project management activities. This person reports to the sponsor, who’s a senior manager responsible for the final outcome of the project, for funding and resourcing it, etc.

There’s one or more production teams in the project. Each internal production team (one with team members from your own company) is lead by a team leader, who reports to the project manager. Each external production team (suppliers) is lead by a supplier project manager who reports to the project manager.

If the project is being done for an external customer, there will be a customer project management as well.


The following are the documents defined in

The templates can be used as they are, or as guides on how to set these documents up in your own system.

It’s important to have a central place for your project documents, with scheduled backups, remote access, and authentication and authorization. If your company doesn’t have such a platform, you can use one of the following open-source, privacy-aware solutions:

If the team is not co-located, you will also need a team chat platform. The following are a few open-source, privacy-aware options:

It’s important to capture risks, issues, and change requests in the Follow-Up Register immediately. Therefore, you need to set up the system in a way that makes access to the register as easy as possible, including access from your mobile phone. If it’s not possible, use a personal journal to record them, and then transfer them to your register as soon as possible. The following are a few open-source, privacy-friendly note taking applications you can use as a proxy:


You can make changes to to better match it to your environment. However, be careful not to harm the internal consistency of your system when doing so, and keep your system simple. It’s usually better to start with the original form of, and adjust it very gradually in response to your needs, and refine those choices by inspection and adaptation.

We have plans to prepare various themes for, each of which will tailor the general system for a certain type of project. The following are planned so far:

Each theme is developed by at least 3 experts from the domain, and one or more facilitators from the core development team of If you’re interested in joining one of the teams above, or have an idea for a new theme, feel free to contact us at


If your project is for internal use and you have no external customer and no external suppliers, then there will be only one perspective to the project. Otherwise, each organization involved in the project will have its own perspective. Everything in should be seen from your perspective to the project; e.g., when you’re describing the justification of the project in the project description document, describe your own justification, and not that of the external customer. is not one system to be used by every party involved in the project, but a system you use for managing the project within your own boundaries.

In addition to the documents, the perspective should be considered when thinking about the roles as well. You may be the “project manager” from your own perspective, while you will be considered a “supplier project manager” from the customer’s perspective and “customer project manager” from your suppliers' perspective.


The first version of was published in June 2016, followed by two minor revisions in 2018 and 2020. The draft of the second version of is published in March 2021. It’s open to public comments at this moment. Its final version will be published in May 2021.

Subscribe to the newsletter

Downloadable PDF of the manual


A - Project Initiation

B - Monthly Initiation

C - Weekly Management

D - Daily Management

E - Monthly Closure

F - Project Closure

G - Post-Project Management

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

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