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

From Birth to Adulthood: How to Mature Portfolio Management Practices

linkedin twitter facebook Request to reuse this  

By Wanda Curlee

When we talk about project, program and portfolio management, the word “maturity” often comes up. But with respect to portfolio management, the newest of these three disciplines, what does “maturity” really mean?

For starters, it means time. Simply aquiring a portfolio management tool doesn’t align the portfolio to the strategy, as Dr. Mark Mullaly noted in a projectmanagement.com blog post earlier this year. Alignment typically doesn’t happen overnight or even in one year. Implementation of strategy normally comes with organizational change, and most humans do not like to change.

Here’s a look at a typical portfolio management developmental process.

The Early Years

Immature portfolio management practices are normally less than three years old. I think of this as the toddler stage. Getting to the next stage of maturity takes a committed C-suite that believes that a portfolio manager can balance the checkbook while delivering strategic benefits.

Remember, no company or individual has a blank check to fund all projects and programs. There must be mutual trust between the portfolio manager(s) and the C-suite. The C-suite must provide the portfolio manager with the authority and support needed to get real traction.

Traction should follow from a defined governance structure, rudimentary metrics, and programs and projects adhering to the governance structure. As Andy Jordan notes, without successful projects, portfolio management will not succeed. Project leaders need to realize that the portfolio manager drives the organization’s strategic execution.

Project managers may see this as an attack on their independence or worry that a project will be cancelled, Mr. Jordan adds. With a cancellation, a project manager and team may be placed on the bench. Organizational shifts are uncomfortable.

Throughout this state, it is imperative that portfolio managers demonstrate value to project and program managers, according to Mr. Jordan. One way to do this is to constantly communicate to these practitioners that they must see everything they do through the lens of the customers’ wants and needs.

Growing Pains

The next step is what I call the teenager stage. This phase takes between three and five years, during which—as any parent knows—rebellion can happen.

An important way to avoid rebellion is by making sure project and program managers see themselves as invaluable. They have the ability to see opportunities and risks that the portfolio manager cannot see. The portfolio manager must create this dialogue, which is part of maturing in the teenage phase.

Throughout this phase, the portfolio manager is working to overcome the remaining naysayers while tweaking the process, procedures, governance and metrics. This will take time as well, just as it takes a teenager time to mature into a young adult.

Adulthood

The final phase is, of course, full maturity. This is not a time for stagnation—if that takes hold it will be the death of the portfolio management team. Stagnation means the portfolio isn’t nimble or reactive to change—the opposite of agility.

Mature portfolio management means calibrating the portfolio as frequently as necessary to fit a changing strategy. Strategy today is not the strategy of yesteryear. Depending on the industry, the strategy may change every year. If there’s upheaval in the industry, strategy could change even quicker.

Can you fathom Apple updating its strategic goals only every three to five years? I can’t either. Reaching maturity for the portfolio manager means truly understanding the industry, becoming entrenched with the C-suite, making changes to the portfolio management process to increase delivery to the stakeholders. It means being agile enough to understand that change is needed.

During the process of portfolio maturation, the portfolio manager needs to consider portfolio rebalancing. This is a relatively new concept, and it was discussed during a breakout session at PMI’s PMO Symposium last year. 

The presenter suggested reviewing the portfolio mix at least quarterly to ensure strategic alignment. The larger point is that, as portfolio management matures, project and program managers should become more comfortable in re-estimating on a quarterly basis. By doing so, those projects and programs that are under-running may give back dollars to the portfolio.

Why is this important? First, it means that excess funds can be used for any projects and programs that are overrunning. But more importantly, these funds can be used to start new projects and programs to deliver increased benefits.

Posted by Wanda Curlee on: September 23, 2015 08:40 AM | Permalink | Comments (3)

Project Management Transforms Taiwan’s Uni Radio Station

linkedin twitter facebook Request to reuse this  

Under the leadership of Chia-chun Hung, PMP, Uni radio station of Taiwan has transformed itself.

Hung, whose father owned the radio station, was thrust into management at a young age when his father became ill. After becoming the station’s vice president in 2007, Hung took over the business in 2011 when he was just 28.

He had been endeavoring to improve the operation structure of the station, but with little success. But after learning project management concepts—Hung is the first PMP in Taiwan with a background in radio broadcasting management—he has successfully transformed the fate of the radio station. It’s now the most popular station broadcasting in the central part of the country.

But back in the midst of the global recession, a sharp advertising downturn was crippling the station. To reposition, Hung gave Uni station a new mission: deliver positive messages that promote social change, like “home and family.” The business operation was also transformed from advertising-oriented to program sponsorship.

Hung then translated the station’s mission into a tangible objective—become an influential platform—and embedded this objective into every project’s scope.

“Knowing the objective of your project right at the beginning makes you more focused, more aware of any deviation,” Hung told me in an interview. “In the meantime, we spent a lot time communicating with our stakeholders the concept of our operation, trying to clarify ideas.”   

