Frank Uncovers Excellence in Leadership

© Copyright Frank D. Kanu 2000-2008

Location: Nationwide
Industry: Software

Scenario:

A piece of software with more than 500 installations and 25 users on average was due for a new version release in June. But, by October, nothing was ready to roll out. The software, when tried with different code bases worked with limited functionality. As a result, the majority of the software’s programmers were busy fixing bugs.

Problem:

The software had next to no documentation and the team had spent more than the amount they had previously estimated. Clients were getting impatient, sales were on the decline, and investors were considering pulling out of the project altogether.

Solution:

The existing version was locked down. Then, all of the code bases were merged into one and documentation was created. We involved the clients in the testing, which got them interested and using the system again. We had every programmer report on their progress daily.

Result:

Within two weeks, a deadline was set for the first beta release of the software. The company delivered on time and got the approval of upper management to continue development.

Tags:

beta release  bugs  case study  decline  functionality  impatient  installations  investors  new version  programmer  programmers  software scenario  upper management  version release
 Technorati (All Links are external): beta release  bugs  case study  decline  functionality  impatient  installations  investors  new version  programmer  programmers  software scenario  upper management  version release  business  case studies  it