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

A Recurring Interview Process Ensures a Good Fit

Promoting Project Management In Conversation

The Strategic Alignment of the Project Portfolio (Part 2)

The Strategic Alignment of the Project Portfolio (Part 1)

5 Steps to Manage Project Dependencies

A Recurring Interview Process Ensures a Good Fit

Great preparation goes into identifying the right project manager for the job—including determining the project’s delivery complexity, defining the role profile, selecting interview questions and validating professional certifications.

 

However, the interview process shouldn’t end once the new project manager is hired. A recurring interview process ensures project managers remain a good fit. It also helps showcase a project manager’s capabilities to instill confidence among leadership groups, stakeholders and team members—especially if elements drastically change, as they are wont to do.

 

Not every project manager is a good fit for every project. Original assumptions that lead to the initial acquisition of a project manager may not hold true as the project progresses. And poor outcomes often result from hasty decisions to get a project manager on-boarded as quickly as possible to start a project within a desired timeframe.

 

Here are three questions that not only ascertain the health of a project, but also the fit of the project manager. Depending on the outcome, you may choose to retain the project manager or replace them with someone who is a better fit.


 

1. Where are we now? 

Being able to confidently articulate and identify the true position of a project and the recent progress velocity to get to that position is a foundation of project management success. Failure to know where the project currently resides puts future progress at risk.    

 

Assisting the project manager in this determination of project position includes schedule and budget performance metrics, resource availability, dependencies, risk, issues and other inorganic position indicators. In addition, a project manager should be able to organically identify the “so what” implications and potential remedies required to create a three-dimensional view of project progress.

 

2. Where will we be in six weeks?

An old adage says that a point shows a current position, two points make a line and three points make a trend. Project managers should be constantly triangulating their project trajectory from their current position. If they can’t, they’re putting the project’s finish in jeopardy.

 

This six-week timeframe means a project manager can have a clear vision of the visible road ahead, but isn’t so far where they have to speculate well beyond a reasonable horizon.

 

Use of predictive quantitative methods and tools and prior project experience can help a project manager confidently state where the project is headed.

 

3. What changed from the original project scope? 

Change is constant. It takes many forms and has diverse impacts. Additions or revisions of functional requirements, technical requirements, different implementation approaches, new expectations, supplier complexity, unfunded mandates and other events make up the aggregate, ever-changing landscape of a project.  

 

While the project manager does his or her best to control identification, processing and action around changes, in some cases the aggregate impact of change can overwhelm.

 

In many cases, changes—such as leadership changes, new suppliers, as well as portfolio management actions that can merge existing projects—have nothing to do with the project manager’s capability. But when the depth and breadth of project change exceeds the capability of the project manager, it may be time to secure a replacement.  

 

What line of questioning might you use to ensure that a project manager continues to be a good fit for the project they were hired for? 

Posted by Kevin Korterud on: April 28, 2017 03:20 PM | Permalink | Comments (3)

The Project Manager’s Influence, Part 2

Categories: Stakeholder, Teams

by Lynda Bourne

In my last post, I discussed one of the more effective approaches for understanding team interaction: the McKinsey 7-S framework. The basic premise of framework is that there are seven internal aspects of an organization that need to be aligned for a company to succeed:  

  • Strategy: The agreed-upon approach to accomplishing the project’s objectives
  • Structure: The way the project team is organized, including who reports to whom
  • Systems: The tools, techniques, and processes used by the team to execute the strategy
  • Shared Values: The core values of the team that are evidenced in its culture and general work ethic.
  • Style: The behavior patterns of the team, how people interact, and their approaches to leadership and authority
  • Staff: The makeup of the team — “having the right people on the bus,” as Jim Collins writes in his book Good to Great
  • Skills: The existing skills and competencies of team members

Project managers can have the most impact on style and shared values. These elements are typically set at the beginning of a project and new team members tend to adapt based on what they see from their colleagues.

Changing these elements mid-project is difficult. If you start right, the tendency will be to perpetuate the good behaviors as the team grows.

However, if you need to spur a shift, I suggest taking these steps:

  • Start with shared values. Are they consistent with your structure, strategy, and systems? If not, what needs to change and how can those changes be implemented?
  • Examine the hard elements next. How well does each one support the others? Identify where changes need to be made. The project’s objectives don’t change but everything else can be adapted (including the strategic approach) to maximize the chance of a successful delivery.
  • Finally, look at the soft elements. Do they support the desired shared values? Do they support the desired hard elements? Do they support one another? If not, what needs to change?

As you adjust and align the elements, you'll need to use an iterative approach. Make adjustments, then analyze how those changes have impacted other elements and their alignment. This may sound like hard work, but the end result of better performance will be worth it.

What are your tips for shifting your team’s style and shared?

Posted by Lynda Bourne on: March 29, 2017 04:23 AM | Permalink | Comments (9)

The Elements of Team Interaction, Part 1

by Lynda Bourne

I’ve always thought the McKinsey 7-S framework is one of the most effective approaches for understanding team interaction. Originally focused on large organizations, the concepts are equally valid for smaller groups, such as project teams. Let’s take a look.

Developed in the early 1990s by McKinsey & Co. consultants Thomas J. Peters and Robert H. Waterman, the basic premise of the McKinsey 7-S framework is that there are seven internal aspects of an organization that need to be aligned for a company to succeed.

These elements are considered either “hard” or “soft”. The hard elements are easier to define, and management can directly influence them. They are:

  • Strategy: The agreed-upon approach to accomplishing the project’s objectives
  • Structure: The way the project team is organized, including who reports to whom
  • Systems: The tools, techniques, and processes used by the team to execute the strategy

The project’s strategy shapes the other hard elements, as the systems and structures used by the team need to support the implementation of the strategy — not work against it. The optimum structures and systems used in an agile project will be quite different, for example, than those used in a more traditional project.

The soft elements are more difficult to define, measure and document because they are influenced by personalities and company culture. They are:

  • Style: The behavior patterns of the team, how people interact, and their approaches to leadership and authority
  • Staff: The makeup of the team — “having the right people on the bus,” as Jim Collins writes in his book Good to Great
  • Skills: The existing skills and competencies of team members

The soft elements are probably more important than the hard elements. When you have a team made up of the “right people” (staff) with the “right skills” working in the “right way” (style) to achieve a shared vision, deficiencies in strategy, structure and systems can be mitigated.

At the center of both the hard and soft elements are Shared Values — the core values of the team that are evidenced in its culture and general work ethic.

As shared values change, so will all the other elements. But when all seven elements are aligned they have enormous power to generate project success.

Have you used the McKinsey 7-S model or something similar on your projects? How can this type of approach help drive team performance improvements?

Posted by Lynda Bourne on: March 24, 2017 06:57 PM | Permalink | Comments (15)

Playing the Right Leadership Role

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 (12)

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 (14)
ADVERTISEMENTS

"If I were two-faced, would I be wearing this one?"

- Abraham Lincoln

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events