Articles by Richard M. Project Management A Killer Idea For Delivering Successful Information Technology Projects
7%-38%-55% Communications MythBy Robert P.
Top 10 Big Mistakes Of Big BusinessBy Francis T.
Climate Change Is Real! Act Now!By Kathrin G.
Improving The Quality Of Decision MakingBy Niladri R.
Knowledge Management And CreativityBy David G.
Top 10 Big Mistakes Of Big BusinessBy Francis T.
Best Practice Benchmarking - The Path To ExcellenceBy Robert C C.
What Is A Healthy Company?By Raymond H.
Challenges And Opportunities In The New EconomyBy Alkistis A.
Managing Bad Debt - Importance Of Good Collection SkillsBy GERARD A.
A Killer Idea For Delivering Successful Information Technology Projects
Why do IT Teams start building before they have it locked down as to what it is they must build? Let’s take a look at a number of reasons why I think they do.
In all of my audits and reviews of Information Technology (IT) project failures - large and small, we have found that the top reason for failure is the lack of agreed and controlled requirements. In other words, the project team did not have a clear picture of what the customer wanted the team to build and deliver. And, in cases where there had been a clear picture of the requirements at some time early on in the project, changes to that clear picture were made but were not controlled properly.
I’ve always tried to work out why a Team of people would start building something before they knew what it was they were supposed to build or before they had a clear picture of what it is they were supposed to deliver. It’s just plain foolish, isn’t it? It’s easy to see how foolish it is if you were dealing with a builder that you had hired to build your house. Before he started, you would definitely have blueprints, specs, etc. for the builder to follow. In addition, you would have agreed the cost and the delivery date. I know you wouldn’t just tell the builder to start without both of you understanding and agreeing the plans, specifications, costs and schedule.
So why do IT people do it? Why do IT Teams start building before they have it locked down as to what it is they must build? Let’s take a look at a number of reasons why I think they do.
One reason is that Senior Management, in most cases, are pushing for a delivery date that is usually very tight and usually not particularly feasible. So Project Managers feel like they need to take some short cuts to deliver on time. And one of the short cuts is to start working on what they believe they have to deliver before what they are supposed to deliver is documented and agreed.
Another reason is that the development team thinks that they know what the customer wants and, therefore, they think they can get a head start and begin working on it before they finish discussing and documenting what the customer really wants.
An additional reason is that there is no process in place that defines how to go about delivering a project and, therefore, the Project Manager makes it up as he or she goes along and decides that a Requirements Document is not needed.
Starting work on a project before you know what it is that you are supposed to deliver at the end is almost always a mistake - A big mistake. Why do I say almost always instead of always? Well, I can guarantee you that if I said always instead of almost always, someone would come up with an example that proves it should have been almost always.
So, take the time to get a Requirements Document prepared, agreed and signed by at least the developers and the customer. File it in the project library and put it under strict Change Control.
Some of the benefits of doing this include, but are not limited to, the following:
• You start off the project knowing what it is that you need to deliver,
• It provides you with a firm baseline on which to develop your cost and schedule estimates,
• It provides you with the basis for evaluating proposed changes,
• It provides you with the basis for the preparation System Test Specifications, and
• It helps in the communication process between you, the development team, and the client.
And last, but not least, it helps you, the project manager, deliver a successful project.
What's your opinion?
10 more Articles by Richard
2 min. When I'm running a Project, I want people to continually remember that we are on this project to achieve.
3 min. As a Project Manager, I feel it is important to have someone or some group you can turn to when you need help to get something done either in the client’s, ...
2 min. "Knowing what we don't know and tracking it is the only way to ensure that eventually we know what we don't know. Understand?"
4 min. The Project Manager must be able to have the helicopter view and understand the big picture and how his/her project fits into the overall scheme of things.
2 min. What is the one thing that most Projects lack? An abundance of time. Most Projects have a very tight schedule and anything that can be done to save time ...
3 min. "I believe that managing a project without the team co-located , especially if part of the team is working at home, is about as difficult as herding cats."
3 min. Success in PM is more about how you tell em' than what you tell em'.
2 min. One thing that I truly believe in is celebrating success on my projects. I know, a lot of projects have parties at the end of the project but I don't think that is enough.
3 min. I believe that a Project Manager should establish an Independent Test Team or an individual on your Project Team with the responsibility of ensuring, through ...