Why Project Managers Use P3M Engine
I can remember preparing project status reports manually. It took a couple hours to collect information and copy and paste it into a status report. Then you had to adjust the formatting so it would look good. If you were lucky, you only had one report to do. I have had as many as five stakeholders, each with a different status report format they wanted.
Fortunately, project managers do not face that anymore if they have a tool like P3M Engine they can use. P3M Engine provides several ways to reduce the workload on Project Managers and improve the accuracy of status reports. These include:
·Automated Data Load
·Configurable Content Type
·Multiple Stakeholder Support
·Configurable Inclusion
·Hierarchy Support
Automated Data Load – P3M Engine status reports are a combination of quantifiable data that is pulled from the system, and subjective content written by the Project Manager. The system data is automatically loaded to a new status report. The data is unalterable and accurate. The Project Manager is unencumbered by the retrieval of all this system data. Project Managers now do what they should be doing—commenting on the data.
Configurable Content Type – Many different types of content can be loaded into a P3M Engine status report. This includes risks, issues, decisions, change requests, deliverables, milestones, and dependencies. Typical information will include data such as title, due date, and health flag. You can configure which content types are included and which are not. If the system finds any included content type to have no relevant records, then the content type is left off the report.
Multiple Stakeholder Support – Part of the beauty of having Automated Data Load and Configurable Content Type is that you can now prepare as many different status reports, in differing formats, as you like. Different report formats can be prepared, including any content type in a variety of locations on the report. The Project Manager’s subjective comments are stored in a single location, like the rest of the data. Now you are setup to publish status reports of varying formats with the click of a button. Bring on the stakeholders.
Configurable Inclusion – Not everything should be showing up in a status report. For each content type, the Project Manager has the capability to mark what should be reported. For example, the Project Manager may be tracking 20 risks, but only three of them warrant the attention of stakeholders and should appear on a status report. The Project Manager will mark those three risks as visible and only those will appear on the status report.
Hierarchy Support – The Project Manager can also mark at what level an item should be visible. So, in the example above, if one of those three visible risks has been escalated and needs to appear in the program status report, the Project Manager can mark it as Program level. In that case it will appear in both the program status report and the project status report. It needs to be visible in both places since it is managed by the project and escalated to the program. P3M Engine tracks this and takes care of it for you.
P3M Engine does what a software system is supposed to do. It enables users to execute processes faster and more reliably with less effort and less cost.
For more information see http://www.p3mengine.com.










