Project Management

Voices on Project Management

by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog

RSS

View Posts By:

Cameron McGaughy
Lynda Bourne
Kevin Korterud
Peter Tarhanidis
Conrado Morlan
Jen Skrabak
Mario Trentim
Christian Bisson
Yasmina Khelifi
Sree Rao
Soma Bhattacharya
Emily Luijbregts
David Wakeman
Ramiro Rodrigues
Wanda Curlee
Lenka Pincot
cyndee miller
Jorge Martin Valdes Garciatorres
Marat Oyvetsky

Past Contributors:

Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie

Recent Posts

Project 2030: Skills We Need to Cultivate Now

The Technical Program Manager: How to Stay Relevant in 2025

5 Things Your Operational Plan Should Do

5 New Project Guardrails for Adaptive Leaders

The Leader's Voice: Respect It, Protect It, and Use It Properly!

Categories

2020, Adult Development, Agile, Agile, Agile, agile, Agile management, Agile management, Agile;Community;Talent management, Artificial Intelligence, Backlog, Basics, Benefits Realization, Best Practices, BIM, business acumen, Business Analysis, Business Analysis, Business Case, Business Intelligence, Business Transformation, Calculating Project Value, Canvas, Career Development, Career Development, Career Help, Career Help, Career Help, Career Help, Careers, Careers, Careers, Careers, Categories: Career Help, Change Management, Cloud Computing, Collaboration, Collaboration, Collaboration, Collaboration, Collaboration, Communication, Communication, Communication, Communication, Communications Management, Complexity, Conflict, Conflict Management, Consulting, Continuous Learning, Continuous Learning, Continuous Learning, Continuous Learning, Continuous Learning, Cost Management, COVID-19, Crises, Crisis Management, critical success factors, Cultural Awareness, Culture, Decision Making, Design Thinking, Digital Project Management, Digital Transformation, digital transformation, Digitalisation, Disruption, Diversity, Diversity, Documentation, Earned Value Management, Education, EEWH, Enterprise Risk Management, Escalation management, Estimating, Ethics, execution, Expectations Management, Facilitation, feasibility studies, Future, Future of Project Management, Generational PM, Governance, Government, green building, Growth, Horizontal Development, Human Aspects of PM, Human Aspects of PM, Human Aspects of PM, Human Aspects of PM, Human Aspects of PM, Human Resources, Inclusion, Information Technology, Innovation, Intelligent Building, International, International Development, Internet of Things (IOT), Internet of Things (IoT), IOT, Knowledge, Leadership, Leadership, Leadership, Leadership, Leadership, lean construction, LEED, Lessons Learned, Lessons learned;Retrospective, Managing for Stakeholders, managing stakeholders as clients, Mentoring, Mentoring, Mentoring, Mentoring, Mentoring, Methodology, Metrics, Micromanagement, Microsoft Project PPM, Motivation, Negotiation, Neuroscience, neuroscience, New Practitioners, Nontraditional Project Management, OKR, Online Learning, opportunity, Organizational Culture, Organizational Project Management, Pandemic, People management, Planing, planning, PM & the Economy, PM History, PM Think About It, PMBOK Guide, PMI, PMI EMEA 2018, PMI EMEA Congress 2017, PMI EMEA Congress 2019, PMI Global Conference 2017, PMI Global Conference 2018, PMI Global Conference 2019, PMI Global Congress 2010 - North America, PMI Global Congress 2011 - EMEA, PMI Global Congress 2011 - North America, PMI Global Congress 2012 - EMEA, PMI Global Congress 2012 - North America, PMI Global Congress 2013 - EMEA, PMI Global Congress 2013 - North America, PMI Global Congress 2014 - EMEA, PMI Global Congress 2014 - North America, PMI GLobal Congress EMEA 2018, PMI PMO Symposium 2012, PMI PMO Symposium 2013, PMI PMO Symposium 2015, PMI PMO Symposium 2016, PMI PMO Symposium 2017, PMI PMO Symposium 2018, PMI Pulse of the Profession, PMO, PMO, pmo, PMO Project Management Office, portfolio, Portfolio Management, Portfolio Management, portfolio management, presentations, Priorities, Probability, Problem Structuring Methods, Process, Procurement Management, profess, Program Management, project, Project Delivery, Project Dependencies, Project Failure, project failure, Project Leadership, Project Management, project management, project management office, Project Planning, project planning, Project Requirements, Project Success, Ransomware, Reflections on the PM Life, Remote, Remote Work, Requirements Management, Research Conference 2010, Researching the Value of Project Management, Resiliency, Risk Management, Risk Management, Risk management, risk management, ROI, Roundtable, Salary Survey, Schedule Management, Scheduling, Scope Management, Scrum, search, SelfLeadership, SelfLeadership, SelfLeadership, SelfLeadership, SelfLeadership, Servant Leadership, Sharing Knowledge, Sharing Knowledge, Sharing Knowledge, Sharing Knowledge, Sharing Knowledge, Social Responsibility, Sponsorship, Stakeholder Management, Stakeholder Management, stakeholder management, Strategy, Strategy, swot, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management Leadership SelfLeadership Collaboration Communication, Taskforce, Teams, Teams in Agile, Teams in Agile, teamwork, Tech, Technical Debt, Technology, TED Talks, The Project Economy, Timeline, Tools, tools, Transformation, transformation, Transition, Trust, Value, Vertical Development, Volunteering, Volunteering #Leadership #SelfLeadership, Volunteering Sharing Knowledge Leadership SelfLeadership Collaboration Trust, VUCA, Women in PM, Women in Project Management

