Case Study 3
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.
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.
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.
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.
This Genius One Article is published here for the purpose of helping to improve your personal and organizational performances; designed to provide
accurate and authoritative information in regard to the subject matter covered. If legal advice or other expert assistance is
required, the services of a competent professional should be sought.
Please contact us directly if you need a word or pdf version of this article.