In these days, I am busy with the building of a system for supporting the PMO via web. In this phase, most of the job consists in the preparation of “standard” templates. They represent the iceberg’s tip; however, the templates are tangible things that will be delivered to the PM. Their acceptance will make a good start. Nevertheless, it is a long journey.

Alphabet and templates

Like the first school’s days, gaining the ownership of the letters gives a strong emotion. It seems that the ability to put those powerful symbols in the right order empowers the writer.

Neat forms that are ready to receive our viewpoint of the current situation seem to offer strong frameworks. This kind of structure can shelter us for a while; just the time to act properly and carry through a couple of issues (e.g. delays).

Pictures and movies

Templates and diagrams (e.g. Gantt) are often used for freezing the running reality. Often, most of the energy spent by PM is dedicated to produce the best possible picture, forgetting that a project needs movies, the best are the documentary type; at least the paying public knows the result of their (in)actions.

Forms and knowledge

More complex is the task, less easy is to create or choose the correct tool (e.g. template). Any decision has to be taken within a proper frame (PMP, Prince2, Agile family) and much more important discussed and approved by stakeholders.

Documents are destined to increase the quality of communication. The information they store is valid until it describes the existing situation.

Templates available

Today there are two more templates:

Issue report

Risk Management register

The policy is to build all meaningful (from my viewpoint) documents; the next phase will involve the final users that, having available the whole set (templates, diagrams and mind maps) can offer their opinion for further improvements.