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
Jess Tayel
Ramiro Rodrigues
Linda Agyapong
Joanna Newman
Soma Bhattacharya

Past Contributers:

Jorge Vald├ęs Garciatorres
Hajar Hamid
Dan Goldfischer
Saira Karim
Jim De Piante
sanjay saini
Judy Umlas
Abdiel Ledesma
Michael Hatfield
Deanna Landers
Alfonso Bucero
Kelley Hunsberger
William Krebs
Peter Taylor
Rebecca Braglio
Geoff Mattie
Dmitri Ivanenko PMP ITIL

Recent Posts

PMI + TED: Possibility Speaks

Adventures in Leadership

Disruption? No Prob for a Rogue Monkey Like You

Separating Standards and Knowledge Management

4 Tips for Project Closing Parties

4 Tips for Project Closing Parties

By Ramiro Rodrigues  

 

A great deal of effort is often put into a project kick-off meeting—so why isn’t that visibility just as important on the other end of the project?

 

What is a project closing party?

A project closing party is an event that intends to provide visibility and recognition to the main professionals involved in a completed project. Obviously, there is no sense in celebrating a project that got aborted or that didn’t reach its main goals and targets. So, we are talking about those projects that managed to get to end with the best combination of its intended results.

 

Within this proposal, it is reasonable to say that what will drive the size of the closing event will be the size (and budget) of the specific project, since it is necessary to achieve coherence between these variables.

 

What are the benefits?

I see two arguments for hosting these events at the end of a project—one strategic and one motivational.

 

On the strategic side, a closing party brings visibility to the executing organization (and, if applicable, the hiring organization) that the project has reached its predicted goals. It will help to reinforce to those at the strategic level of the organization that the team is capable and reliable.

 

From a motivational standpoint, these events will help recognize the efforts of the project team.

 

How should they be executed?

If you think a closing event could benefit your project efforts, here are some tips to abide by:

 

  1. Forecast the closing event in your project planning. It will allow you to make the proper arrangements of budget, time and resources.

 

  1. Manage expectations: Don’t hide the event, but also don’t overestimate what is forecasted in the plan.

 

  1. Honor the forecast: You can’t skimp on the event if it’s forecasted from the beginning—it will only leave a negative impression on the people involved.

 

  1. Gather people and acknowledge the merit: Just like in the kick off meeting, you should identify and invite the right stakeholders to witness the recognition of that specific team who performed great work.

 

Done well, events like a project closing party can have positive repercussions on your next projects.

 

Do you regularly host or attend closing events at the end of your projects? I’d love to hear your thoughts!

 

Posted by Ramiro Rodrigues on: April 17, 2019 01:07 PM | Permalink | Comments (13)

3 Tips For Assuming an Existing Project

As a project manager, there’s perhaps nothing better than starting a new project. With it comes a fresh start and the promise of a successful conclusion. To me, it’s akin to starting a new year in school with new notebooks, where nothing has been written to spoil the fresh sheets of paper.

 

However, as we become more experienced as project managers, we’re called on more and more to assume control of a project already in motion. This might be triggered by a happy event, such as a promotion for the existing project manager, or a less-than-happy situation, such as a lack of progress on the project.

 

Assuming responsibility for a project that has already launched is a lot different than starting from the beginning. You won’t have the benefit of starting with a clean sheet of paper, and there will be things you need to do—and undo.

 

Here are three tips I always follow when assuming control of an existing project:

 

1. Assume Nothing    

When starting a new project, you have the opportunity to perform mobilization and initiation activities to effectively set the project on a path to success. In addition, there are some early checkpoints where you can perform structured control actions to further assure the proper trajectory of the project.  

While the existing project status reports can show the assumed disposition of a project, they may not reveal essential missing activities needed for project success. For example, an existing project might not have had the benefit of a thorough mobilization and initiation effort to properly set its course. In addition, there may be hidden or under-mitigated risks, emerging issues, stakeholder challenges and hidden dependencies that have not yet come to light. 

When taking over an existing project, the first thing I do is review it in the same way I would a new project. Introducing a pause in project activities to perform a “soft reset” allows both confirmation of assumptions and validation of project progress.

In addition, this activity can reveal unseen factors that put the current project position in doubt. This is a good time to reforecast the remaining work. By assuming nothing about the project, the “soft reset” serves as a basis to properly transition the project towards success.

 

2. Match the Team to the Realistic Remaining Work  

One of the most important facets of a soft reset is reforecasting the amount of remaining work. Use the existing forecast as a foundation for considering other factors that may influence the future progress of the project. These may include effort, scheduling conflicts (e.g., year-end holidays), upcoming business process changes and technology-readiness dependencies. 

