IT Project Failure Warning Signs
This list was adapted from ITBusinessEdge
Lack of governance: Project criteria, roles, processes & outcomes not used or accepted by management. Not understanding project risk.
Internal politics: Territorial fights. Its not my job, or “they” messed up.
Communication issues between the business and IT: IT talking with the business stakeholders about bandwidth and blobs rather than end user oriented benefits.
Unclear expectations: Bad estimates and ambiguous expectations.
Lack of fact based analysis: Plans not based on facts but on opinions. Studies have shown, for example, that projects of any magnitude can’t produce a viable estimate without a model like SEER.
Lack of input from users: IT may know how to do it but users probably know what they need better.
Changes in project without re-planning
Unplanned changes in key personnel
Unrealistic schedules: Projects on death marches.
Unanticipated operations costs: These must be estimated well up-front
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Off Topic: Estimating the Occurence of Phantom Traffic Jams
Estimating the slowdown on the freeway. Interesting article from Wired quantifies and estimates the occurrence of phantom traffic jams. You all know them… traffic slows to a crawl. There must be an accident. But no, it is just a phantom traffic jam. Living in Los Angeles I find this really interesting.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
New Code Counter Update Available from USC
The University of Southern California has been developing and updating line of code counters for a number of years. Such code counters can be very handy when using lines of code as a size measure. I know, many object to using lines of code, but when used correctly they can work well. We see users who have just as much success with lines of code as they do with function points, use cases, etc.
Even if you are a functional size user, knowing the SLOC for legacy can be useful, rather than counting the function points, etc. Here is the announcement from USC:
We are pleased to announce that a new version of the Unified CodeCount (UCC) tool is now available to the public at http://sunset.usc.edu/research/CODECOUNT/. This Release 2010.07 supports new programming languages (e.g., Fortran, Python, ColdFusion, Bash and C-Shell script) and the CSV output format among other enhancements and bug fixes. Please refer to the release notes document for further details at http://sunset.usc.edu/research/CODECOUNT/download/2010/UCC_Release_Notes_v.2010.07.pdf
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Project Prediction Infographic
