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.

The term path is used for a sequence of activities that are serially related to each other.

Imagine, for example, that your colleagues have decided to organize a barbecue. After dividing up the work, you are responsible for hiring the catering services. For this task, you are likely to have to look for recommendations, check availability and prices, analyze the options and then choose the best one. These four activities are a path. In other words, they are a sequence of activities that must be carried out sequentially until a final goal is achieved.

A project manager’s job is to estimate the duration of each planned activity. And if we return to our example, we could consider the possible durations:

Activity 1: Seek professional recommendations—three days

Activity 2: Make contact and check availability and prices—six hours

Activity 3: Analyze the options—one day

Activity 4: Select the best option and confirm—two hours

This sequence of activities will last 40 hours, or five workdays. And since the whole barbecue has been divided among various colleagues, other sequences (or paths) of activities—such as choosing the venue, buying drinks, organizing football, etc.—will also have their respective deadlines.

The critical path will be the series of activities that has the longest duration among all those that the event involves.

Let's imagine that the longest path is precisely this hiring of the catering services. Since the process is estimated to take five days, the barbecue cannot be held at an earlier time. And if it were held in exactly five days, all the activities involved in the path have no margin for delay. This means that if, for example, my analysis of options is not completed on the date or within the duration planned, then the barbecue provider will not be selected in time, which will invariably lead to the postponement of the barbecue—and leave a bad taste in my co-workers' mouths.

Under the critical path method, there is no margin for delay or slack. If there is a delay in any activity on that (critical) path, there will be a delay in the project. At the same time, other "non-critical" paths can withstand limited delays, hence the justification of the term.

It is the duration of this path that is setting "critical" information for all projects—when all the work will have been completed.

Do you use the critical path method in your work? If so, what are your biggest challenges?

We are experiencing a great contemporary paradox: In spite of state-of-the-art gadgets and collaborative communication tools, which should be streamlining and facilitating work, we feel increasingly burdened with more responsibilities and response requirements.

The clearest side effect is the epidemic feeling that we are always short of what we wish we could have read, produced or done.

Of course, the benefits that technology has brought us in recent decades are indisputable. The production of human knowledge has gained stratospheric scale. The world has become "flat"—economies are now deeply integrated, and long distances have been collapsed by hyperconnectivity. But this also means that a good share of the world's population can now compete for the same professional space as you and your company.

Perhaps this is why recurring publications about better management of time and its countless functions become the focus of attention for the most attentive visitors to bookstores.

When everything is urgent, in fact, nothing is. If everything has the same priority, there is no way for anything to stand out. Perhaps this is the central issue behind the stress so many people feel today. Once the urgency of demands is generalized, it becomes difficult to produce high-quality, timely results.

What’s the solution? Planning, planning and ... planning. Only a good deal of planning — structured and strategic — allows corporate and project leadership to stay focused on real priorities and meet the right attention needs of their teams.

For the individual, planning is also a personal survival tool for organizing and balancing work, personal and social demands.

It’s time to hit the rewind button on 2017 and look back on the year that was in project management.

And dang, it was a big year — full of ambitious projects that packed a punch. I’m still processing the €700,000 Museo Atlántico, an eerily beautiful underwater collection of 300 sculptures off the coast of Lanzarote, one of the Canary Islands — only possible with the project team navigating complex requirements and skeptical stakeholders. And though not without its challenges, the first phase of the Hyderabad Metro Rail — a massive public-private partnership project — pulled in more than 200,000 passengers on its first day alone.

That wow factor sometimes extends to what some might view as more mundane matters like the schedule. Elon Musk’s latest project adventure, for example, called for installing the world’s largest lithium-ion battery within 100 days — or it was free. Somehow scheduling matters don’t seem so pedestrian when there’s US$50 million riding on the project’s outcome. For the record, Mr. Musk and his team pulled it off.

The project is part of a plan to make Adelaide, Australia the world’s first carbon-neutral city. That push to sustainability is nothing new, of course. But it got real in 2017. Sustainability is no longer swathed in gauzy green layers. It has real strategic objectives — and is held to real metrics and governance.

The U.K.’s Crossrail team, for example, recently released a treasure trove of documentation highlighting its efforts to minimize disruption and pollution on the £14.8 billion rail project, which is expected to be completed next year. The results are impressive and could serve as a blueprint for embedding sustainability in other megaprojects. “Crossrail not only set a new precedent for delivery of a truly ambitious 21

st century infrastructure project, the strategic approach they took in managing the many environment and sustainability challenges was exceptional,” Martin Baxter, chief policy adviser for the Institute of Environmental Management and Assessment, told Railway Technology.

Even as the United States pulled out of the Paris Agreement, dozens of the country’s mayors signed their own accord on climate change. And U.S. business leaders — at companies across all sectors and sizes — didn’t miss a beat, launching their own projects to address the issue.

Yet such political disruptions — along with the Brexit bombshell — are clearly rattling the business world: More than half the CEOs in a KPMG survey said the uncertainty of the current political landscape is having a greater impact on their business than they’ve seen for many years. And those same business leaders know they must adjust their strategies. “All of these political events can have consequences on project planning,” John Greenwood, PMP, founder of Grand Unified Consulting, told PM Network.

There’s a reason disruption is such a buzzword: It’s everywhere. Today’s project environment demands an extra dose of innovation and agility (and probably a few extra shots of espresso). Just look at how many retailers and restaurants are experimenting with pop-ups — and relying on project management to tame the chaos. To achieve that so-in-demand-yet-so-elusive agility, you may want to check out the latest PMI Thought Leadership Series.

