Brice Vuagniaux

Last week, our development team was supposed to launch a new version of our application. As usual, right before finishing the application we discover that one or two problems had to be corrected. We were then faced with the following options: We correct the problems and test to verify that everything is working. Usually this means the project will be delayed (it wasn't exactly ahead of schedule to begin with...) and that numerous time-consuming tests will have to be done. We correct the problems without testing the application. After all, we've done very complete tests and since the project is late already ... We wait for the new version to modify the changes ("it's too bad but we saw these problems too late and didn't want to delay the project any longer..."). Lately, we've been exploring a new method of implementing changes more efficiently using an impact analysi... (more)