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
Marian Haus
Lynda Bourne
Lung-Hung Chou
Bernadine Douglas
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Roberto Toledo
Vivek Prakash
Cyndee Miller
Shobhna Raghupathy
Wanda Curlee
Rex Holmlin
Christian Bisson
Taralyn Frasqueri-Molina

Recent Posts

Playing the Right Leadership Role

How To Protect Your Team’s Time

Advancing the Program Management Vanguard

3 Sources of Project Failure

A Better Path Forward For Federal Programs

Playing the Right Leadership Role

Categories: Best Practices, Career Help, Change Management, Communication, Communication, Complexity, Education and Training, Facilitation, Human Aspects of PM, Human Resources, Leadership, Leadership, Lessons Learned, Lessons Learned, Mentoring, New to Project Management, PMOs, Portfolio Management, Program Management, Project Delivery, Project Failure, Project Planning, Project Requirements, Reflections on the PM Life, Roundtable, Stakeholder, Strategy, Talent Management, Teams, Tools

Leadership Role

By Peter Tarhanidis

It is not unusual for project leaders to fill a variety of leadership roles over the course of the many unique initiatives we take on.

As I transition from one client, program, employer or team to another, my personal challenge is to quickly work out the best leadership role to play in my new environment. Therefore, I find it helpful to have some knowledge of leadership theory and research.

Leaders must understand the role they fill in relation to staff and management. That typically falls into three categories, as defined by Henry Mintzberg, Cleghorn Professor of Management Studies at the Desautels Faculty of Management of McGill University, Montreal, Quebec, Canada:

Interpersonal: A leader who is either organizing the firm or a department, or acting as an intermediary. He or she is the figurehead, leader or liaison.

Informational: A leader that gathers, communicates and shares information with internal and external stakeholders. He or she is the mentor, disseminator, and spokesman.

Decisional: A leader that governs and has to make decisions, manage conflict and negotiate accords. He or she is the entrepreneur, disturbance handler, resource allocator and negotiator.

During one of my recent transitions, I thought I was a decisional leader, but I was expected to play an informational role. When I acted on information rather than sharing it and gaining consensus toward a common goal, my team was very confused. That’s why it’s so important to know the role you’re expected to fill.

When you start a new effort, how do you determine what role you’re expected to play? How has that contributed to your success?

Posted by Peter Tarhanidis on: March 17, 2017 09:50 AM | Permalink | Comments (8)

How To Protect Your Team’s Time

Categories: Leadership, Teams

by Christian Bisson, PMP

All team members must make—and meet—commitments to keep a project on track. However, it’s the project manager’s job to foster the conditions that will allow the team to deliver on its commitments.

Here are three tips to help you protect team members’ time — and ensure they’ll have the bandwidth to keep their promises.

1. Trust your team.

It can be tempting to ignore team members when they warn that there’s too much work to be done in a given amount of time. You may think they should simply push through. But if the project manager doesn’t commit to realistic deliverables—and find backup when necessary—problems just compound.

Take agile teams. It they commit to more work in a sprint than they feel they can complete, it will only make matters worse when unfinished work passes on to the next sprint. But if they commit to less work and get it all done, you might be surprised to find additional work added to the sprint, since the team is performing better than planned.

2. Clarify requirements and objectives.

A team can easily lose time trying to get up to speed. As a project manager, you can reduce confusion and delays by reviewing requirements and answering questions at the outset.

For example, if you’re working on a project with wireframes or designs, you may ask a team member to complete a simple task, like display the product page.

The team member that commits to this could then deliver half of what you expected simply because he or she didn’t have the full picture. Perhaps he or she thought only the desktop version of the page was needed and didn’t bother with the responsive design as you had expected. If you review instructions before work starts, you’ll have the opportunity to catch these types of discrepancies.

3. Protect their priorities.

If team members are constantly interrupted, their efficiency drops. You can help them focus in a few different ways:

  • Avoid ad-hoc status requests. Plan status meetings (i.e. daily scrums) or ask the team to reach out to you when they need something instead of you interrupting them to ask what they need.
  • Insulate them from changes. Changes are to be expected in projects — and it’s your job to deal with them so the team can remain focused on their work.
  • Be the shield. If another stakeholder — for example, a senior manager — interrupts the team with questions or requests, insist he or she go through you to obtain 
Posted by Christian Bisson on: March 09, 2017 09:13 PM | Permalink | Comments (8)

Advancing the Program Management Vanguard

Categories: Best Practices, Government, Leadership, Program Management, Project Delivery, Risk Management

 

In my last post A Better Path Forward For Federal Programs , I discussed how the Program Management Improvement Accountability Act empowers the Office of Management and Budget to create a program and project management strategy for the U.S. federal government.

The legislation also requires the heads of several U.S. government agencies—including the Departments of Agriculture, Department of Labor, Department of Commerce, Department of Energy and Department of Education—to designate one senior team member to serve as its program management improvement officer. In this role, the senior team member will be responsible for implementing program management policies established by the agency and developing a strategy for enhancing the role of program managers within the agency.

The program management improvement officer also has another set of responsibilities that I find particularly interesting. The law says the project management improvement officer must develop a strategy for enhancing the role of program managers within the agency. This includes expanding training and educational opportunities for program managers. This portion of the legislation creates a formal process for program managers to strengthen their existing competencies and allows project managers to develop into program managers (I once wrote a post on this topic).

Given the complexities inherent to contemporary program management, professional development initiatives will successfully prepare program managers for progressively larger delivery responsibilities. In addition, they will create an opportunity to centralize lessons learned on existing delivery programs for even more effective future program management.

