Skip to main content

More Mistakes To Do...

In my article ‘Plan to do New Mistakes’ published here, in this blog in Feb. 2008, I had listed ‘Classic Mistakes’ from Steve McConnell’s book ‘Rapid Development: Taming Wild Software Schedules’ and mentioned that a Project will definitely be a success, if the Project Manager ensures that the team doesn’t do the ‘Classic Mistakes’. Towards the end of the article, I had also mentioned that by doing new mistakes, a Project Manager can also contribute to the history of software engineering, in jest.

Well, Steve McConnell and his team have actually revised the classic Mistakes and updated the list. :)

The following Classic Mistakes were added.

  • Confusing Estimates and Targets
  • Excessive Multi Tasking
  • Assuming Global development has a negligible impact on the total effort.
  • Unclear Project Vision
  • Trusting the map more than the territory
  • Outsourcing to reduce the cost
  • Letting a team go dark

The addition had produced a total list of 42 classic Mistakes.

I have listed the Top 10 Classic Mistakes here from the updated list. These are also called the ‘Most Damaging Classic Mistakes’.

  1. Unrealistic Expectations
  2. Overly Optimistic schedules
  3. Short Changed Quality Assurance
  4. Wishful Thinking
  5. Confusing Estimates with Targets
  6. Excessive Multitasking
  7. Feature Creep
  8. Noisy Crowded Offices
  9. Abandoning Planning Under Pressure
  10. Insufficient Risk Management.

It may be funny, but nothing related to ‘Technology’ figures in the top 10 list. I believe it sends the message to people that Good Project Management Practices along with good technical practices alone will lead a Project to success. The relationship between ‘Technology and Project Management’is an AND condition not an OR condition.

If you want to know all the 42 classic mistakes, their definitions, how these mistakes rank and the methodology used , please refer to the paper here. ( note registration is needed).


Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …