crazed monkey

Ian Stevens' weblog

RSS

Toronto Police eCOPS a lesson in how not to manage a software project

The Toronto auditor general’s report on the failed eCOPS project reads like a list of what not to do with a large software project. To start, the project was handled in-house with no regard for the expertise of existing employees. Probably because of their lack of experience, requirements and use-cases were “inadequate, incomplete, or in some cases, non-existent.” Most importantly, development costs were not tracked and quickly got out of hand.

Too often it would seem that project managers and developers forget the old maxim that “time is money.” Projects are often started without a proper plan including a time estimate, cost assessment and an analysis of whether the benefits outweigh those costs. This mismanagement of time results in changes of scope over the course of the project with creeping time overruns as “unforeseen” difficulties arise and features are tacked on.

Sadly, the Toronto Police eCOPS failure isn’t an anomaly in the software industry. The only news here is that it has been a colossal waste of public money.

This entry was posted on Tuesday, June 14th, 2005 at 11:37 pm and is filed under computers, programming. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “Toronto Police eCOPS a lesson in how not to manage a software project”

  1. Mervyn Fessman Says:

    September 26th, 2007 at 6:13 am

    Sounds like a classic!

Leave a Reply