What Documentation?The client had developed one of its product with a minimum of staff. The bad news is that there was no coherent documentation for the product. Not surprisingly, new releases were always late and buggy because nobody really knew how to test the product thoroughly. New staff struggled to add new features and fix bugs without causing regression problems. A few weeks after taking over the product we made it an integral part of our work to document the system. That has helped new staff to navigate the code, has accelerated development and it has allowed us to create a thorough test suite. New releases are now more predictable and of higher quality. Technologies
« Robot Watching « » Agility » |
home » success stories » what doc?
Site Menu
