A basic definition of the Project Management Officer's role and a review of the PMO's main activities.
Over recent years, the PMO approach is gaining popularity, with many organizations acquiring experience in applying this
function and appreciating its benefits. Yet for many, this is an unfamiliar term, while others only have a cursory understanding
of the advantages and benefits that a PMO can bring to their organizations. For the benefit of all those that are unfamiliar
with this approach, here is a basic description of both the approach and its advantages.
PMO typically stands for Project Management Officer - the person in an organization, group, division or department who is
responsible for the definition and / or implementation of a diverse range of project management fields, with a special
focus on planning, monitoring and controlling the progress of project schedules.
In some cases, especially in large organizations, the PMO is in fact a group of people who share this responsibility:
Project Management Office.
Major activities of a PMO:
Assistance in planning project schedules:
Collecting data from various parties involved in the project.
Defining a list of tasks, dependencies and priorities, and allocation of resources for these tasks.
Preparing a work plan / Gantt chart for the project.
Ongoing tracking of project schedules that may include:
Collecting performance data independently (manually) or via pre-defined reporting mechanisms.
Updating schedules according to the data collected.
Identifying short and long term problems, based on updated data and the forwarding of warnings to appropriate parties. In some cases the PMO may also propose solutions.
Assistance in preparing for and conducting periodical tracking / status meetings.
Assistance in assessing the implications of changes to project definitions.
Monitoring of other subjects for handling: these are sometimes referred to as "action items", "open issues" or simply "issues". This is usually a long list of tasks that for various reasons are not included in the Gantt chart, yet their completion is vital for the success of the project.
Planning and monitoring project budgets: repeating the steps described above in relation to budgetary issues (required only for some projects).
Definition and tracking of the relationship to other schedules / plans that impact on the project/s for which the PMO is responsible. This responsibility covers, among others, connections between the various parts of a single project or between various parties in the organization who are involved in the project.
Serving as a knowledge center for the use of project management tools
Possible additional activities of a PMO:
Defining / updating methodologies.
Defining / updating processes.
Additional issues related to coordination between projects (such as sharing information, establishing / maintaining joint databases).
Maintenance of relevant IT systems (such as Microsoft Project Server).
Post Mortem reviews of completed projects.
Assistance to QA personnel.
Why do we need a PMO?
Some organizations, especially those who still lack project management culture, attempt to assign PMO tasks to
overburdened project managers. In large and / or complex projects, it is often the case that project management in itself i
s a sizeable and complex task that a single individual finds difficult to cope with. The direct result is that many of the tasks
listed above are not executed, or are executed only very partially.
As a result, various difficulties arise that accumulate and mount as the project progresses, and finally these problems
often severely impact the very realization of project goals (schedules, budget, content and quality of results).
The role of a PMO is to handle the tasks described above, while freeing the project manager to concentrate on his/her
primary role - leading the project to its successful completion.