project management - ITM Platform | Projects Programs Portfolio

Everyone´s starting point is different, but we can all agree you need a steady foundation when building anything and your PMO´s framework is no exception. It should be clear and shared by the entire organization. We’ll guide you through planning, implementing and disseminating your PMO. Whether you´re familiar with ITM Platform or not, our examples are a ¨one-size-fits-all¨. This design assists in highlighting situations that you may encounter along the way and applicable to most cases.

So, let´s dive in to the 6 essential elements you need to consider in order launch your PMO framework.

Download the eBook: How to set up a sustainable PMO with ITM Platform

1. Project types

First, decide what kind of projects you’re running; the type of project will also govern its lifespan.
As you implement (or relaunch) the PMO it’s a good moment to reflect on the variety of projects in the portfolio and possibly take time to redesign them. A PMO can also manage operations if they consist of specific tasks that are assigned to different teams. Managing projects and operations together from the PMO is especially useful when the resources and clients involved are the same.

This is the case with software development projects, or products that require maintenance by the same team that developed the original project. The Kanban methodology is useful for managing services because it offers an organized structure in which you can see the status of tasks at a glance. More importantly it allows you to limit the flow of work according to your resources.

The service concept is also incorporated into ITM Platform – you can create entities for the sole purpose of managing operations.

2. Workflows

A workflow allows you to map out all the possible statuses that a project goes through. Make sure it is based on the business’s procedures – don’t be tempted to invent statuses that do not reflect the reality of the company.
The workflow is defined by two main components:

The changing status of a project
For example, we can decide that when the status of a project is designated as ‘draft’ that can only be changed to ‘started’ or ‘discarded’.
The conditions for changing the status and who is authorized to grant permission for that change.
Make the conditions for changing statuses as simple as possible; you can always increase the complexity later, and you may even find that there is no need to do so.

A word of advice: do not replace the work of defining organizational procedures with a workflow. The workflow should be a conveyor belt, not a control mechanism.

3. Priorities

It's very easy to configure the different degrees of priority, but the work of a PMO starts way before this: you have to agree what each priority means. It should be extremely clear what “high priority” or “medium priority” means. Obviously, medium is higher than high, but does that mean that you shouldn’t start with the medium priority ones until the high priority ones are finished? Should we put twice as many resources into high priority versus medium priority?

The PMO should know the actions associated with each priority and make this clear to everyone else so that the organization makes homogenous decisions.

4. Risks

Good project management is in essence risk management and a PMO ensures that this function happens consistently throughout the decision-making process.
The formula impact x probability = exposure level is only useful if it leads to consistent decisions by project managers.

Identifying risks is a tricky business as it’s often subjective and affected by personal bias. The PMO standardizes procedures using criteria and tools approved by the board, backed by the project managers.

5. Waterfall or agile methodologies?

Both of these methodologies can co-exist in one integrated portfolio as long as the PMO establishes criteria to decide on the appropriate methodology for each project.
Some organizations make all decisions – waterfall or agile – based on politics. This kind of decision making can lead to patchy results.
If your organization decides on agile methodologies for all projects – while at the same time demanding medium and long-term deadlines – the methodology probably hasn't been chosen on the basis of solid criteria.

To determine which methodology to use the PMO should ask:

Is the result of the project relatively uncertain or are we well aware of the outcomes?
Is the project subject to deadlines which govern the date of deliverables or is a short-term vision of all the tasks enough?
Are sponsors and clients willing to have continual involvement in the project without knowing the final outcome? Or will they happy to be less involved and just accept the final outcome?

If your organization decides on agile methodologies for all projects – while at the same time demanding medium and long-term deadlines – the methodology probably hasn’t been chosen based on solid criteria.

6. Project templates

One of the major benefits of a PMO is that it allows you to capitalize on knowledge accumulated from previous projects. Be sure to put mechanisms in place to recover the lessons that have been learned. That way the know how isn’t lost when the project ends but can be applied later on.
Creating project-specific templates means the contents can be re-used in future projects. Another benefit of templates is to re-use frequently used structures just by changing dates and figures. It’s similar to those cooking programs when the chef says ‘here’s one I prepared earlier’.

A good PMO ensures that the knowledge stays within an organization, and not only at the level of the individuals involved.

This online PMO & Organization Self-Assessment can help you get started and analyze your organization.

Planning and implementing a PMO has a rhythm of its own. Don’t be tempted to rush. You risk chaos if the process rushes ahead of the organization’s own maturity by trying to tackle all the stages at once.