Uni station’s programs consist of two types: those initiated by the advertisers themselves and those initiated by the station. In the former, the station helps the advertisers produce the program and realize their beliefs and ideas. In the latter, programs are produced by the station on its own, and the staff finds the appropriate organizations to sponsor them.

No matter which type, the station takes the lead in the production and helps the advertisers establish their brand’s image. The audience does not hear any advertisements during the program; the name of the sponsor is only given at the end of the show.

Seven years after Hung began Uni’s transformation program, the practice has gained the station a good reputation. Today Uni even “jumps down from the air to the ground,” holding seminars, family activities and campaigns—all in an effort to fulfill its mission.

Posted by Lung-Hung Chou on: September 17, 2015 11:29 AM | Permalink | Comments (0)

If Your Project Addresses the Wrong Problem, It Won’t Be Successful

linkedin twitter facebook Request to reuse this  

In my previous post, I emphasized the importance of engaging and involving stakeholders proactively in a learning process about project definition and planning. I highlighted soft systems methodology as a powerful problem-structuring method.

But how exactly can we incorporate problem-structuring methods into the project management practice? Are they really useful and feasible? Let me guide you through an example below, step by step, according to the Soft Systems Methodology.

Project: Build a New Power Plant

  1. Problem situation unstructured: Our energy supply isn’t meeting demand.
  2. Problem situation expressed: This expresses the area of concern through a rich picture containing both appropriate symbols for real-world activities and words.

Figure 1: Simplified rich picture for the project “Build Power Plant” (Trentim, 2013)

  1. Root definition: The purpose of the project is not to build a new power plant; the end objective is to deliver enough energy to the client. The client expresses the most important human activity system (HAS) to be further studied. We could define more than one root definition to represent a different HAS. For each HAS, we have an analysis of the customer, actors, transformation, weltanschauung (comprehensive worldview), owner and environment (CATWOE).
  • Root definition: to ensure that the client has enough energy.
  • CATWOE Analysis

Customer: client

                           Actors: sponsor, project manager, team and contractors

Transformation: provide enough energy

Weltanschauung: energy fuels operations

Owner: client

Environment: client environment

  1. Conceptual models: We could develop many models in different levels to better understand the problem. Simplifying, I’ve created a conceptual model of how the client uses energy, based on the root definition stated before.

Figure 2: Conceptual model based on root definition “to ensure that the client has enough energy” (Trentim, 2013)

  1. Comparison between conceptual models and the real world. This stage compares what we are now to what we want to be able to do. The conceptual model (or models) represents how things should work. The reality has to be changed in some way to improve the problem-situation.

Table 1: Comparison to reality (Trentim, 2013)

  1. Feasible desirable changes: The project manager and his or her team propose solutions (project scope). In stage 5, we compare the ideal conceptual model to reality, so we can propose feasible solutions and create action plans.
  2. Implement solutions: project execution.

Actually, the solution implementation might encompass all of the project life cycle. Stages 1 to 6 may happen prior to project initiation or in the beginning of the planning phase. Once we have the problem statement and the proposed solution aligned strategically to stakeholders’ expectations and needs, we can use our traditional project management knowledge, as compiled in the PMBOK® Guide, for example.

A successful project delivers solid benefits. That’s why we have to understand the problem before we start creating a solution. In other words, well-crafted plans and detailed scope definitions are useless if they do not address the real needs of stakeholders. Don’t you think?

Have you ever solved the wrong problem? Please leave your comments and thoughts below.

Posted by Mario Trentim on: September 15, 2015 04:42 AM | Permalink | Comments (18)

What Project Managers Can Learn From One Very Successful College Football Coach

linkedin twitter facebook Request to reuse this  

by Dave Wakeman

I’m always looking for a way to tie project management to college football, and the start of football season is a great time to do just that. I went to the University of Alabama, which has been on one of the greatest runs in college football history over the last nine years. This is due in part to the vision of coach Nick Saban.

If you don’t know much about college football and Nick Saban, you’re probably wondering what this has to do with project management. But Saban’s success stems in part from his coaching philosophy, which he calls “The Process.” His reasoning is straightforward, as he once said: “Process guarantees success. A good process produces good results.”

Here are several lessons project managers can learn from coach Saban’s process.

Culture is everything: Every organization has a culture. Some are well thought-out, methodical inventions imprinted through consistent actions and accountabilities. Other organizations, not so much.

At the University of Alabama, “The Process” is at its heart a cultural tool that seeps into every action that every member of the football program takes over the course of the year. Saban is consistent in his discussion of creating a culture that allows his team to focus on the aspects of their “jobs” that create success.

As a manager and leader of your projects, you might be able to deliver the same sort of project culture by clearly stating your expectations for communications, reporting or meetings—or all three.

Regardless of your priorities, take a look at how you can communicate the kind of project culture you want to create.

