portfolio - ITM Platform | Projects Programs Portfolio

ERPs (Enterprise Resource Planning systems) are the widest and most complex category of business software. As they are dedicated to all kinds of resources management, they must coexist with other business solutions which are more dedicated to business, such as PPM systems. In this article, we provide the keys regarding the limits of each tool and tips for a successful integration.

Sometimes, at ITM Platform we receive integration requests from some of our clients’ ERPs. In the following example, we explain what the coexistence rules are between a Project Portfolio Management system and an ERP.

Why ERP and PPM should coexist: a common story

A great ticketing agency hires a business controller to carry out an evaluation of the company’s internal processes. Its mission is to suggest improvements oriented to solving data discrepancy problems which currently exist between the finance department and commercial divisions. These matters are having important political repercussions because they affect sensitive issues such as the calculation of bonus at the end of the year.

From the first moment, the expert supposes that the problem is within the business software that the company is using. Or, in other words, within the incoordination between the different management tools that have been adopted in different areas of the company, in which the CIOs figure doesn’t exist.

An ERP with duplicated information is a bad ERP

Our business controller discovers that no one has taken the effort to define information flows between ERP (a kind of a feral version of SAP) and the company’s project portfolio management system. The consequence is that there are parallel processes with divergent results whose origin is difficult to estimate. Basically, the ERP doesn’t get to capture the complexity of a project’s cost structure in which there are cost estimates, real bills, calculated costs of internal and external hours, reported and accepted…

From that moment on, a decision is taken: PPM system, oriented to business generation, should be the entry point for all the information related to the organization’s projects, so that PPM project’s financial data “rules” over ERP and disagreements can be eliminated.

This example is typical within ERP integration and project management software. Generally, it is advisable to give autonomy to PPM system in order to support the projects’ activity solvency.

5 keys to ERP’s successful integration with a PPM system

Even though each company will have different use cases and specific necessities, there are some clear recommendations for the successful integration of ERP with a PPM system.

Let each system do its job. Data integration must be limited to what it is strictly operative. it is not advisable to design an integration which turns out to be an even greater complexity. On the other hand, orient yourself by three basic goals: avoid work duplication, avoid data divergence and promote transparency.
Share the necessary information. In a corporate environment, there cannot be black boxes. But we aware about the amount of information you share: when transparency is perfect, informative noise can be very loud with a very high productivity cost. That is why it is often advised not to send ERP more project data than the strictly necessary to carry out administrative and financial control tasks.
Choose a flexible PPM. Many PPM systems only send aggregated information about project costs, hindering project costs allocation to different items. By contrast, ITM Platform can send information with the desired granularity thanks to its open API (see documentation).
Don’t slave away your project managers by forcing them to adopt the projects’ module of you ERP. As you can see down below, the best way to integrate ERP and PPM is by letting ERP be in charge of the administration and PPM face all the complexity and the flexibility that a project demands.
Encourage collaboration around projects and the standardization within ERP. Apart from data integration, every technological integration process must face human and change management components. Designed procedures must leave enough operating space for project experts, taking advantage of communication and team cooperation systems, which sets out the PPM solution. On the other hand, ERP usually keeps to much stricter, standardized and mandatory procedures.

What sections of a project are covered by ERP?

When analyzing information systems and data flows in which a business environment is based, it is essential to know in advance what the connected areas are and possible overlaps between different platforms.

There are 4 points in which ERP administrative control layer comes into contact with projects:

Costs
Human resources and payroll
Suppliers management
CRM

In all these areas, it is crucial to design automatic flows from the portfolio management system to the ERP, specifying in each case the needed granularity and not sending invalid data as, for example, the estimated cost of a task.

What can't an ERP do?

The perception of an ERP being a business management machine which serves for any kind of activity can be a very big strain for corporate projects’ health.

For example, here are 5 areas in which ERP does not meet operative standards required by a portfolio management software

Resources planning: even though ERP can calculate and manage resource payments, only PPM has the enough flexibility to plan the resources and to be adapted to delivered work as it is being produced.
Project methodology: PPM tools are designed to be configurable to project methodologies in almost every environment. In addition, its functional scope is, as in ITM Platform’s case, very ambitious, gathering in one place financial and efforts data, risk planning and management, business goals, documents, deliverables, etc.
Task management and access to team members: the work content is difficult to manage from an ERP as, generally, the number of project team members with access to the environment, as well as its collaborative characteristics, is limited.
Portfolio view: PPM systems have prearranged project and portfolio signs and metrics which give a real-time image of the projects’ advancements, apart from allowing to work with customized exportable reports. Obtaining a similar view from an ERP means a tremendous configuration effort and hundreds of consultancy hours, while with ITM Platform it is about a few weeks.