Download our new eBook: How to set up a sustainable PMO with ITM Platform

So what can businesses and project managers do to ensure essential components of projects are being completed in time and on budget? In this article we develop the 5 main keys of success.

Keys to success

A good plan is only useful if it can be implemented in the field. For that you need adequate resources and a favorable environment. Before creating a PMO:

1. Make sure you have the right skill set

Ensure that your people have the right skill set. If you have neither the team nor the required skill set, it’s a good idea to limit the scope of the PMO so that it can be set up without the risk of failure. Embarking on a PMO without the appropriate know how is like setting sail on a ship without skilled sailors, the enterprise will unravel at the first ill wind.

2. Start with high-visibility, high-impact projects

Like every other business unit, the PMO must prove its worth from the very beginning to win over naysayers. A smart PMO manager will look to deliver early wins on to the scoreboard. This is not always easy because of its cross-functional – and according to detractors – unnecessary nature. Tackle the most widely acknowledged problems first.

3. Identify the needs of the business clearly

The organization and the business have needs that may or may not have been explicitly identified. Meeting these needs should be your starting point. That way you’ll start off on the right foot, giving you enormous leverage when it comes to defending your decisions in the future. Do your research.

For example, as a PMO expert you may consider it vital to set up a document template repository. But maybe what your stakeholders actually need is a way to decide how progress on projects is measured.

4. Have a solid framework

And which is integrated into the business. A PMO that acts as a lone wolf is destined to fail. It is important that there are simple, fluid communication channels to ensure that everyone is working in the right direction. Put these in place from the outset.

5. Draw up clear key performance indicators

Having a lot of indicators does not necessarily mean having lots of information. Make sure that you not only have the right tools but also that the KPIs are relevant to your business.

What to consider for a consistent roadmap

To create a consistent roadmap, you should take into account:

The maturity of the organization.
The goals suggested by the Board of Directors.
The available resources.
Positive and negative environmental factors.

With these parameters, we know our start and end points, the resources available and the pace at which we should go.

An example of a roadmap

Let’s take as an example Booksy360, a mid-sized publishing company. This is their roadmap divided into four stages, starting from a tactical PMO and moving towards a strategic one.

Period 1

Booksy360’s PMO steering group decides to establish a basic communication system, using a common language. In this system planning is based only on timeframes and deliverables. Document templates are created for each project type. Stakeholders will receive reports about the status of their individual projects and Booksy360’s board will be kept up to date via a regular portfolio report.

Period 2

All communication channels are now established. The PMO encourages collaboration between units and projects. Inventory and purchasing are added as extra elements to plan, manage and control. Resource management is now based on professional profiles, such as editors, writers and production engineers.

Period 3

Formal risk management starts, agreed by all departments. Alongside this Booksy360 initiates change and quality management. Even if these were taking place informally before, now they are at the heart of the process.

Period 4

The final stage is when the actual strategic contribution starts. But it is long way down the line so for now Booksy360’s steering committee predicts it will include portfolio planning, benefit realization management and governance

The online PMO & Organization Self-Assessment may help you analyze your organization.

When we think about Project Management Office, a project management software is pretty much a necessity. However, there are many other solutions that can make the life of a project manager easier in several facets from productivity to communication. In our last article on apps for PMOs we introduced the first 7 software applications, today we continue the list by presenting you with another 6 tools that will make your work easier and faster. Thank us later ?

1. Airtable

Combine Excel, Pinterest, Trello and a database management system and you have Airtable. No jokes. Airtable is an extremely powerful solution that enables you to visualize the same data in various ways: table, Kanban, blocks (Pinterest style), calendar and forms. It’s so versatile that it can be used for almost any activity that requires a database.

Pros

Airtable is powerful and flexible. It allows you to manage in a single location the data you probably would have separated into different areas. For example, you can use it for demand management in conjunction with ITM Platform. You can create an internal form for project proposals from employees, a table view for project managers to manage the proposals, and a blocks view accessible to the whole organization to inform of the selected projects. Airtable is also customizable with “blocks”, a premium feature that allows users to add new functionalities to tables.

Cons

While great for managing, Airtable is quite poor on the communication side. While there’s the possibility to comment on each line of the table, that’s the extent of its communication capabilities given that there’s no chat feature .

2.Visio

If you have ever needed to design a flowchart or a diagram you are probably going to love this one. Microsoft Visio is a diagramming and vector graphics application that is used to design charts swiftly and easily.

Pros

