Tom has posted 1 posts at DZone. View Full User Profile

Content Management Software Blunder

  • submit to reddit

I read a short "Tech Buzz" story in the 5/18/2008 issue of InformationWeekly. The short story centered around a Content Management Software development company (the name was not revealed). The story stated that the un-named software company was on it's way out of business due to 5 strong (yet correctable) blunders.

  1.  New software versions not thoroughly tested before releasing to customers. When bugs were reported on the company's tech blog, the entries were erased.
  2. Very little interaction between customer tech support and the engineering team.
  3. Documentation obviously out of date.
  4. Software upgrades causes major issues, including corrupting the intalled software.
  5. Turning off non-required software modules caused software to act unstable.

Based upon my knowledge of IT and software, I have seen and been a part of this type of customer abuse. I feel blessed to make a nice living from what is really my hobby. The main causes of the stated issues that I first think of are:

  • Non-flexible release date.
  • QA time partially eaten by overruns by the development team.
  • Too many managers resulting in poor communication.
  • The QA team is in India and the development team is in the USA - the teams are not on the same clock schedule.

I am interested to hear what others have experienced as causes to the major 5 issues mentioned.

(InformationWeek story written by George Dearing)

Published at DZone with permission of its author, Tom Pridham.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Nishant Kumar replied on Fri, 2008/05/23 - 6:45am

Two more points.

1. The QA team in not the gatekeeper of the product. ie they have not been given the right to halt the release if it is not of a certain quality.

2. This un-named company is playing a catch-up game with a competitor. The competitor has released a new feature (fringe feature) which people are not using much but it is still a new feature. The quality of the user required features suffer because of the time devoted on salesman required feature.

Geertjan Wielenga replied on Fri, 2008/05/23 - 7:18am

Basically, the fundamental problem described here is the reason for "agile" development methodologies.

Tom Pridham replied on Fri, 2008/05/23 - 8:51pm in response to: Nishant Kumar


Sounds like you may work at the company mentioned in the article? If so, I mean no harm, I just wanted to make the point that a huge portion of software shops make the same mistakes.


Kind Regards,

Tom Pridham

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.