There is no worse person to be than the project manager at the end of a failed project. As an IT project manager, I have experienced that feeling and I can tell you it's not nice. IT projects are particularly difficult to manage. In fact there really aren't any IT projects, just projects that have elements of IT in them.
The trouble with these projects is that often you are doing something that hasn't been done before, is unproven or cutting edge. Customers expect a good result not excuses, even though these projects are frequently a journey into the unknown. If we take the construction industry, building a new bridge for instance, we have been building bridges for hundreds of years and know how to do it. We understand how things are going to happen, in what order and the expected result. This is rarely the case with IT projects.
Avoiding the common pitfalls of IT project management is not rocket science; it is simply a case of taking some sensible measures. Identified here are five killer mistakes of project management:Who Owns the Project?
The Mistake:
The nature of projects is change and change often encounters resistance. People don't like change so they need to know it is necessary and what benefits it will bring. In order for a project to deliver change it needs the backing of senior management. Without it the project will proceed very slowly. The sponsor (senior management) is the person that drives the change forward and the project is the mechanism for change. A project without support from senior management will struggle.
The Solution:
Make sure you have the top down backing from senior management. There must be direct communication from the sponsor to the stakeholders. The message must be, "we are serious, this thing is going to happen so you are either with us or you are not" and beware those that are not.
Be careful as project manager to make sure the sponsor does not take the project over and become the de-facto project manager.
Getting Users Involved
The Mistake:
Lack of user input and involvement is the recipe for a bad project. This can either be because of the "we know what you want" mentality from the IT department or lack of interest from the customer. Either way it must be avoided.
The Solution:
The IT department must take time to understand the customer's requirements before proposing any technical solution. Often IT is blinded by the latest, newest thing available and try to shoehorn the requirements into it. On the other hand, customers must devote the time and effort necessary to ensure a successful project by interacting with the IT department and making sure all requirements have been fully defined. Ensure you have spoken to all stakeholders to gather their requirements and that they continue to work with you for the duration of the project.
Stopping Scope Creep
The Mistake:
Scope creep is the cause of more project failures than anything else. Not knowing exactly what a project is aiming to deliver or setting off in a fit of enthusiasm, but little else, is a recipe for failure.
The Solution:
Ensure that the business case, requirements and scope are clearly defined and documented. Make sure the stakeholders understand them and sign them off. Stick rigidly to the scope and if changes are required then put them through a change management process where they are documented, justified and then agreed upon.
Managing Expectations
The Mistake:
Often there is an expectation that IT is like a magic wand you wave and suddenly a miracle occurs. During a technology project, expectations can inflate to a ridiculous degree. It is the role of the project manager to manage expectations to a sensible level.
The Solution:
One way to avoid this is to break a project into smaller pieces or phases. I equate this to a sausage machine, where you feed in the raw material at one end and out it comes as small, perfectly formed, packages or sausages at the other end. The same can happen with IT projects where you take small packages of requirements and push them through the machine, producing several deliverables over the life of a project. This way you manage expectations by making frequent deliveries to demonstrate what the technology can really deliver. This approach ensures the project delivers to the customer's expectations by giving them early visibility of what you are building.
Understanding the Lingo
The Mistake:
Have you ever stood next to a group of IT professionals and wondered what on earth they were talking about. It is like a whole new language and to non-IT people it often is. The pitfall comes when the customer and IT think they are talking the same language when in fact they are not. This leads to a problem when the IT department delivers what they understood the customer wanted and it turns out to be something different.
The Solution:
Communication problems are the hardest to resolve as often it is only by looking back that the problem is identified. Regular communication and a close working relationship with the customer will help. What you really need is a person with a foot in both camps, who understands the business and the IT equally well. If you can identify this person make sure you keep hold of them, they are hugely valuable. If you are unable to find this person, the next best option is to have two people, one from the business and one from IT. By working closely together and sharing information they can minimize any communication problems.
Finally
In 1995 The Standish Group surveyed IT executive managers for their opinions about why projects succeed. The three major reasons given that a project will succeed are user involvement, executive management support, and a clear statement of requirements. Concentrating on these three aspects alone will give your project a good chance of success.
Don't become the victim of a failed project, put measures in place that will ensure your success.
After all it's not rocket science!
Don't forget to leave your comments below
Duncan Haughey, PMP is the editor of Project Smart, the project management resource that helps managers at all levels to improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With regular updates it keeps you in touch with the latest project management thinking.
Subscribe to this comment's feed
written by sfgilani, September 17, 2009
-
- +0
-
-
written by Renaud, September 17, 2009
-
- +0
-
-
written by ssolyom, September 17, 2009
-
- +0
-
-
written by martin62, November 19, 2009
I am not new to project management, but I am new to the "theory and literature" as I am currently enrolled in certification program. What surprises me as a read through the literature and the case studies (my program uses IT as the base model), is what they come up with are things like (as with the NWA ResNet case study I just read) the "key to project success was a clear vision and an align of the project with business objectives". Well duh!! What are you going to tell me next ... 2 plus 2 equals 4? The other gem they went on about was this innovative thing where they engaged users in defining system functionality! Yeah? .. what were you doing before, consulting Tarot cards?
I am a social scientist (economist actually) and my project work is in the world of international development aid, so maybe I do not understand the significance of these little revelations as my project management life is all about coommunications, stakeholder involvement and consultation. In my world, the project management issue is transition planning. For some reason the "duh" factor is that the objective of projects should be the sustainability of project benefits/outcomes post closure! Well, try to deal with that apparently 'obvious' issue in the development aid world!
I guess the things is, if all this was easy, then everyone would want to do it.
Enjoyed your article greatly!
Cheers
John Martin
-
- +0
-
-
Click Here to login or create a free account.
