Project Disaster
Posted by Sajith M on Nov 28th, 2006
2006
Nov 28
A project (software project) is a disaster in the making when:
- you have a project that has vague requirements/unclear requirements
- you have a project that has an impossible deadline and/or budget
- you have a project that no one wants to be part of
One or more of these factors are a sign that you are on a project that is going the disaster way. These are three factors I could think of, what do you think?
PS: A blogger who happens to be on such a project might stop blogging for such a time, till the project gets over or is canceled (hint to Ekawaaz ;-)
Posted under: Technology , Software Development
Tagged with: Budget, canceled, disaster, impossible deadline, project, software project, vague requirements
November 28th, 2006 at 17:00:20
Very well chosen topic !! :)
You already have The Number One :
“you have a project that has vague/unclear requirements.”. This is a sure fire killer. No questions about it.
Other top one’s:
1. The Project Manager is clueless – and thinks it is unnecessary to understand anything more than the client name, and the end date. Rest are details meant for developers.
2. Ignoring the importance of Proto Typing, Proof of Concept – both a requirement and technology validator kind of thing. This simple measure alone has saved large projects from disaster.
3. Overdoing or Underdoing important aspects of the project.
Eg: Builds.
- doing builds thrice a day is a recipe for disaster.
- doing builds once a month is also a recipe for disaster.
Eg: Document Management.
- not having a SINGLE easily accessible repository of important docs.
- having the important docs in everyone’s email boxes but no central repository. hahaha.
4. Weak Leadership – Project Manager, Architect, Technical Lead.
Like in anything else – a strong leadership can carry the Mediocre. NEVER the other way round.
5. Refusal to accept the 20/80 Rule.
There will invariably be people who are more adept than others. Recognizing who these people are – and giving them the lead. It is important to differentiate positively.
Well… there are more.. but enough for now :)
December 1st, 2006 at 04:14:59
Ah ..lol I got your clue…lol good to see you back…well pass and fail is part of life..I am totally agree with your points and aswell Apun..Apun seems management gurur…:))
December 16th, 2006 at 13:03:39
Thats where you can use some requirement analysis, sometimes it might be as simple as that a few emails or a couple of phone calls can get requirements straight
Thats when you sit down and work out options… alternative ways to get things done, modify features, prioritise, talk to the client
Thats where the challenge lies, don’t always have to think like others
December 18th, 2006 at 09:00:19
Thanks for the comments Anish.
Agree with you Ekawaaz, Apun seems to be on track to be a management guru ;-) Thanks Apun for the insights :-)