From the reforecast, compare these factors against the capacity and capabilities of the existing project team. Review whether you have the requisite skills and team members available for each phase of the project. In addition, consider the availability of key resources who cannot be readily substituted in case they are not able to work on the project. This examination of project resources by phase should include not only individual team members, but also team leads and third-party suppliers.

 

3. Engage More Frequently With the Most Accountable Stakeholder

While there are many inorganic components of a project, such as deliverables and status reports, often the most critical components revolve around the organic nature of people. Having strong executive sponsorship, a structured governance engagement model and open communication all enable project success.

When you are introduced as the new project manager on an existing effort, some change management work will need to be done to ensure a smooth transition.

Given the myriad stakeholders involved in a project, who should you start with? The typical consideration is to start with the most senior leadership stakeholder, who is typically also the project sponsor.

I think, however, a better place to start is with the most accountable stakeholder. This would be the person who after the project is implemented would manage the new solution to achieve the project objectives. In addition, this person would likely have the greatest knowledge of requirements and implementation considerations, which would be valuable to your soft reset.

 

Set Your Team Up for Success
When airline pilots transfer control of an aircraft to another pilot, they go through a structured process. Before control is transferred, the flying pilot does a check of instruments, course and speed. The pilot currently flying and the pilot taking over the controls exchange a distinct exchange of commands to ensure a precise transition and a safe flight.  

Assuming control of an existing project should have that same level of attention to detail and precision. Now that you are leading this existing project, be sure to consider the factors shared above that confidently allow you to say, “I have the controls.”

When assuming existing projects, what sort of activities do you perform as part of a transition? I’d welcome other thoughts to help make us all better project managers.

Posted by Kevin Korterud on: February 02, 2019 06:53 PM | Permalink | Comments (17)

Project Management for Business Transformation

Make it or break it!

In the world of Business Transformation (BT), project management plays a critical part in the successful delivery of the business transformation programs to an extend where I can say it is a “Make it or Break it”

And why is that?

Imagine a school music play and the effort required to coordinate everything to get it done successfully. Of course, there is a lot of planning, coordination and execution that goes into it to produce a high quality school play

Now imagine an orchestra and the effort required to get this done successfully. In essence and to the inexperienced eye, the tasks may be similar but the effort and complexity are just a different ball game altogether

This is the same thing when it comes to managing a non-BT project and a BT project. The main tasks of initiation, planning, execution, monitoring and closing may look the same on the surface but underneath the skeleton,  is a different level of complexity

Having said that, BT project management requires a different calibre of project managers to help get the beast out of the door while achieving business outcomes

To be on the same page, let’s define what business transformation is. Business transformation is a significant change that an organization goes through impacting its people, process and/or technology. The change is usually a complex one with long term business outcomes to be achieved   

Project management becomes the core part of delivering the business transformation and ensure that business outcomes are achieved. The calibre of the BT project manager is therefore a lot more complex and at a higher level of maturity. Below are the key characteristics for a successful business transformation project manager  

Exceptional Business Acumen

  • Ability to lose the jargon and speak to the business in their own language
  • Come from a place of wanting to understand what the business wants and needs
  • Makes no assumptions about what success looks like but instead co-create with it with the business
  • Understands the business vision and direction and how to best position the project to fulfil the business outcomes
  • Keep everyone accountable to achieving measurable business outcomes  

Visionary and can see beyond the short term goals

  • Able to mentally fast forward the current events to predict issues and resolve them early on
  • Proactively seek guidance and collaboration to ensure alignment
  • Understand the art of the unspoken word and the goal behind the goal
  • Able to manoeuvre and venture into the political landscape of the organization and foster relationship building

Can see different angles and prospective

  • Understand the business interdependencies, people impact and technology constraints
  • Able to see the logic in the various stakeholder groups’ points of view and make sense of them all to come to a well-rounded conclusion
  • Understand the different motives of the various levels in the organization i.e. executives, management and front liners

Diversified skill set

  • Having a diverse skill set is key in the success of BT project management. This allows the project manager to properly articulate what is required and most importantly see the missing links
  • Able to work better with the project team members coming from a land of similar experiences (not necessarily at the same level of depth)

Knows and understands failure

  • A project manager who have seen this, done that would have a higher level of exposure to different setups and problems which enriches their ability to problem solving
  • Have seen the good, the bad and the ugly means they can smell failure from a mile away and able to take action to set proper direction to avoid it or have the proper contingencies in place

Knows the job and acts beyond it

  • In the world of BT, project managers hardly have a job description to follow. For hiring purposes, yes they might have one but when doing the doing and working day-in day-out; they work on ensuring that the BT project is delivered successfully. This will take them beyond the scope of works to understand the wider environment of the project and resolve problems and issues that may “technically” be out of the project scope “the agreed baseline scope”
  • BT project manager does not say “Sorry, this is not my job!”

 