Admittedly, when I first heard of this legislation, I was somewhat doubtful of its ability to influence program management results. However, after diving into the details, I’ve become an advocate. I’m excited about the new standard it will set for federal program delivery—and the prospects it holds for building similar program management capabilities in the private sector.

We may jest about the effectiveness of government regulations, policies and practices—but this legislation has the potential to significantly boost program management innovation in the public sector.

Do you believe the Program Management Improvement Accountability Act will spur program delivery improvements in your workplace?

 

 

Posted by Kevin Korterud on: March 02, 2017 08:05 AM | Permalink | Comments (11)

3 Sources of Project Failure

Categories: Best Practices, Communication, Leadership, Lessons Learned, Program Management, Project Delivery

by Dave Wakeman

In conversations with project managers I hear a lot about the causes of project failure. Here are three big ones that come up over and over again—and how to avoid these common traps.

1. Overpromising and under-delivering.

This will set you up for long-term failure because your sponsors and stakeholders will start to lose confidence in you.

While there are numerous reasons why you might go with this approach—from the inability to be truthful due to political pressure or a desire to please everyone—it almost always fails. When you make promises for the sake of not having to say no or wanting to please, you are just prolonging the pain.

Here’s how to avoid overpromising: When there’s pressure to come up with unrealistic promises, ask what is pushing these demands or why this timeline is important. Knowing the answer might help you prioritize parts of the project that can achieve those goals or help you reallocate resources in a more productive manner.

2. Micromanaging.

When pressures mount, it can be easy to think that we can or should step in to deal with any and every problem. But offering up ideas, thoughts, directions and other forms of advice meant to move the project along can often slow things down.

Micromanaging can feel good, but it is often destructive because it undermines the larger need to build trust and confidence in our subject matter experts (SME). If we don’t, we will find ourselves fighting a never-ending battle. We’ll try to stay on top of more and more as SMEs push back by not doing their best work because they feel we don’t trust them to do their jobs.

3. Withholding important information.

In my view, one of two things drives secrecy in projects: fear or lack of trust. Both often occur because you don’t have a good working relationship with your team, stakeholders or sponsors.

But as a project manager, your job is to manage the flow of communications into and out of a project so that smarter and wiser decisions can be made.

Set some guidelines and expectations for your communications with teams, stakeholders and sponsors. Then, as the project advances, judge your relationship against those expectations.

If you find that your information needs and expectations aren’t being met, you have to have a conversation with your team or stakeholders. Be clear with team members and/or stakeholders about how the information deficit is impacting the project.

The best project managers push themselves and their team to address uncomfortable situations before things get any worse. How have you built a project environment infused with trust and openness? 

By the way, I write a weekly newsletter that focuses on strategy, value, and performance. If you enjoyed this piece, you will really enjoy the weekly newsletter. Make sure you never miss it! Sign up here or send me an email at dave@davewakeman.com! 

 

Posted by David Wakeman on: March 01, 2017 11:01 AM | Permalink | Comments (11)

A Better Path Forward For Federal Programs

Categories: Best Practices, Government, Innovation, Portfolio Management, Program Management, Project Delivery, Strategy

 

 

By Kevin Korterud

 

Program management made news in December (though perhaps not front-page headlines) when the United States Senate unanimously approved the Program Management Improvement Accountability Act. The legislation enacted a number of initiatives for improving federal program delivery, which has suffered from past budget, schedule and quality challenges.  

While government legislation is not necessarily my weekend reading of choice, I recently spent time reviewing the new law. It quickly became apparent to me that, although targeted at improving the delivery of U.S. federal programs, it includes many considerations that are universally relevant to program delivery, even if you’re working in the private sector.

As part of the legislation, the deputy director of management at the Office of Management and Budget has been tasked with several new functions related to program and project management. Let’s take a look at two that I find particularly exciting and relevant to program managers around the world.

         

1. Chart A Strategic Course

Executives often tell me they don’t know where to start when it comes to improving program delivery. There are typically so many interrelated issues that it’s difficult to determine which actions would have the greatest impact on delivery results.

Other disciplines, such as technology architecture, business change management and customer satisfaction, typically work from some sort of strategic or transformational roadmap. The roadmaps identify common issues, solution strategies and transformational initiatives that drive success for that discipline.

The new federal legislation requires the deputy director of management to  “establish a 5-year strategic plan for program and project management.” A program management maturity roadmap will provide a common vision around necessary improvements. And given the size and complexity of federal programs, it will also help teams avoid repeating prior delivery missteps, and enhance the performance of program management processes.

 

2. Lay a Solid Foundation

Early in my project and program management career, it was common for companies to have a homogenous, centralized employee workforce with strong business and technical domain knowledge that was built over many years. Today, the landscape of program delivery is much more fragmented and fragile.

Global delivery centers, various delivery approaches (waterfall vs. agile), business leaders that rotate every few years, contractors that play a larger role in delivery and emerging technologies are all components that complicate program delivery. It is a wonder that program delivery is ever successful!

The new federal legislation says the deputy director must also, “oversee implementation of program and project management for the standards, policies, and guidelines…” The creation of program management standards, policies and guidelines will serve as a foundation to harmonize the discordant realities of modern program delivery. By establishing unified rules, boundaries, practices and performance metrics that drive a cohesive approach, the inherent complexities of today’s programs can be successfully addressed.  

 

What elements of the Program Management Improvement Accountability Act do you find most intriguing? I look forward to discussing. 

Posted by Kevin Korterud on: February 24, 2017 05:59 PM | Permalink | Comments (4)
ADVERTISEMENTS

"Education is an admirable thing. But it is well to remember from time to time that nothing that is worth knowing can be taught."

- Oscar Wilde