Keep on reading:

Benefits of connecting your CRM to your project management tool

Your bank’s mobile app would not exist without unified Project Portfolio Management

Receive the latest blogs directly into your inbox

Managing a portfolio of innovative projects incurs many difficulties, such as the establishment of a culture of continuous evaluation in order to validate the hypothesis, or the difficult collaboration of multidisciplinary teams with no prior experience to rely on. For those who lead the innovation strategy, the biggest challenge is to have a tool that allows distinguishing the relative importance of each project in order to prioritize its implementation.

As the ratio between innovative ideas and projects reaching the final stage is very low, it is especially important to ensure that the highest value projects are approved. It is worth noting: innovation projects are very inefficient. It is necessary to spend time and money on research until you get an idea that is really worth pursuing. But that does not mean that you do not have to control how much time and money you spend, or what activities.

That is why this type of portfolio usually follows a lean philosophy: it starts from a hypothesis or idea that must pass through successive phases of refinement and validation.

Thus, before the existence of a project in the execution phase, there is the proto-project: first the idea or hypothesis, then the MVP, which requires pivot points. When the starting hypothesis is not endorsed by actual experience, or only partially, the proto-project can be reoriented in the light of what has been learned.

As pivoting generates additional costs in the search for commercial and technical viability, innovative proposals must be constantly evaluated to consider which ones should have room to generate inefficiencies and additional costs until a sound foundation is found - and which are discarded so that the investment is sustainable.

Innovation and corporate values

Innovation projects in large corporations are usually characterized by responding to a vision that goes beyond the business, also pointing to values such as Corporate Social Responsibility, environmental sustainability or the consolidation of one's own innovative culture.

For example, BBVA has an ambitious innovation strategy centered on Big Data. As the ultimate goal is to better understand the behavior of customers to provide better services, efforts are directed towards knowledge creation. With important ramifications: the key professional is no longer the traditional financier, but the data scientist, who "dominates statistics, knows how to program and also understands the business". The various initiatives that emerge from BBVA's Big Data strategy struggle for finite (though abundant) resources, which is why Marco Bressan has decided to concentrate on the centralization of information to begin with.

Start prioritizing your portfolio of innovative projects with ITM Platform

On the other hand, the means that any corporation has to materialize an innovation strategy is its portfolio of projects. In order for the portfolio of projects to have sufficient bearing, portfolio management must be the explicit responsibility of a corporate unit, often the management committee itself.

In the case of General Electric (GE), verticals include aviation and transportation, but they extend to materials as diverse as software, health services and water.

A sample of the diversity in GE's innovative portfolio

Unfortunately, as innovative projects are often completely unpublished and very different from each other, it is often difficult to know which projects are to be given preferential treatment. Is it more important that the project produces a social return or contributes to the modernization of the technological infrastructure?

Given the difficulty of comparing two innovative projects and knowing which will bring greater value to the company, it is crucial to have a criteria for making complex choices objectively.

Complex decisions are often subjective

A complex choice is one in which the alternatives are weighted based on more than one quality, so that there is no optimal alternative that surpasses the rest.

For example, several factors are taken into account when choosing an internet service provider: price, quality of customer service, the speed of the line and the reputation of the company. Usually the more economical services offer lower speeds, while more established brands often offer improved after-sales services. The decision is never obvious.

Complex choices are made daily. Often, as is the case with internet providers, the final decision is usually subjective, because whoever decides does not have the necessary time or tools to decide which option gives the maximum value. This hasty dimension of the decision allows competitors to appeal to the consumers' emotions and win with arguments less related to the service itself.

However, it is obvious that whoever leads the innovation program of a corporation can not be carried away with emotion. You will have to give reasons for your decisions, rely on data and get the push and commitment of many teams, who often work in remote locations.

Complex corporate decisions:

Portfolio prioritization with AHP

Without a technique or method to compare between the different value criteria, each choice between projects is difficult, equivalent to the choice between ethical values, such as freedom and equality.