Success is a process: As leaders, we have to balance two competing interests: the long-term success of our projects and our organization and the short-term tasks involved in delivering us to the long-term outcomes.

One of the big things Saban has done at Alabama is emphasize setting long-term goals for each team and the program, while also consistently focusing his players on the task at hand. This most readily plays out in his insistence that his players focus only on winning the play of the moment, treating each play as its own mission and never looking at the scoreboard.

You might help your teams by setting clear long-term project goals, but then breaking them down into phases with each phase having its own individual stages with a beginning and end. More emphasis should be placed on the specific stage than the overall project.

Communication is key: The image of Saban as a fiery hard-to-please taskmaster may have some validity. But one thing that often goes unnoticed is that he’s typically toughest on his teams when they’re winning and have a tendency to lose focus. When the team is losing a game, he tends to be very encouraging and measured.

As the leader of your team, you can put this idea to work by looking at the way you communicate with your own team and think about what is and what isn’t effective. Maybe you’ll find you’re pushing when you should be nurturing or nurturing when a good push is needed.

Even if you don’t like Alabama, Nick Saban or football, you can and should learn lessons from college football. A great college football team is very similar to a great project team, and a great coach has to be a great project manager.

For your enjoyment, here’s a 60 Minutes TV show profile of University of Alabama’s team from a few years back:

Let me know what you think in the comments! And, most importantly, Roll Tide! 

By the way, I've started a brand new weekly newsletter that focuses on strategy, value, and performance. Make sure you never don't miss it, sign up here or send me an email at [email protected]

Posted by David Wakeman on: September 09, 2015 02:27 PM | Permalink | Comments (8)

How Portfolio Managers and Business Analysts Can and Should Collaborate

linkedin twitter facebook Request to reuse this  

By Jen L. Skrabak, PMP, PfMP

Just like portfolio managers, business analysts are gaining wide acceptance as a profession. Business analysts can now earn their own PMI certification (PMI-BA) and read their own practice guide (Business Analysis for Practitioners). (Here’s a piece of cultural trivia: Did you know the latest bachelor on the reality TV show “The Bachelor” is a business analyst?)

Portfolio managers should get to know business analysts in their organization, because they can help ensure alignment and management of the portfolio to achieve the organization’s strategic goals and objectives.

What exactly do business analysts do? They, well, conduct business analysis. That’s defined as:

•identifying business needs

•eliciting, documenting and managing requirements

•recommending relevant solutions 

With this in mind, there are four major ways that portfolio managers can leverage a business analyst:

1) Develop Pipeline Opportunities

Business analysts can play a critical role in analyzing business problems and opportunities that will eventually be used to initiate projects and programs in the portfolio. Product or technology roadmaps can outline potential projects or programs that will be initiated at future points. They’re also valuable during a project because they can support proposed changes to a project scope (which will affect the overall portfolio) and ensure that the business justification for the project or program remains valid. 

Many business analysts are embedded within business areas and are critical to early identification and understanding of future opportunities or changes to the portfolio.

2) Define Needed Business Capabilities

We often think of business analysts as documenting business requirements.  Those requirements are built upon an understanding of which capabilities are needed for a particular business domain. 

Typically, capabilities are based on the goals and needs of a particular business area. Those needs may be depicted through business domain capability maps, end-to-end process flows or functional diagrams. An assessment of whether the capabilities currently exist or not becomes the basis for identifying priorities and gaps (in processes or talent). It can also be used to benchmark against other companies.

3) Develop Business Cases 

With their high-level understanding of the goals, objectives and needs of the enterprise, business analysts can assist in defining the justification for the proposed solution. The basis of a business case is the needs assessment. This process seeks to understand the underlying business problem, assess the current state and perform a gap analysis against the future state.

In addition, the proposed solution (see #4 below) is needed for high-level cost estimates that become the basis for the numerator of the ROI. The potential return (denominator of the ROI) is also based on an analysis of the impact of the solution on the current process.

4) Perform Solutions Analysis

One type of solution analysis is to assess a variety of options to go from the current state to future state. (For example, process changes vs. system implementations.) Business analysts can work with business stakeholders to define immediate solutions (quick wins that may be process changes) or longer-term solutions (new products or systems). 

Business analysis outputs provide the context to requirements analysis and solution identification for a given initiative or for long-term planning. Business analysis is often the starting point for initiating one or more projects or programs within a portfolio. The analysis is an ongoing activity within a portfolio as the business environment changes and more information becomes available, creating new competition and strategies.

How do you work with business analysts? Share your experiences and best practices in a comment below. Also, if you’re looking to learn more about how business analysts can support practitioners, check out this pmi.org webpage.

Posted by Jen Skrabak on: September 01, 2015 04:37 PM | Permalink | Comments (29)
ADVERTISEMENTS

"A thing worth having is a thing worth cheating for."

- W.C. Fields

ADVERTISEMENT

Sponsors