Project, Program, Portfolio Management Office
Leaders define the vision. A business turns vision into value. It still takes a team of executives, managers, project managers, and individual contributors to drive the projects that build the capabilities to transform businesses. Ergo, projects are the enablers for turning vision into value.
The Vision to Value keynote is geared toward helping executives, finance leaders, technology leaders, and project managers understand what is required to enable the organization to share and stay focused on the company's goals, hence, reducing waste, increasing productivity, and decreasing waste.
People routinely ask me the question, "What do you do when you find yourself on a project that is a hopeless failure?" It was raised again a few weeks ago in a Focus.com roundtable and then last week in an interview with Andy Kaufman. It only matters if the executives above the project are ignorant to how dire the situation is. It is tricky, trying to convince someone that they have a problem when they refuse to acknowledge the obvious—a tough and politically dangerous sell. The general consensus is "dust of the résumé." However, there is a logical approach to the problem—be logical.
It is amazing how people on failing projects neglect to look at their own issues prior to blaming someone else. Yes, blame is easy and on red projects since no wants to be the source of the issues. The truth is, everyone is at blame, so before bringing in an auditor or recovery manager, tidy up your house first.
Let me be perfectly clear, I hate PMOs. It matters not if you call them project management offices, program management offices, or portfolio management offices, they only spell one thing—poor leadership. Now those of you that know me, have heard this enough times that your eyes are rolling back as you mumble, "Here he goes again. Who set the bait in front of him this time?" However, I have confused people with a couple of PMO articles that might seem contrary.
From her corner office, the new executive decried, "Decentralize the PMO. Let each department be responsible for their own projects." Maybe she had made a pact with another executive for some other bit of power, or it could be she lost a power struggle and the PMO had to go, or possibly she has little regards for project management thinking it is a mechanical, blue collar discipline that methodically follows a recipe to execute each project. Bottom line, she is missing the point of the Project Management Office (PMO)—it is all about business goals. Unfortunately, for the company, decentralized PMOs provide little if any value. They are similar to distributed teamwork—an oxymoron. The concept is illogical.
Last week I gave a presentation at the San Diego PMI Chapter's Tutorials conference. Flanking both sides of my ten o'clock presentation in the leadership track was Steve Romero. His two presentations were on IT governance. His energy, insight, enthusiasm, and passion (not to mention being the IT governance evangelist for CA Technologies) made him an excellent selection. And, what is so news worthy about that? Nothing. However, for someone that has little regard for adding one more layer of management to solve a problem, I was surprised that I sat through both of his presentations. He provided a three hours of information on governance—both PMOs and PPMs—crammed into two intense and valuable hours.
If you must choose between managing a project or building a team, start with the latter.
Teams run projects, not project managers. Projects fail without teams, plain and simple. Project managers need to start by building a team. Red, or failing, projects have an even bigger problem, the teams are beat up, demoralized, depressed and frustrated. The recovery manager must focus on rebuilding the team. Balancing this with finding the project's issues may seem daunting. Fortunately, many aspects of these tasks overlap and good leadership qualities make it even easier.
In a recent blog on stupid decisions, a reader asked about lessons learned processes. I had to defer the question since my reply would have been as long as the blog he was commenting on. So here we go: the entire class of retrospectives, postmortems, and lessons learned are a waste of time. Well, to be fair, I have never seen them work. They may have worked for others. Maybe the reason I never see them work is that I am involved only on disasters, you know, those projects everyone talks about for years to come, the ones people cannot get way from fast enough. Surely, the type of work I perform taints my experience.
Many companies have some form of a portfolio management group to manage their projects and their backlog. The projects they govern range from network pulls to new software development. However, most use only one methodology to run these projects. It may be waterfall, Agile, Critical Chain or some other process. This is analogous to having only one knife in the kitchen. Anyone that has cooked more than a few meals realizes that a table knife is insufficient for all your kitchen needs. It purees tomatoes, cuts meat poorly, fails at filleting fish and suffers as a steak knife. There are hundreds of knives, each designed to do some specific job. As with many jobs, some tools are better than others are for certain tasks.
The policy reads, "Before you can proceed, the PMO needs to approve the design gate." So, you begrudgingly wind down the project so the slowest members of the design team can catch up. A week, maybe two, sometimes even more flash by. The rest of the project team starts finding work on other projects. Once the PMO finally gives the project the green light, you will need to wait for people to complete those other tasks before they can focus on your project. Precious time is lost.