Posted by Jess Tayel on: January 31, 2019 06:44 AM | Permalink | Comments (13)

Do You Know The 3 Drivers Of Project Success?

by Dave Wakeman

I recently came across some of management guru Peter Drucker’s thoughts on project management. 

As often happens with Drucker’s writing, the lessons he wrote about many years ago are still applicable today. 

In his thinking about project management, Drucker came up with the idea that it really came down to three ideas: objectives, measurements and results. 

Let’s take each of these areas and think about how we should approach them today. 

Objectives: Many projects get stuck before they even begin, due to a poor framing of the project’s objectives. We should be undertaking our projects only when we have moved through the project-planning phase to such an extent that we have a strong grasp of what we are hoping to achieve. 

These objectives shouldn’t be fuzzy or wishy-washy. They should be solid and rooted in the overall strategy of the organization you are performing the project for. 

This means you have to ask the question: “Does this project move us toward our goals?”

If the answer is “yes,” it’s likely a project that should be launched.

If the answer is “no,” it’s likely a project that needs to be fleshed out more, rethought or not undertaken at all.          

Measurements: Drucker is famous for this adage: What gets measured gets managed. 

In thinking about project management, measurements aren’t just about being able to improve project delivery. They’re also essential to ensure the project is headed in the right direction. 

To effectively measure our projects, we need to have laid out key measurements alongside the project’s objectives. 

The measurements should be specific, with expected outputs and completion dates, so you can affirm whether you are on schedule, behind schedule or ahead of schedule. 

At the same time, the measurements should inform you of your progress as it compares to your strategic goals. 

Results: Ultimately, projects are about results. 

To paraphrase another great thinker, Nick Saban: If you focus on doing your job right on each play, you’ll put yourself in a position to be successful at achieving your goals.

Saban coaches U.S. football, but this works just as well for all of us in project management. 

If we are focusing our energy on tying our projects to our organization’s strategy, through this strategy we focus our project efforts on the correct objectives in line with our strategy. Then we use those objectives to measure our progress against the strategy. We should be putting ourselves in a position to get the results that we need from our projects. 

These results should be measured as positive outcomes. In Saban’s case, that’s wins. In your case, it might be a new technology solution, a successful new ad campaign or a profitable fundraising effort. 

To me, reviewing Drucker’s thoughts on project management is a reminder: Even though there is a constant pull of new technologies, never-ending demands on our attention and a world where change feels accelerated, sometimes the best course of action is to step back, slow down and get back to the basics.

 

Posted by David Wakeman on: January 18, 2019 10:02 AM | Permalink | Comments (13)

The Intersection of AI and Ethics

by Wanda Curlee

Imagine this: You’re walking in San Francisco, California, USA, when you spot an out-of-control trolley car headed toward a group of five people working on the track. You yell for them to get out of the way, but they don’t hear or see you. You’re standing next to a switch, which would send the trolley on a different track. But there’s one worker on the alternate track who, like the five other workers, doesn’t hear you or see the trolley.

You have a choice: Do you flip the switch? Do you take one life over five?

There is no right or wrong answer. It’s an ethical dilemma.

As project managers, we routinely face dilemmas, although they’re not typically as dramatic as the trolley scenario.

In project management, our answers to ethical dilemmas are typically driven by our moral compass or the company’s statement of ethics. Does that mean we are correct? Correct by whose standards?

The rise of artificial intelligence (AI) could bring new factors into our decision-making process. As project managers, we will use AI to make decisions or assist us with decision making. What the AI tool(s) decide to present can drive our decision making one way or another. What happens if AI presents us information that compromises the safety and efficacy of the projects? What happens if AI makes a decision that seems innocent but has dire consequences based on the logic tree—results that you, as the project manager, might not be visible to?

When revealing an ethical issue in a project management logic tree, it would seem that the decision making should be automatically deferred to the project manager. But whose ethics are used to decide when there is an ethical dilemma? What may seem a common decision to you is an ethical one to someone else.

AI is coming. It most likely will arrive in small bits, but eventually, it will be part of the project management landscape. So take steps to prepare now. Make sure you help with AI decision making when you can; participate in studies and surveys on AI and project management; study ethical dilemmas in project management and understand how the AI tool(s) are coded for ethics.

Be ready because project management is getting ready to change, not by leaps, but by speeding bullets in the near—and not so near—future.

 

Posted by Wanda Curlee on: November 19, 2018 02:58 PM | Permalink | Comments (49)
ADVERTISEMENTS

"Do not fear to be eccentric in opinion, for every opinion now accepted was once eccentric."

- Bertrand Russell

ADVERTISEMENT

Sponsors