Date

Viewing Posts by Mario Trentim

Digging Deeper into a PMO Implementation Plan

Categories: PMO

linkedin twitter facebook Request to reuse this  
In my last post, we discussed the five basics of a PMO implementation plan. Here, I'll delve deeper into those five: 

1. Current State Assessment

When assessing the current state, it might be helpful to hire an external consultancy, as internal initiatives may lose momentum along the way. The people internal to an organization might not be able to ask the right questions or they might even resist due to a fear of change. An external consultancy can assist in overcoming political issues by adopting a structured approach. Usually, consultants force or drive change because that's what they are hired to do. In the end, a good diagnosis will point out issues and opportunities for improvement. 

2. Future State Vision

Based on the assessment, it is possible to design a future state vision, describing how projects, programs and portfolios should be managed in order to fulfill organizational needs. That's because when the current state is clearly understood, it is easy to compare to benchmarks. Consequently, the organization can realize what is missing or what is done but could be improved. Ultimately, the future state vision details exactly what the organization wants to become.

3. Gap Analysis

The next step is to carry out a gap analysis by comparing the current state to the future vision. This analysis has to focus on three factors: 

  • What is desirable? 
  • What is effective?
  • What is feasible?
A successful gap analysis clearly identifies what is missing or what could be improved, prioritizing which features, processes and structure the PMO should have, according to effectiveness (cost x benefit), desirability (sponsorship; what the company want to implement) and feasibility (what is realistic and what is possible to do). We have to select and prioritize based on cultural and organizational feasibility, not only based on resources available.

For example, imagine an organization wants to implement enterprise project management (EPM) software. There are plenty of options in the market. Some have fancy features and are more expensive. It might be desirable to have top-notch software, so we won't have to substitute or upgrade it for years. However, it is effective to choose software that offers the simplest solution and satisfies future state needs. Finally, it might be feasible to start with familiar software to overcome people's resistance and rejection to the PMO implementation.

In this particular case, project professionals might desire the best EPM in the world (desirability) -- but the company could do well with a free version or simpler software (effectiveness). Finally, considering that people unfamiliar with project management practices will have to use the software, it might make sense to get something familiar or similar to other software they already use (feasibility).

4. Implementation Strategy

After the gap analysis, introduce stakeholder requirements to define the implementation strategy. I recommend thinking of the PMO like a new business unit or a small new company. The PMO should have its own mission, vision and goals. We have to identify who are its stakeholders and customers, so we can define its value proposition and its services. Personally, I use the Business Model Generation canvas to do that.

The implementation strategy defines the approach to implement a PMO, major expected results and the overall framework, considering organizational strategy and corporate project management governance. Consequently, the PMO business model must support and enhance strategic alignment by selecting, prioritizing and managing portfolios of projects that sustain and boost organizational strategy.

