Institutionalized Process
One of the challenges, in any organization, is to get all the players to follow the process. So, P3M Engine was designed to meet that challenge.
A critical success factor for large projects and programs is consistency. Consistency enables comparisons and it simplifies what must be remembered to manage effectively. If a program has 10 projects in it and they all report on different elements of their projects or they report on the same elements but measure them differently or categorize them differently, there is no way to make comparisons. There is no way to establish a norm. It is difficult to set expectations across the program. There is confusion understanding the progress and health of any project, as leadership tries to remember which measuring protocols belong to which projects.
Multiply this inconsistency and confusion when a program is one of several programs in an organization. It makes managing the work very challenging.
Replacing inconsistency with consistency requires several steps.
·Define the process – Defining how everyone executes their work will create the single-source reference. Everyone who executes work should refer to the process to know the right way to execute.
·Communicate the process – A process collecting dust does no one any good. The process must be communicated to those who will execute the process.
·Execute the process – The people who do work must perform that work as prescribed by the process.
These all have their challenges. If you were to take a sampling of organizations who do not execute consistently, you would find interesting phenomena about these three essential steps.
·Many, but not all, organizations define the process.
·Not all who go to the effort and expense of defining a process communicate the process to those who execute the work.
·Not all performers who have the process communicated to them execute in accordance with the process.
How do you overcome these challenges?
·Define the process – Make it mandatory or make it easier, or both. Well managed projects start with documented plans. There should be an overall project management plan with subplans for knowledge areas such as scope management and change control. Documented default copies of these plans come with P3M Engine. This provides a great starting point for each PMO or program manager. You can modify the plans or not. They are already ideal for using P3M Engine.
·Communicate the process – Usually this is done by sending all project managers an email telling them where the documented process is located. It is also communicated one time during onboarding of new team members. More mature organizations may conduct some training. Some organizations follow portions of a process via management oversight and reviews. Often, the documented process is rarely referenced after being produced. In P3M Engine, all project plans are one click away. They are as easily referenceable as any other project information.
·Execute the process – Usually the only way to ensure the processes are being executed is to have regular management oversight and to have stakeholders demand items, such as required reports, that are produced through properly executed process. These techniques are not very effective. P3M Engine overcomes these weaknesses by embedding processes. Whatever is defined in the project plan is executed by the users as they use P3M Engine. They are inseparable. When the project plan defines how to measure risk, that is how it is measured. When the project plan calls for a specific number of change control boards and defines the thresholds of authority for each, then new change requests go to the appropriate change control boards for action, automatically.
Every large project, program and PMO needs consistency to do their work well. P3m Engine helps ensure that needed consistency by taking most of the work out of process definition and most of the risk out of process execution. If you have never enjoyed consistency before, you will be amazed at how much easier work becomes.
See more at http://www.p3mengine.com/institutionalized-process.