Although there are dozens of prioritization methodologies for product requirements, there are not many alternatives in the world of project management.

The most convenient method for responding to complex choices representing the alternatives between innovative projects is AHP, an acronym for Analytical Hierarchy Process.

In short, AHP is advisable because:

It helps build consensus around how to implement the innovative portfolio strategy
It is linked by definition to the criteria, values and business objectives
Shorten the political discussions
Increase the commitment with the decisions taken, since all the criteria of the corporation are represented in the right measure.

This technique allows for comparing, in a table format, the relative importance of each criterion or objective.

The resulting table does not hierarchize in absolute terms. That is to say: it does not classify the objectives from more to less important, since that is an oversimplification. On the contrary, it allows us to attend to fundamental nuances when it comes to assessing the diversity of value propositions delivered by innovative projects.

For example, in the case of an innovative portfolio one could compare the importance of the following objectives:

Improving innovative culture
Increase market share in digital services
Modernize the technological infrastructure

Let us now imagine that the management committee of a corporation devotes a meeting to compare these objectives and discuss which is more important for the strategy comparing them in pairs. The conclusion would be something like the following table:

Although matrices can be done by hand or in Excel, it is convenient to have software that allows calculation and is integrated with the project management itself, such as ITM Platform.

Thus, not only is there a system that helps to perform the analysis, but its results are registered and connected with the evaluation of the projects themselves.

By linking each project to the objectives and criteria it supports, ITM Platform indicates which projects contribute the most value and should start sooner.

Of course, the work of evaluating the proposals will remain a difficult art, as well as the elaboration of innovative proposals, with all the market prospecting exercises, identification of tendencies and uncertainty for the future.

But there is a basis in the management of the information that must be demandable. The facilitated prioritization that we have explained in this article has the great advantage of generating consensus and supporting informed, renegotiable and easy to communicate decisions.

Receive the latest blogs directly into your inbox

Financial services are an infallible measure of your time

At the time of European colonization, the great adventures of exploration were only possible thanks to the issuance of loans by the great bankers of the time.

In the western United States, at the beginning of the nineteenth century, banks operated with minimal regulation. To build trust in its users, the bank was often the most solid building in the entire settlement. During the time when remote communication was done by MORSE code and the train lines forced to coordinate the schedules in remote territories.

Nowadays, the need for trust and guarantees has not changed, although the means to produce it uses current technologies.

Monitor the contribution of your technological projects to the development of the business with ITM Platform.

Entities providing financial services to private users move trillions of dollars around the world, and mainly include commercial banks and insurers. The transition to increasingly more digital users has forced this sector not only to provide online banking services, but to give access to those same services in mobile applications.

The pressure on banking to modernize its IT systems

And it's not just about designing an attractive and useful online banking application.

A commercial banking mobile application is only possible as a result of dozens of different projects, such as:

Making remittances to other banking entities
Secure authentication system with fingerprint
Account management, with recovery of historical information and permanent updating of the latest movements
GPS navigation to find the nearest cashier or office
Viewing of information

All this does not take into account all the technological infrastructure with which the online banking application must be connected in order to be launched, nor the legal and compliance obligations to which this type of operations are subject, including the protection of data during its recovery , treatment, storage and communication.

Competition is fierce: according to a Ernst & Young report launched in 2016, in most surveyed countries, the general public relies more on mobile banking services from supermarket chains or digital home banking to traditional banks' online banking applications .

If these projects were not managed in a coordinated way, it would be impossible to guarantee the service. What's more, it would be crazy to think that it would work at the time of launch. That is why every financial services company needs to manage its projects in a coordinated manner.

That means that, without addressing all the implications and connections between the new application and existing systems, and without coordinating projects based on these connections, at some point we will find this message when we open our online personal banking application:

"We are experiencing some technical difficulties. Apologies for the inconvenience."

If we reach this outcome, coordination has failed. Meaning having to abandon the project management to deal with the crisis.

The message has as many causes and variations: login problems, failure to update data, procedural problems.

However, the result is the same: loss of customers and reputation.

That is why, for the organizations that manage to coordinate their projects, competitive advantages immediately ensue. In addition, attracted by a comforting user experience, new customers arrive in flocks. The most robust building in the city has been erected, perfectly visible on every mobile screen.

Financial services and project management