5. Implementation Plan

Finally, the implementation plan is the detailed project management plan for implementing the PMO. While the implementation strategy is the approach chosen to implement the PMO, the implementation plan puts that strategy into action. 

We start by defining its scope and work breakdown structure. Then we create a schedule of tasks to deliver the project scope. Resource needs are identified and a budget is set. Other subsidiary plans are created to manage integration, scope, time, cost, quality, communications, human resources, risks, procurement and stakeholders. 

The implementation plan should be as detailed as you need. I want to emphasize the importance of defining a business model for your PMO, allowing for performance measurement and improvement after the implementation. 

In my next post, I'll provide a framework for sustaining and improving your PMO, once it is set up and running. Do you have any tips or examples of PMO implementation plans? 

Posted by Mario Trentim on: February 21, 2014 09:50 AM | Permalink | Comments (2)

Five Basics of a PMO Implementation Plan

Categories: PMO

linkedin twitter facebook Request to reuse this  
I often say that establishing a project management office (PMO) is not for the faint of heart. It is a very difficult endeavor -- not just because it involves advanced knowledge, but also because it challenges status quo in the organization. 

In my previous post, we discussed The Must-Haves of Establishing a PMO. Now we are going one step further by laying out an implementation plan. Implementing a PMO involves five basic -- but essential -- sets of decisions:

1. Current State Assessment

  • How many projects do we have today, and how are they being managed?
  • Are their results satisfactory? 
  • Do we really need a PMO? 
  • What type of PMO?
2. Future State Vision

  • What functions will be performed by the PMO?
  • What results do we expect from the implementation?
3. Gap Analysis

  • What do we have right now in terms of project governance, methodology, infrastructure, human resources and software?
  • What do we need to implement a PMO that delivers the expected results?
  • How are we going to handle change management, stakeholder expectations and cultural aspects?
4. Implementation Strategy 

  • What is the scope of the implementation?
  • What are the barriers, enablers and risks of this implementation, and how are we going to deal with them?
  • Are we going to hire a consultancy?
  • Do we start a small pilot and grow it through quick wins? Or do we set up for global, company-wide implementation?
  • What are the implementation's critical success factors?
5. Implementation Plan

  • What is our roadmap for implementation?
  • What are the implementation's phases and key milestones?
  • How many resources do we need? 
  • How much will the implementation cost?
  • How do we guarantee the PMO's sustainability? How are we going to measure its performance and improve it?
Not following these steps can result in serious problems. For example, if we don't conduct a gap analysis, we will probably end up with an unfeasible plan, disconnected from reality. 

I once participated in a PMO implementation that was doomed to fail under the original plan. The future state vision was nearly impossible to reach, considering the current state of the organization. While conducting the gap analysis, it became clear that we should lower our expectations to implement that PMO. In that particular case, it was necessary to implement a rudimentary PMO to kick-start a cultural change to embrace project management. That was the chosen implementation strategy, which led to a feasible implementation plan supported by key stakeholders.

In my next post, we'll dive deeper into these five steps with best practices and examples on how to carry them out. 

What other questions do you think are helpful to ask of your organization when building a PMO implementation plan? 

Posted by Mario Trentim on: February 06, 2014 10:13 AM | Permalink | Comments (5)

The Must-Haves of Establishing a PMO

Categories: PMO

linkedin twitter facebook Request to reuse this  
Seventy percent of organizations had a project management office (PMO) in 2013, according to PMI's Pulse of the Professionâ„¢ In-Depth Report: The Impact of PMOs on Strategy Implementation. That compares to 61 percent in 2006. Despite the increasing number of PMOs, many of them still fail. The first step in effectively establishing a PMO is figuring out if your organization even needs one. Only then can you ask, How can we establish one successfully?

Part of determining if a PMO would be a good fit for your organization is knowing what a PMO's functions are. A PMO is an organizational structure, like a department or group, responsible for helping the enterprise achieve its strategic goals through effective project management results. Therefore, a PMO usually delivers three main objectives:

  • Efficient projects: better results
  • Reporting: information to support decision-making 
  • Standardizing: consistent and repeatable results
