Project Rescue and Recovery
A project manager's job is to deliver value. Achieving the original schedule, budget, and features is meaningless if the customer does not receive value. As with all simple statements, this much easier said than accomplished. Projects managers must assemble adaptable teams that use flexible, lean methodologies. Arrogantly selling the latest technology or tool is narcissistic. Focus on the customer. Be vigilant at ensuring the information is always available for the customer to reassess the project's value and for the project team to reevaluate their proposal.
"People say I am indecisive, but I am not so sure about that." I have seen this quote attributed to a former US President, but I doubt he actually siad this. First, it is too intelligent a comment for him and, second, he is far from indecisive. The liberal pundits trying to attribute that quote to him confuse indecision with defective decision making. You can figure out who the President is on your own; however, it is irrelevant. This article is about leadership not politics. Organizations confronted with a decision-challenged individual in a leadership role, is adrift in the sea of serendipity. They bobble around having no direction.
"I just want to be a project manager. I don't want all that responsibility." The room was silent, save a few exasperated sighs. We all looked around trying to figure out how we would handle the comment. However, there are many levels of project management maturity and only the highest levels require leadership. In fact, the prominent certification process—PMI's PMP®—has little to do with leadership until 2015. So where do we learn about leadership and how can we improve our leadership skills?
The system integrator is the magical troupe that works with the customer and the software vendor to deliver a project's desired functionality. They cut through the vendor's promises while controlling the customer's expectations to create a successful deployment. Mike Krigsman refers to this triad as the Devil's Triangle; all three parties are culpable in the failure and share in the success. However, the system integrator is responsible for holding the three together to achieve successful delivery. The cornerstone to this relationship is a thoughtfully built contract.
I have always enjoyed being part of team building exercises. The one where you close your eyes and fall backwards hoping that your team members catch you is my favorite. It reminds me of an amusement park ride. There is always the thought in the back of my mind that some trickster will let my head crack on the floor. I think it adds more excitement. However, team building exercises only go so far and normally fail to reach their objective. They are too transient. The event happens, the manager checks off the list to show the task is done and he or she goes back to managing the team with status reports, task assignments by email and visiting people only when something goes wrong.
"Networking? I am just not good at that." I hear this time and again. With the recent financial issues in Europe, the line is repeated with a frequency reminiscent of 2009. So, it is time to pull out the pom-poms, put on the short skirt, and be the cheerleader chanting its virtues. For those of you that know me, the visual may be a little disturbing, but I conjure it up with your best interest in mind. The fact is, most of us dislike networking. After all, "work" is its middle name. It is, however, how people do business and find jobs. No argument, it is difficult to approach total strangers, publish an essay for the world to critique, or launch a tweet into the ether's unknown, being fully aware there is no way to delete a disgruntled individual's flame-o-gram on your dissertation. It takes guts to air ideas for others to appraise, "like," deride, or amplify. The best way to start, however, is to jump in and immerse yourself. An acquired talent, networking takes practice and it is more than face-to-face interactions.
Nothing starts your day worse than waking up to a CNN News crew on your front porch. That is what happened with Cover Oregon (Oregon’s failed HIX implementation). Now, with multiple lawsuits filed, only time will tell who the real losers are. One thing is for sure—there will be no winners. With all the contracts, audit reports, and court documents in the public domain there is no better time to learn.
Estimates for the annual cost of project failure are as high as two trillion dollars a year. The rates for projects being at risk are in the 60-70% range, and a quarter of all project's problems are so bad they are simply canceled prior completion. Preferably, all projects will run according to plan. However, moving from a 60% failure rate to 0% is unrealistic. First, organizations must understand what it is that makes their projects fail. Reasons range from methodology to human failure to poorly understood concepts to scope creep. Analyzing projects as systems uncovers all the factors that can contribute to failure.