Apart from being easy to use, Visio is part of the Microsoft Office family of solutions, which means that it is perfectly integrated with other common solutions like Word or Excel. It also allows users to design 3D map diagrams and to pull information from external sources that can update automatically.

Cons

The main issue of Visio is its compatibility as it only works on Windows. Furthermore, it doesn’t allow for real-time collaboration, without mentioning the hefty price tag (considering that it is unlikely a software you’ll use every day).

3. PMO Value Ring

The PMO Value Ring is the perfect software to use in conjunction with a project management software. The software is designed by PMOs for PMOs and is aimed at providing a consistent framework to manage the PMO across different stages of its life cycle.

An example of a complete cycle in PMO Value Ring:

Pros

The tool forces the user to be consistent in the definition of the PMO and all its elements, such as Functions, Roles, Stakeholders etc. All the data can be accessed in a consolidated dashboard view that scores several different aspects like ROI or maturity.

Cons

The downside of the PMO Value Ring is that it is not integrated with any other solution, which means that all the data should be inputted manually. Furthermore, the software enhances and facilitates the management of the PMO but it is separated from the actual project management activity of the office.

4. ClicData

ClicData is a very powerful data visualization and BI software. It allows users to create and share dashboards that are automatically updated from the data source.

Pros

Clicdata is integrated with almost anything, at least with all the main apps used for business. This is great as it allows to create dashboards that can then be shared with, for example, a director or CxO, that needs to have access to live data. Another strength of ClicData is that it permits cross-evaluation of data or automatic database merge.

Cons

The interface is drag and drop but this does not mean that it is easy to use: the logic behind the interface is not always the most intuitive and the user needs to have a clear understanding of the structure of the data imported, which is not always bvious when importing data directly from a third-party source. Also, more complex dashboards require some time to set up so ensure to allocate enough time when implementing ClicData.

5. Sharepoint

I’m sure many of you are already familiar with SharePoint. For those who don’t know it’s a web-based collaborative platform that is primarily sold as a document management and storage system. But the product is highly flexible and usage varies substantially between organizations. Sharepoint is commonplace in larger organizations where the document management is complex and encompasses several departments.

Pros

The main advantage of SharePoint is in its document management capabilities: given its configuration capability you can create several Site Collections, limit their access, from one single, clean interface.

Cons

The main cons of SharePoint are tied to its main strength: as a consequence of being highly configurable Sharepoint is quite complex to manage in its full capability, meaning that you’ll often need to dedicate human resources or hire a consultant.

6. Risk assessment matrix

Good planning is essential, so that project managers and the respond to the emergence of risks. ITM Platform’s Risk Assessment Matrix evaluates risks depending on their impact and probability, allowing to visualize the level of risk exposure. Thanks to that information, you can prioritize risk management and reduce exposure!

Pros

This matrix allows you to register, quantify and share risks and you can share them collaboratively as well.

Cons

The tool can only be accessed online and only covers the risk management part of a Project manager work routine. However, if you need a more integrated application you can try ITM Platform, where the risk management functionality is integrated with a whole set of their features… What do you think of these 6 tools? Are there any that you’d like to see covered that are not in this list? Let us know

Receive the latest blogs directly into your inbox

This article is part of a series on the PMBOK areas of knowledge. You can read the previous articles here:

The last area of knowledge of the PMBOK (Project Management Book of Knowledge) covers the best practices to manage the relationship with stakeholders.

Specifically, this area of knowledge focuses on identifying people, groups or organizations that may affect or may be affected by the project and analyze their expectations and its impact on the plan.

Manage project stakeholders in a collaborative environment

It is essential to keep in mind that clients too are stakeholders, as their satisfaction is crucial to the success of a project. This means that projects could re-start from 0 if the client’ expectations are not taken into account early enough.
This problem was so frequent in software development that led to the development of agile methodologies, which seek a fluid communication with customers.

Advice for Stakeholders Management

1. Identify the parties or public interested in the project

In this phase of project management, it is important to focus on identifying the stakeholder from the very beginning, since this will allow us to obtain an overview of the stakeholders map and the problems that some actors may pose at a later moment.

2. Make sure that all interested parties agree and know their roles or responsibilities

Before starting the development of a project, it is essential that all the actors involved know the rules and assume the commitment and responsibility expected of their functions. From the beginning, we will identify team leaders, work teams, and their roles.
Good pre-planning facilitates a smooth development and helps to avoid conflicts in the future. If everyone agrees with the requirements and objectives, he or she will work to keep pace with the events and avoid delays; delays that only will be translated into extra costs and unwanted results.
On the other hand, rules must also ensure fluid communication with customers, so that they have sufficient information to evaluate the project development and express their point of view. If necessary, the circumstances under which a client’s opinions may involve changes in the project can be agreed upon.

