Web-articles

Keep it Simple - A Cliché, a Philosophy

This is a topic for which one could write volumes.  However, that would contradict the entire point of the article.  In order to “keep it simple” this article must deliver its message with relatively few words.

Some of the most spectacular failures (software implementations) have been the result of over engineering.  While no one begins a project with the intent of over engineering, it isn’t something that just happens.  It results from:

Lack of leadership during the design phase

Typically the second phase (after the “Administrative Phase”) of an initiative is the “Design Phase”.  It is during this time that research and analysis are performed, decisions made, and the design finalized.  Strong leadership is required to keep the team on task and to resolve intramural squabbles.  We’ve all heard the story of the camel and committees.

Scope Creep – Changing the design during the development phase

It is not only likely, but inevitable, that the requirements will change after the specifications have developed if the right people are not involved during the design phase.  Such changes will also occur if the team leaders do not properly facilitate the design meetings.  These after the fact changes cause the developers to layer the new requirements over the original, already developed, programming. 

Not enough attention given to managing expectations

It is possible for a technically perfect project to be considered an absolute failure because it didn’t meet the expectations of senior management.  While the new implementation may perform to the design specifications developed by the project team, it may not meet the metrics established by management.  For example, it may have taken too long or cost too much.