Obviously, implementing and sustaining a PMO is not cheap. Usually, there is some capital investment in setting up a PMO, particularly because it will add management overhead in addition to existing projects' costs. For a company whose core business involves only a few projects, if any, it might not make sense to implement a PMO. And while there's no formula to determine when organizations need a PMO, most do when they have:

  • A large number of projects -- a PMO manages interdependencies, resources and provides standardization
  • Very big projects -- they usually bring high complexity, which requires coordination and integration
  • Strategy that depends heavily on new projects -- a PMO in this instance provides strategic alignment, prioritization and selection.

So let's say it's been determined that your company needs a PMO. How do you lay the foundation to establish it effectively? First, it is important to know that there are different types of PMOs. These include but are not limited to:

  • Project office: Planning, monitoring and control functions for large and complex individual projects or programs
  • Departmental PMO: Integrating projects into one or more portfolios of projects, managing a shared pool of resources and providing consolidated reports 
  • Enterprise PMO: Ensuring strategic alignment by selection and prioritization of projects, programs and portfolios. (Read more on PMI® Thought Leadership Series: Strategic Initiative Management - The PMO Imperative.)

Keep in mind that implementing a PMO involves a lot of change management, because it entails a new organizational structure, which affects the balance of power and culture in an organization. I recommend organizations invest more in change management tools or talent. 

Finally, to tailor the best PMO for your organization from the start, I recommend following these key steps:

  1. Define a mission. What does your PMO do? 
  2. Define a vision. How do you want it to grow?
  3. Identify key stakeholders. Who are your clients?
  4. Select core functions and services. How does your PMO add value to stakeholders?
  5. Create proper metrics and key performance indicators (KPIs). How do you know your PMO is doing OK?
  6. Continuous improvement. Develop action plans based on metrics and KPIs
  7. Focus and value. Keep it lean. It is common for PMOs to start adding more services, processes and features. Sometimes they are only wasting resources because the organization doesn't need that.
In my next post, I'll outline a plan to implement a PMO. We will also talk about maintaining a PMO and continuous improvement to keep it sustainable.

Do you have advice for determining if your organization needs a PMO or basic tips for establishing a strong, sustainable PMO?
Posted by Mario Trentim on: December 20, 2013 02:51 PM | Permalink | Comments (5)

Embedding Portfolio Management Through Effective Communications

linkedin twitter facebook Request to reuse this  
Despite uncertainties in today's economic environment, organizations remain under pressure to successfully execute business strategies. These challenging conditions demand that organizations innovate and gain an advantage through projects. Yet launching a bunch of projects won't save the day. We need solid portfolio management to enable that competitive edge. It's not just about software, methodology and frameworks, after all. To perform well, portfolio management requires a cultural change and solid communications within an organization.

And yet, we still suffer due to poor communications. Many companies, for instance, invest significant effort and capital on projects and programs that do not directly align with corporate objectives because those goals are poorly communicated. Meanwhile, others struggle to balance risk and fail to seize opportunities because of ineffective communications that do not support informed decision-making. For example, I worked on a project of high complexity that had huge technical challenges. These challenges could have been better addressed if there had been more communication among different research teams in our organization.

The payoff to investing in project communications can be substantial, as many studies -- such as a recent one from PMI -- point out. Companies that excel at portfolio management are able to complete projects on time and under budget, increasing ROI and other benefits. But how do we consistently communicate the portfolio management strategy, policies, governance and benefits throughout the organization?

  • With clarity. Clarity is the most important factor for the success of portfolio management. People can't commit to what they don't know or don't understand. Clearly state and communicate the portfolio objectives, policies and procedures. 
  • With openness. On top of developing a nice-to-have framework for project selection, prioritization and portfolio monitoring, spread the word throughout the entire organization on why the company needs portfolio management and how it works.
  • With alignment. Corporate objectives -- and how portfolio management can help the organization reach those goals -- have to be part of the message. Alignment means credibility for portfolio management, because it shows how it adds business value. To communicate the value, show the organization the selection criteria and key performance indicators and their rationale.
  • With discipline. Portfolio management requires consistent feedback, information and reports -- mainly from projects and programs, but also from functional managers, senior managers and more. Discipline means setting up processes and procedures to push and pull communications in a dependable way for the organization. In other words, in-and-out communications have to flow without interruption, overcoming organizational barriers to get information needed and to provide useful, timely information.
  • With accountability. Everyone in the organization should be responsible, in one way or another, for the portfolio results. That means project KPIs and portfolio KPIs should align better. And the best way to achieve that alignment is by ensuring everyone is on the same page about the corporate portfolio strategy, through rigorous governance and consistent communications.

