by Kevin Korterud
The technology found in today’s automobiles is simply amazing. Front and side traffic radar units, anti-dozing head movement detectors, driving timers that alert drivers when they should stop for a break — all good examples of accident prevention mechanisms.
Projects to some degree are like automobiles: They are on a journey to deliver passengers (the project team and stakeholders) to a pre-determined destination. However, despite the introduction of many modern project management technologies, research shows that we continue to experience project accidents. These accidents result in extensive and costly rework to get a project back on track.
I think part of the solution to avoid these potential problems is to borrow from recent automobile technologies as a way to detect troublesome signals. These signals are not readily perceivable from traditional project management methods.
Here are a few examples of anticipatory signals that portend the onset of a skid that often leads to a project accident.
A core competency of a project manager is to determine the schedule, budget and progress trajectory of a project. The project forecast is essential to determine where the project will finish for these measurements. Schedule, budget and progress forecasts from team members that exhibit great degrees of change over prior reporting periods are indicative of trending to an accident. This downward spiral is exacerbated when the forecast measurements come with great uncertainty; e.g., “I don’t know what this will take to finish.”
Several techniques can be employed to reduce the volatility of forecasting. Some of these techniques include initiating a peer review of the forecast with another project manager or supplier subject matter expert, as well as pausing the project to recalibrate the forecast in a dedicated working session. Taking time to implement these and other techniques to mitigate forecast volatility will get the project back on track before an accident.
2. Static Project Status
Project status reports can offer a tremendous amount of value to a project manager. They accumulate both qualitative and quantitative data that sheds light on the current project state. But, despite the visibility status reports provide, they’re just a snapshot. That limits their ability to show progress trends. In addition, a project status report that does not show content changes week over week indicates that the project is likely stalled and headed toward an accident.
To increase the anticipatory value of a project status report, introduce trending and predictive data for risks, issues, deliverables and milestones. This allows the project team to determine what level of progress has been achieved, as well as what progress to expect. It also better positions the project manager to escalate mitigations to avoid an impending project accident.
At the beginning of a project, stakeholder engagement and enthusiasm is typically high. This is not unlike the start of a road trip. But, as time passes on a project, the level of enthusiasm and engagement can begin to wane. Stakeholder engagement over time will face tough tests from project risks to resource challenges to dependency conflicts. Each can sap the energy levels of stakeholders. This leads to passive engagement at best and complete disengagement and absenteeism at worst.
To keep stakeholder engagement at the proper level, stakeholders need to be treated like any other resource on a project. Their time needs to be managed in work plans to avoid oversubscribing their capacity. In addition, their work should be focused on higher value activities that promote project progress. Providing the team access to project support staff to maximize productivity also helps further stakeholder engagement and leads to persistent engagement.
Perhaps one day in the future there will be technology solutions that provide anticipatory signals for projects headed for an accident. Until that day comes, however, project managers still need to think organically and look for hidden signals of dangers to project budgets, schedules and progress.
What do you see as the leading indicators that a project is trending toward disaster?
Lead With Value
by Dave Wakeman
Where do you stand on the value vs. benefits debate?
As someone who spends most of my time managing projects in marketing and revenue-generating roles, I likely see the idea in a much different way.
To me, value is the most important thing that you can sell to your sponsors, stakeholders and your team.
I think it’s pretty simple: If you are selling benefits, you have allowed yourself to slip into the world of commodity.
As the need increases for project managers to advocate for resources and execution in projects, it’s important that we don’t give weight to commodity thinking. If we allow ourselves to become a commodity, it becomes much easier to ignore our project, cancel the project or not give the project the resources it needs to be successful.
Value, on the other hand, allows you to explain your project in terms of impact. And if your stakeholders, sponsors and team see the impact and the improvement of what your project will mean to the organization, community or stakeholders, it becomes much easier to sell the importance of the project, the need for resources and the benefits.
Here are a couple ideas on how you can prioritize value in your projects.
Lead with impact. Think about how the work you are doing is going to improve people’s lives, the success of an organization or some other high impact measure that will get people excited.
Here’s an example: In working on the New Year’s Eve ball drop in New York’s Times Square for several years, I could have easily said my main job was to make sure that I expedited people’s access to the restricted areas, hastened the process of getting people in and out of Times Square and ensured that the primary entertainment events went off in a timely manner.
That would be missing the point. The impact that I created was that I ensured that the logistics of the ball drop didn’t stand in the way of people having a safe, enjoyable New Year’s Eve experience.
In the first example, those are just commodity activities.
But if I do the job of selling the value the right way, it’s much more likely that the project is going to go through in a way that I hope for.
Don’t just think of the tangible benefits; think of the intangible benefits too. The core of the benefits argument is that tasks are the only thing people value in business or project management.
As someone that started out my career working in entertainment exclusively, I recognized pretty early on that what people view as a benefit often is independent of what they are actually getting from physical goods.
For all of you thinking about value over benefits, this boils down to tangible versus intangible value.
If you are selling the value of your projects, and you want to increase the impact of your conversation, focus on impact. Think about it from both the tangible and intangible angles.
The tangible value in your project might be how much more money they are going to earn, how much money they are going to save or how much more efficient something will be.
Your sponsor or stakeholders might really be much more excited by less stress from commuting, in the case of a mass transit or road project. They might find that the reduction in time allows them to spend more time at home with their family.
Or, the intangible might be something else entirely.
The key is to not allow your project to just become a checklist of activities. If you do, you are likely dealing with commodity status and no project team does their best work in that situation.
High-Performance Teams Are Purpose-Driven
Education and Training,
Human Aspects of PM,
New to Project Management,
Nontraditional Project Management,
Reflections on the PM Life,
Categories: Benefits Realization, Best Practices, Career Help, Change Management, Communication, Complexity, Education and Training, Facilitation, Generational PM, Human Aspects of PM, Human Resources, Innovation, Leadership, Lessons Learned, Mentoring, New to Project Management, Nontraditional Project Management, Program Management, Project Delivery, Project Failure, Reflections on the PM Life, Risk Management, Stakeholder, Strategy, Talent Management, Teams
By Peter Tarhanidis, Ph.D., M.B.A.
Program teams should collaborate like a world-class orchestra.
This ideal state of team engagement and performance requires the presence of several key elements, including an engaged sponsor, a governance committee, a project manager and a status dashboard to communicate performance.
However, maximizing this level of performance is especially challenging when working with cross-functional groups, external stakeholders and shareholders. This increases the complexity of the human performance aspects of team management.
I recall one assignment I worked on that required the team to design and build a new centralized model to bring together three different operations. The team was given two additional challenges. The first challenge was to consolidate disparate teams into two geographic centers. They also had to reduce the overall timeline from 18 months to 10 months.
These challenges exacerbated how teams were not working well with their counterparts. They quickly became dysfunctional and lost their purpose. The project was crashing.
Stepping into this situation I decided to conduct a stakeholder analysis. I used this approach as an intervention method to understand the underlying themes. The analysis revealed the team:
After reflecting on the team’s feedback, I realized that most members wanted to find meaning in their work. It seemed no one was developing their sense of shared purpose and putting their strengths to work toward this program.
I decided I needed to re-invest them as members of the team. To get the team back to performing well, I:
This approach strengthened the program and delivered on the challenges.
The lesson learned is, do not simply apply methods and approaches in complex program delivery. Manage the team’s purpose and establish shared values as an important driver of overall delivery.
How do you manage that purpose and invest in high-performing teams?
By Wanda Curlee
In my last post, I discussed the project manager-powered management model that centers on neuroscience and people. Many models that discuss project management forget that people are the center of a project team. It is the people that have the power within the project.
Below is the model—let’s look at it in more detail.
By keeping the triangle in balance, the project success rate increases to 60 percent.
Time is the anchor as it can’t be managed. After all, time is constant — a person can’t make it go faster or slower.
Variables are on another side. They incorporate all those items that affect the project or program, including environment, politics, lack of resources, risks, opportunities and more. The effects of the project or program can be positive or negative. Hence, a powerful sponsor can increase the project’s success rate.
Finance is the final side. The word finance was chosen deliberately. Today, there are many ways to support a project or program. It may be normal currency. But financial support could also come in the form of bitcoin, credit cards, loans, various apps used to exchange money and even bartering. Each type is no better or worse than the other. In the future, there may even be something different that has not even be envisioned today.
Project or program managers and their teams have to keep the triangle in balance. If one side falters, the triangle collapses — hence the red bolt in the middle.
The project manager should lead efforts to keep the triangle in balance and drive results; the project team has the power to accomplish tasks.
The entire model is based on human emphasis, which is predicated on neuroscience. And once project or program managers understand the foundation of what drives human behavior, they can then motivate and drive projects to success.
However, the project/program manager has to have a sense of pAcuity: The “p” is project, program, or portfolio, while acuity means keenness. The leader, along with the team, has to have the keenness to take the project/program/portfolio in the right direction by understanding how to harness individuals’ power. Individuals, then, need to have the keenness to assess what is going on around them to drive the tasks to completion. This is done through neuroscience or understanding how we as humans think.
Stay tuned for my next post to understand the brain and how it drives us to perform on the project or program.
Award-Winning Metrics For 2018
by Kevin Korterud
What are the best metrics for determining if a project is about to experience schedule, budget or quality slippages? These metrics are best categorized as delivery volatility metrics.
Executives already know when a project is in trouble — they are more concerned with those projects whose trajectory is on a currently unseen course to trouble.
PMI offers guidance on project metrics to help detect delivery volatility, such as the Cost Performance Indicator and Earned Value Management. While project reporting will likely have one or more of these metrics, I got to thinking what other metrics would indicate the potential of delivery volatility.
An additional complication is the various approaches used today, including agile, waterfall, company custom, software product, service supplier and regulatory. These can all generate their own set of metrics.
While pondering this question watching TV one evening, I noticed a multitude of movie, theater, television and music award shows that tend to occur this time of year. A characteristic of these shows is the numerous categories that are awarded to nominees — Best Supporting Actress, Best New Pop Group, Best Special Effects and so on.
As I was organizing my thoughts around metrics, I figured: Why not use award show categories to help shape an answer on which metrics would best suit early detection of delivery volatility?
As the Master Of Ceremonies for the 2018 Project Metrics Award show, here are a few of the winners:
As our projects become more complex and more numerous, the ability to deliver on a set schedule becomes more important. The SPI has the great benefit of comparing actual and planned progress in an objective manner: earned value/planned value.
The true power of SPI comes into play when selecting a method for earned value accumulation. Assuming work plans are at a level of granularity where task progress can be measured within a two to four week window, a conservative earned value scheme such as 0%/100%, 25%/75% based on task start and completion is a very objective means of calculating progress.
With these conservative schemes, you capture value when the tasks have started (when resources are truly free to work on tasks) and whether the task has been completed (usually with acceptance of completion by a project manager or stakeholder).
Given today’s tight delivery timeframes, as well as the need to coordinate delivery with other projects, SPI is a good indicator as to the schedule fitness of a project.
2. Best Supporting Emerging Metric: Functional Progress Metrics!
As I shared above, there are now a multitude of methods available to run projects. From these methods, all sorts of new metrics are available to project managers to identify delivery volatility. These metrics can include completed user stories, forecast backlog, project burndown, build objects, test case performance and many others.
In addition to these new metrics, a whole host of new waterfall, agile and other tools have come into play that capture functional progress outside of the traditional work plan tasks and milestones. In fact, work plan detail requirements can be relaxed when these tools are used to shed light on the functional progress of a project.
The power of these functional metrics is that they allow the next level of inspection underlying project phases, tasks and milestones to see delivery trajectory. For example, being able to see the detailed completion progress of requirements, build objects and test cases in automated tools allows project managers to catch underlying barriers to progress before it is revealed in a work plan.
As project managers, the universal outcome for our efforts is that we need to create value for our project executives and stakeholders. While activities can lead to creating value, our mission revolves around the production of deliverables in a timely manner to fulfill a project value proposition.
The inherent power in providing and approving deliverables in a timely manner is that they are completely objective means of progress. No matter what method, effort, dependencies, resources, tools or other constructs of project management are employed, deliverables are an indicator of whether you are making progress. The track of deliverables being created, reviewed and approved on schedule means you are making definitive progress toward value.
Creating a track of deliverables and their targeted completion dates with progress that can be monitored through other metrics allows a universally understood path to project completion. For example, if a deliverable has not yet been approved by stakeholders, you are making visible a potential schedule delay that would impair future work activities.
To host your own 2018 project metrics award show, one does not need a spotlight or trophies. You just need to think about what metrics can serve to detect early signs of delivery volatility beyond the self-declared green/yellow/red stoplights that are typically found in project status reports.
If you were handing out your very own 2018 project metrics awards, what categories would you select? What would win?