Review Processes that Work
We had a client who decided to redevelop and update their main system. The design was being done on a module by module basis with all of them being linked through a common interface. With other business commitments and development conflicts the project was not moving quickly.
However, when we had completed the design of a module (not the coding), we wrote some Test objectives or conditions so we knew the scope of the testing. We sent the Test Objectives for review by the business and development expecting a quick turnaround with few comments.
Instead, we received a surprise from the business. They did not dispute our Objectives and agreed that they represented the design elements and would test them thoroughly. However, the design did not suit their business requirements and needed rework prior to any development.
We saved $1000 of development and testing cost by identifying this early and before a lot of work had been completed.
Review processes do work!