I'm a firm believer that the role of communications is to ensure that portfolio management is embedded in the corporate culture. What do you think is the role of communications in a portfolio?

Posted by Mario Trentim on: October 01, 2013 09:49 AM | Permalink | Comments (2)

The Secrets to Managing an Innovation Portfolio

Categories: Portfolio Management

linkedin twitter facebook Request to reuse this  

Managing a portfolio of innovation projects is very different from traditional portfolio management. Innovation projects hold more uncertainty. It is usually difficult, if not impossible, to provide good estimates and a detailed project plan. And while most organizations care about managing the development of marketable new ideas, few really know how to foster them for business results. 

The first step to managing a portfolio is determining the role and ROI of innovation in a business environment. Innovation, in essence, has to bring tangible results and a competitive advantage to the organization by generating new revenue, reducing costs, improving asset management and increasing reputation.

To achieve these goals, innovation portfolios aim for steady innovation flux, or a constant pipeline of new ideas, for a sustainable competitive advantage. That requires balancing short- and long-term benefits and costs of the following:

  • Incremental innovation: Developing new products, processes or services 
  • Basis innovation: Researching low-maturity technology
  • Radical innovation: Supporting efforts to create breakthrough innovation

For example, it would be shortsighted to generate only incremental innovation; in the long-term, there will be no breakthroughs. However, incremental innovation brings short-term revenue, which is important to keep the company going. Basis and radical innovation generate new products, but require significant time and effort. A good portfolio balance mixes incremental, basis and radical innovation projects in a way that best fits the organization.

Another important aspect of managing an innovation portfolio is selecting the right ideas. Selection is particularly crucial to innovation projects because of the commitment to a long-term "technology roadmap" (i.e., if you choose to invest in Blu-ray products, that means you have a Blu-ray portfolio). Investing in the wrong technology can put an organization in financial jeopardy. Complexity is also greater because you're creating something new and without precedent. So the challenge is choosing projects that support the organization's long-term objectives while still considering these aspects. In summary, innovation portfolios need different selection and prioritization criteria. Here are suggested criteria, ranked from most to least important:

  • Strategic alignment
  • Potential to generate innovation 
  • Level of risk
  • Technological maturity
  • Use of resources
  • Degree of complexity
  • Level of interdependence with other projects

The criteria above are mainly qualitative, so you should also use an enterprise-wide scale for grading each project's potential to generate innovation:

  • High: There are many potential ways and areas to apply this innovation
  • Medium: There is a specific use for this innovation; we are somewhat sure about market demand
  • Low: We are not sure how it will work

After selecting your innovation projects by balancing the above criteria, tailor key performance indicators. Here again, KPIs will differ from a more traditional portfolio. Some I have used in the past include:

  • Ratio between long- and short-term projects
  • Ratio between high- and low-risk projects
  • Number of new technologies created
  • Ratio between technologies applied to new products and technologies created
  • Number of patents created
  • Revenue generated by patents
  • Number of projects successfully transferred to market
  • Percentage of projects commercially successful
  • Return on product development expense
  • Number of new customers from new products or services
  • Market share growth from new products and services

Does your organization have research, development and innovation projects? Do you use an innovation portfolio? How are they managed? 

Share your thoughts below along with your Twitter handle, and Voices on Project Management will publish the best response as a blog post.

Posted by Mario Trentim on: August 06, 2013 11:51 AM | Permalink | Comments (1)
ADVERTISEMENTS

Where lipstick is concerned, the important thing is not color, but to accept God's final word on where your lips end.

- Jerry Seinfeld

ADVERTISEMENT

Sponsors