Program Guidance to Start Successful Project
The subpoena shows up at the front desk and the call comes to you to pick it up. That nauseating feeling in your gut is the prelude to a long day… no… a long year. The lawyers want every contract and statement of work, each change order, log, email, document, physical mail, specification, test document, picture, drawing, scratch note, etc. that ever existed on your project. You reflect back on the project and wonder how many times you cut corners in order to get the project done. Well as "done" as it is. After all, the customer never did really accept the final product. Maybe you should have had the project health check performed.
In May 2007, the Massachusetts Division of Unemployment Assistance (DUA) signed a contract with Bearing Point, Inc. to modernize the State’s unemployment processing system. The project was called the DUA Quality Unemployment System Transformation (QUEST) Project. Bearing Point filed for bankruptcy in February 2009 and Deloitte announced they would buy Bearing Point for $350MM in March of the same year.
"The government is incapable of running projects. Simply put, their miserably high failure rate proves that government should be out of the project management business." There are plenty of examples of this. We have heard this line, or ones similar to it, time and again and rarely hear how the projects failure reasons support the hypothesis. The reason? The prognosticators purporting this are part of the problem. Coming to that conclusion does not take any superior intellect—just listen to the nightly news. However, to try to get closer to the truth, I candidly and confidentially interviewed a number of government project managers and executives to gather their views. Following is a summary of those conversations.
In order to comply with the Affordable Care Act, the State of Oregon made the decision to build its own Health Insurance Exchange (ORHIX). An online portal to allow applicants was supposed to go live October 1, 2013. As of March 30, 2014 the site was not functional and all ORHIX applications must be processed from paper applications.
Decisions, deshmisions, what is the big deal? Anyone can make a decision! Hardly. After years of working with ineffective initiatives and consternated companies, I have a healthy respect for the D-word. It is all about the seven 'tudes—ineptitude, attitude, fortitude, altitude, aptitude, incertitude, and vicissitude. Some organizations obtrude the 'tude in which they are imbued, while others are denude of a common 'tude.
Months ago, maybe over a year, now, I was blasted for talking about innovation in the context of information technology (IT) projects. The gist of the complaint was that all IT folks think they are building some new groundbreaking, revolutionary application that requires the latest in technology's tools. I agreed with his argument, qualifying that although this seems to be a pervasive theme, IT is a discipline that needs to keep one-foot in the pioneering frontier. Regardless, I had to concede that many innovative initiatives are more about a technician playing with some new toy. Jobs like implementing ERP interfaces to manufacturing execution systems (MES) only sound new. Unfortunately, I must say, "been there done that." Most IT is neither new of innovative. To avoid squandering funds, executives must understand and direct what needs to be innovative and permeate the company's culture with that knowledge. Otherwise, the wasted time and expense will suck a company dry.
"Project management is easy. We have been managing people for hundreds of years. Just take any manager, give them a project, and tell them to get it done." Experienced project managers will accurately predict the end of this story—there is a disproportionate chance this project will fail. Rather than "manager" being the key noun, a leader is required to deliver project value on time and within budget. To distinguish the project manager further—functional managers need only manage subordinates, while successful project managers lead extended project teams. This fundamental difference drastically increases the project manager's scope of the responsibility, since the project team includes an entire flock of stakeholders.
With the coming of 2011, it is time to reflect on our past and contemplate the future. We think about our families, our friends, our successes and failures; we think about our jobs, our professions, and the world of possibilities. We must reaffirm our ship's direction, stay the course, make corrections, or find a new destination. As project managers, we must look at the recent changes in the discipline and translate those into a plan for our professional development—a plan that meets our needs and the needs of the discipline.
Most projects’ problems exist long before there is approval for the project to begin. Unrealistic expectations, misaligned goals, improper supplier involvement, and poor definition are a few reasons that projects go awry. Therefore, looking at different methods to start projects—getting engaged with the customer long before the project starts—is critical.