In order to avoid messages like that and to construct a robust strategy of technological delivery, the responsibility of the CIO of a banking institution has to be the general of his army. In order to coordinate their activities, these profiles should focus on at least 6 major responsibilities:

Develop projects for all business units of the organization with equipment and limited funding, often responding to direct demands for new internal projects.
Contributing to productivity goals consistently.
Leading the digitization of the service portfolio.
Modernize information systems, which are often decades old. The transition is difficult, but without it the overall response time will be compromised. In addition, problems of backward compatibility may arise as soon as there are strong demands to implement new technologies for a user, such as direct mobile payment.
Reducing contingencies that impede active planning and "putting out fires" effectively.
Use credible measures to see if teams are working on appropriate projects.

The 11 questions for financial services projects

These responsibilities require access to aggregate information, such as that provided by portfolio management tools, and which can be summarized in 6 basic questions:

What projects are currently being implemented?
What projects are planned?
What resources are available?
Are there limits or restrictions on the use of these resources?
What other projects can be implemented with current capacity?
What are the dependencies between projects?
What are the options for resolving conflicts for the use of resources between different projects?

In addition, there are other questions whose response is likely to require meetings and deliberation. The following 4 are some examples.

Are there unapproved project proposals that merit efforts in the light of the current situation, or do they have synergies with other projects already initiated?
Given the follow-up of the projects, is it appropriate to cancel any of the ongoing projects?
Have resources been planned according to project priorities and job-specific competencies?
Is there any review of objectives and priorities affecting project implementation?

In order to be able to respond adequately to these questions, it is necessary to use the project portfolio of the organization as a repository of ideas and proposals that are evaluated, analyzed and initiated according to a constant cycle.

In many organizations in other sectors, the portfolio steering committee is comprised of directors from various areas, each of whom provides input on priority projects. This model can also be implemented in banks or insurers; the key is to find the balance between the technical feasibility criteria of IT managers and the business vision.

On these foundations, the digitization, innovation and commercial development projects of any financial services entity will be protected by a robust governance system with guarantees of success.

If you liked this blog, here are some related blogs that you may find interesting:

How to manage multi-project organizations

How SaaS-based project management has surpassed the MS Project model

Integration with the ITM Platform Project Menu

Receive the latest blogs directly into your inbox

Why make status reports?

Every project needs a status report , also known as progress report, in which the status of the project is clearly, accurately and objectively reported.

Start feeding your project status reports with live data on ITM Platform.

A project status report is intended to provide an evaluation of the progress and communicate execution details. Therefore, the development of the progress report is of great importance, since it is vital that it be carried out following a predetermined model. Only in this way will the users of the reports be able to compare them with each other:

Comparing status reports for different phases of the same project gives you a better idea of the distance covered, analyzing how far future projections from previous phases have been verified or denied
Comparing reports from different projects is crucial, especially among similar projects using Gantt charts, to understand where discrepancies between estimates and real data are

If you do not have a reporting model in your organization, you are missing out on the advantage of being able to compare reports. To make matters worse, homogeneous models allow users of such reports to find the information they need quickly, as they know how it’s structured. This is one of the aspects where by a Project Management Office can bring great benefits for internal communication in an organization.

A status report contains a brief description of the main elements of the report, establishing causes and explanations that justify and give context to the data. Metrics and graphics will allow the user to understand the progress of the project in a very short time.

The executive summary: Basis for monitoring a project

This section requires an objective description of how the project is running . The summary should present clearly and simply the most important results of the project, including:

Milestones fulfilled
Deliverables and quality
Risks or unforeseen events
Relationship between estimates and real, in at least three aspects: resource allocation, costs and deadlines
The difference between the estimated progress and the progress to date. If the date of delivery is considered unrealistic, this alarm signal is the first step to alert the customer and negotiate a new date with him.

On the other hand, the executive summary is very effective for a detailed follow-up of the unplanned challenges that arose during project development, as well as actions to be implemented in the short term , so that any eventuality can be mitigated.

The purpose is to ensure that the project continues on the path to success, delivering the project on time, with the expected quality.

Project progress reporting: steady progress assessment

The constant evaluation of a project is vital to know what countermeasures should be taken to make the project successful. Hence the preparation of this section outlines the most problematic areas of the project.

Likewise, suggestions and corrections can be advanced to solve a specific problem. As the project, often, cannot wait to receive feedback on these aspects, decisions are already taken, so this point can delineate already decided actions.