This is the stuff of Silicon Valley — and it’s fast becoming business as usual. Take cloud computing. Born in the valley, it’s now infiltrating every sector and forcing old-school businesses like telecoms to respond. Next-gen tech is being woven into the DNA of once-Luddite sectors, like agriculture and construction. Even the ultra-staid financial services sector is realizing full-on digitization is the only way to survive. Indeed, that push has spawned the fintech industry that extends to even emerging markets like Nigeria and India. The latter recently launched a project that saw 86 percent of the country’s cash go out of circulation overnight to be replaced by digital payment systems. Demonetization is the wave of the future, Gilles Ubaghs, principal analyst at Ovum, told PM Network. “It is already changing India, and it will change the world.”

That’s the truly spectacular thing about project management. It really does have the power to transform. No big shocker then that organizations are looking for the talent that can deliver those results.

A study by Anderson Economic Group and PMI found the project-management-oriented labor force is expected to grow by 33 percent in 11 countries through 2027. That’s 22 million new jobs. Whoa.

And as the first members of Gen Z are hitting the workplace, they’re already scoping out project management. They appreciate what they see: “I like the way you have to incorporate organizational skills along with people skills,” Myles Wilson, a junior project manager at Virtual1, told PM Network. “The idea that I could interact with many different people on a daily basis to achieve the same goal is something that inspired me to pursue project management.”

So at least one thing didn’t change in 2017: Project management still rocks.

As both a project and program manager, I’m always keen to have projects and programs take the right first steps toward success. In the past, this would involve selecting the unified delivery approach used for all of the projects on a program. The idea was to impart consistency to the way projects were managed as well as produce common metrics to indicate progress.

It’s not that easy anymore. Today’s programs have projects with agile, waterfall, supplier, corporate and sometimes regulatory-mandated delivery approaches. In addition, these approaches as well as the different arrangements made with suppliers (e.g., time and materials vs. fixed price with deliverables) have dramatically increased the level of complexity and diversity of delivery approaches within a program.

So as a program manager, how do I keep all of these projects in sync no matter the delivery method? As a project manager, how can I execute my project in concert with the overall program in order to maximize the value that will be delivered, while avoiding schedule and cost overruns resulting from projects not operating in harmony?

These are emerging challenges for which there are no single easy answers, of course. But I have found a handful of tips useful in getting a program’s projects to operate in a synchronized manner. I’ll share the first few in this post and the final ones in my next post, appearing later this week.

1. Remember: There’s No Such Thing as Agile or Waterfall Programs

Given the mix of project delivery approaches, the program needs to properly segment work to manage the budget, resources and schedule regardless of the project delivery approach. In addition, the schedule alignment points, budget forecast process and deliverable linkages need to be identified between the various projects.

Typically, I find that while there is effort to plan for these items at the project level, the upfront effort for this harmonization at the program level is underestimated or sometimes left out altogether—program managers think the project teams will figure this out themselves. This sets the program up for schedule and budget overruns as well as overall dilution of the program business case.

Some ways for a program manager to harmonize projects on a program include:

Determine which agile sprint cycles will be used for aligning data integration, requirements and deliverables with the other projects.

Forecast the number of agile sprint cycles possible given the program schedule and budget parameters.

Use an integrated schedule to constantly generate awareness of relative project progress within a program—no matter the delivery approach.

Identify key dependencies between projects in the program; this can include event, deliverable and external dependencies.

Use active resource management across all projects on the program.

2. Make the Correct Delivery Approach Choice Before a Project Begins

The type of delivery approach for a project is determined by the type of work being performed and the end consumer of the project’s deliverable.

For example, a project on a program that is slated to create a consumer portal would be a desirable candidate for an agile delivery method. Another project that involves heavy system integration that a consumer never sees would be a candidate for a waterfall approach. A project to pass data into a government system would likely have its delivery approach set by the governmental body.

So before a project starts, program and project managers should agree on the optimal delivery approach that is the best fit for the project.

Look for more advice in my next post on synchronizing a program’s projects, regardless of delivery method.

Have you been in situations where it seems that only shouting generates results? Or has your team been pressured to complete tasks that don’t appear to benefit your project? Maybe as the project manager, you have been in the middle of confusion and agitation that seem to undermine your project management abilities.

Could it be that many of the scenarios you encounter have their roots in conflicting stakeholder requests and misunderstandings? Well, it’s possible to avoid these types of predicaments. Consider utilizing the following three tools that allow you to have better control of your project and your project team:

1) Communications Plan. Outline a plan with names, contact information, and details on when and what messages need to be delivered to and from you. This tool allows you to know the frequency of message exchanges and the media required for specific contacts.

It also lets you know what level of detail the message should have, i.e., if it is going to a senior manager vs. a member of the supporting team.

2) Stakeholder Analysis. Prepare an analysis of your stakeholders to understand what their roles are and what area of your project is impacted by their involvement. This tool can help you with the department that has the biggest impact all the way down to the departments that have even a small effect.

Additionally, this tool can show how those who are directly or indirectly connected to your project may have an influence that can be detrimental.

3) Project Plan. Develop a plan with the focus on your project objectives and what the project will entail. Organize the plan for what needs to be done and when. The tool should show ownership and timings that you can share with stakeholders to also make them aware of the potential influence of their requests.

Sometimes, we get can get distracted when trying so hard to make sure our projects meet every need. There are many voices, conflicts, risks and events that affect the success of our project. Leaning on these tools may make your stakeholder management process smoother.