3. Get consensus on the application of changes to the project

Changes in a project are inevitable since contingencies always arise that require the modification of some criteria or change in scope. The more complex a plan is, the more susceptible it is of being changed during its development. Therefore, it is important that all participants agree on how to handle the changes.

4. Favor communication

Establishing communication guidelines at the beginning of the project will improve the flow of the same. The team will be able to determine, since the beginning, the frequency of the communication and its content, that should preferably be concise and focused on the progress or issues that affect the project.

5. Give permanent visibility to the project teams

Transparency is a fundamental virtue in all project communication. It does not make sense for a project manager to have secrets.

It is important to define and communicate the vision of the project early on, as teams become more involved and the risk of losing focus on the project is mitigated. This way you make sure that any decision is coherent with the vision and objectives of the project. This point is very important because it helps reduce risks, errors or loss of focus.

6. Involve interested parties in the entire process

Although we assigned functions and teams from the very beginning, interested parties (stakeholders) should be always involved, so that they can participate in the problem solving or the revision of the requirements.

7. Reach an agreement with what has been done

In order to avoid entering a circle of changes and stagnation that could jeopardize the development of the project, it is important to reach agreements on the work done.
In an organization that manages strategic projects and internal transformation, Stakeholders Management goes beyond the project closure, since its delivery enables capacities that could benefit other levels of the organization. Otherwise, the value delivered is not internalized and won’t become a competitive advantage sustainable over time. This approach has been called Benefits Realization Management (BRM) or Benefit Management.

8. Empathize with the other interested parties

All project participants are stakeholders, but the stakeholder map also includes parties that do not actively participate in the development of the project. You should take them into account and empathize with them as the capacity for empathy is a crucial skill for the success or failure of a project.
The analysis of a project should not be limited to the interests and influence of stakeholders but should include how to identify their objectives, circumstances and the way they perceive the project.
Empathic analysis helps us to discover hidden variables that show us the way to solve problems or overcome obstacles that we may encounter.

Receive the latest blogs directly into your inbox

Project based management is a widely spread practice in the business world because of its effectiveness in generating competitive advantages. However, it cannot be effective without the support of a strategic project management office (PMO) that actively helps define corporate strategy.

Unfortunately, project management is not applicable in the same way in every organization because companies do not all share the same processes, functions or need for oversight (what we call "maturity" in project management).

Take your PMO to the next level of maturity with ITM Platform, try for free now.

For this reason, we distinguish between different levels of maturity according to the workings of the project office, from the most basic to the true strategic PMO:

Low maturity of a strategic PMO: Inventory and control

In corporate environments it is essential to make an inventory of all the initiatives that are under way. That is the mission of a PMO of low maturity: to gather and consolidate information about all the projects and other relevant activities to report where resources are being invested.

Medium maturity of a strategic PMO: coordination

The next step for a PMO is to have the ability to forecast problems and, consequently, to tackle them. This function is common when the PMO coordinates the resource allocation. For example, during periods when there is a high volume of work, it is the PMO that should be aware that projects are accumulating and identify bottlenecks.

A PMO of medium maturity aims to improve the efficiency of the organization, recognizing possible conflicts in the planning process and proposing solutions.

High maturity of a strategic PMO: strategy and business

The highest maturity of a PMO is achieved through a fit with the corporate structure that makes it the right hand of the Board of Directors. This fit implies a governance model where strict methodologies are followed while the most important practical decisions are taken, precisely, based on the information that the PMO offers.

In these cases, the project office becomes a key element for the corporate strategy to become a reality.

Strategic questions for a high maturity PMO

A strategic PMO should be considered as an internal service that offers practical information, answering questions like:

What is the status of the project portfolio?
Are resources scarce? Does this shortage affect cashflow?
Are we executing projects that are no longer worthwhile?
Which proposals or ideas will improve the current portfolio?
What kind of new processes can be implemented as a result of the experience acquired from past projects?

However, this approach does not allow a PMO to fully develop its potential. Strategic PMOs have a proactive spirit: they collaborate with the management in strategy development and manage all project-based work.

While PMOs should be empowered, at the same time they should leave the most important decisions to management. For example, if a protocol is put in place requiring the cancelation of projects with a budget greater than a certain amount (for example, € 500,000), it makes sense to warn directors beforehand allowing them to authorize or indeed veto the final decision.