Registration Template: Project Control

The status report should generate relevant information about the risks recorded. It is advisable to start from a registry template by means of which you can retrieve useful information in an orderly way. This registry template will contain:

Project Risk Factors,
Probabilities
Project impact

You can visit ITM Platform’s free risk assessment matrix to compile this information quickly.

Know all about metrics: Promotes project tracking

Managing a project is only possible if you have the tools to quantify the different parameters involved, offering objective and comparable data. Thus, you can measure, for example:

Delivery times
Quality of the deliverables, based on the number of requirements included
Costs incurred to date
Percentage costs over total
Amount of unanticipated costs incurred
Hours worked, either per worker or by professional category

Result indicator

If the result is not a material product but a service, and the project covers the phases of implementation and marketing, there will be a large number of quantifiable aspects related to the result, such as the number of users, their average cost, and so on. These indicators will serve to measure the quality of delivery.

If you are interested in knowing which indicators you can use to manage your portfolio, you can continue reading these articles:

Receive the latest blogs directly into your inbox

A project management office (PMO) can fulfill multiple functions related to the supervision of an organization's project portfolio, often with managerial functions and with a strategic orientation that is added to the simple control and monitoring layer.

However, it is not clear what an agile PMO is or how it is structured. It is becoming increasingly urgent to clarify this aspect, since many teams and even entire organizations, especially in the field of software and application development, rely entirely on agile methodologies such as SCRUM.

Before entering into the matter, it is necessary to clarify three different senses of what can be understood by agile PMO.

Disambiguation: What do we mean by agile?

An agile PMO can refer to several situations, such as:

1. The agile implementation of a PMO

As the start-up process is long, complex and may have difficulties in demonstrating its benefits to stakeholders with a high capacity for influence, some experts advise that the start-up approach be agile and be protected from criticism towards a structure that it is not working 100% yet. In addition, it is possible that the difference stakeholders do not agree on what should be the role of the PMO in the organization, in which case their scrutiny on the development of the implementation will necessarily be uneven.

Reference: https://www.pmi.org/learning/library/agile-project-management-office-expectations-7069

To combat this disadvantage, a PMO whose implementation is conceived as an agile project must deliver processes and functions useful for the operation of the PMO in a continuous and early manner.

The measure of the progress of the project, as is logical, is given by the functionality of the PMO itself.

An agile implementation is usually characterized by an initial diagnostic phase, followed by phases of planning, execution and closure that can be iterated several times until the PMO has the desired maturity.

However, in the first iteration of the execution, the PMO already assumes characteristics that allow it to operate in one or more of its functions.

2. The role of a PMO whose objectives is to manage the project portfolio following agile principles

It is not essential to have adopted SCRUM throughout the organization so that we are interested in benefiting from some of the advantages of agile principles at the corporate level.

For example, the agility applied to the entire portfolio of projects allows for early decisions and rectifies the initial planning of projects when the context that justifies them is modified.

3. The role of a PMO in an organization that has exclusively adopted agile project management methodologies

What happens when an organization that worked with classical methodologies or waterfall becomes guided by SCRUM or other agile methodologies?

What is the role of the PMO in this new situation? Is the mission aborted and the office deleted, or is it given a new meaning?

The cultural and change management role of the PMO can be fully maintained. In the new context, the PMO facilitates the deployment of the agile culture in the different areas of the organization.

The predominant areas are the following:

Training: includes training new people in agile methodologies, preparing meetings and workshops, deepening for key embers, as well as coaching services.
Work monitoring: although the agile philosophy is very horizontal and does not require so much external control, a PMO can support the performance of the teams helping them to manage the backlog, offering clarity in the performance of the teams through an impartial external vision, and helping to that the documentation that works in the organization is productive and does not produce unnecessary work.
Interlocution with the business: One of the fundamental aspects of the manifest agile is the constant efforts to understand the need of the client and guide the work to the delivery of utility. In internal projects, it is essential that there is a well-oiled transmission chain with those who administer the corporate strategy so that they know that the engineering teams are working on the most critical aspects and that they deliver the most value to the business.

Next, we detail better what the work of an agile PMO consists of in this last case.

Save time and money by connecting your agile projects to a comprehensive overview of all your costs and resources.

