Introduction | Frequency of Build | Implementing Weekly Build
Broken Builds | Get the Customer to Review the Product Early
Conclusion | Footnote: Whence the Term "Smoke Test"?

Conclusion

By implementing a weekly build and smoke test, in addition to using other tools, we were able to deliver the project with a productivity improvement of as much as 50%. The project was also delivered with no overrun in either effort or schedule. An outline of the weekly build and smoke test is shown in Figure 1.

Figure 1: Weekly Build and Smoke Test
Figure 1: Weekly Build and Smoke Test

A program or project manager needs to find novel and innovative ways to monitor the project and the Weekly Build and Smoke Test technique greatly assists in this regard. It helps the project manager to verify the progress quite early during the software development life cycle.

Get the Customer to Review the Product Early  Get the Customer to Review the Product Early
Home | Issacons | PM Glossary | Papers & Books | Max's Musings
Guest Articles | Contact Info | Search My Site | Site Map | Top of Page