The nuance is important, as our readers are well aware that managing agile projects involves ongoing guidance to customer requirements and very frequent evaluation cycles. The question is how the responsibilities of methodological guidance, centralization, control and direction of the PMO can be connected in these cyclical structures, maintaining customer orientation and business perspective.

The fundamental risk, let's face it, is to create a small bureaucratic monster that coagulates methodological demands without adding value.

Failures in the conception of a PMO

The main problem arises when, in order to achieve agile projects, an attempt has been made to establish rules of action that have merely pigeonholed and limited decision-making.

Despite falling under the range of agility, SCRUM requires the production of a lot of documentation with a very high frequency, including the requirements of user stories.

A recurring error when creating PMO in agile environments is utilizing them as centralized offices that impose internal policies and norms. Keep in mind that circumscription to certain standards at work can marry poorly with the completion of certain complex projects. There is the risk of restricting the freedom of action and the margin of manoeuvre that are fundamental to produce value in all sprints.

A PMO cannot be confused with merely a controlling body that seeks to fit agile projects into tactics, methodologies and master projects of the manager that have been preconceived without special attention to the changing nature of agile projects.

First correct interpretation of the agile PMO

In contrast to the centralized and bureaucratic PMO, the most attractive in an agile environment is the performance of a facilitation function.

This can be done by establishing recommendations to help manage the workload, distinguishing between priority and ancillary tasks, helping project managers determine how much they can rely on experts, and even set basic standards of performance and work ethics that are in line with the values and mission of the organization. So that all projects, besides providing value to the client, are oriented to the common benefit and growth and consolidation of the organization.

One difficulty of any multi-project organization is the barrier to sharing knowledge, both within the same project team and between different projects. In the first case, the difficulty is that the experience and specialization accumulated by the veterans is not limited to the tasks they perform - which would create bottlenecks; In the second, the difficult thing is that the experience in the development of a project is not forgotten with its completion, but rather to increase the experience accumulated by the organization.

An agile PMO, among other things, faces the specific knowledge challenges that hinder operational improvement in agile performance.

And one of the main goals of an agile PMO is to make all parts of the organization that take part in a project as a unit, as a team, and even as a team of teams. In this sense, it is important that whoever is going to coordinate the work of the PMO accredits the following virtues:

- Relationships. Good contact with leaders of other departments as well as people integrated into other projects.

- Trust. Openness in dealing with those who are going to influence the project is key to its success.

- Experience. Undoubtedly, having previously faced similar projects provides sufficient evidence to address future projects.

The goals of an PMO agile

Once we have analyzed some guidelines of an agile PMO , we are going to offer you the primordial purposes of these organs. Take note.

1. Manage new project entries

It makes no sense to approve projects above the delivery capacity of development teams. The PMO can function as the housekeeper to resist the temptation to start projects too soon. You have to wait to finish projects to start others of equal size.

2. Validation of the planning rules

The probability of unexpected and unnecessary changes must be reduced to the maximum, due to the overall understanding of the program.

3. Creation of training programs

Training is fundamental so that the knowledge of the equipment is truly complementary and there are no empty areas. The detection of gaps should be the basis for proposing training to members.

4. Limit waste

Only the PMO will have aggregated information on where time and effort is wasted. It is possible that different projects have similar patterns that point to the inefficiency of the processes. Drawing attention to them is the first step to rectifying them.

5. Delivery report

Reporting to consolidate an accredited view of the status of part of a project or its overall vision will facilitate the interpretation as to whether the affairs of the organization are being carried out in the most functional way. Without going further, conclusions that can be drawn from these reports may become important in the allocation of personnel for certain tasks or working schedules.

6. Business rules related to the benefits of the project

When making a commitment on a project, it is imperative to keep in mind that there are minimum results that have to be fulfilled. This duty also facilitates the adjustment to content that is compatible with existing quality projects. A uniformity that you do not have to understand as negative, but as an orientation towards excellence.

7. Validation of a resource plan

Every project requires a realistic allocation of resources. You have to keep in mind that the amount of resources of an organization will always be insufficient to delivering all the projects that can be generated, hence it is necessary to select, analyze conscientiously and not to precipitate. The allocation must be reasonable (it is fundamental to minimize the risks) and must be based on the fact that, in a final global calculation, the investment and achievement are compensated.

In short, we hope this text has helped you understand how an agile PMO has to works.