Monday 11 December 2006

How not to release software...

1. Do a presentation of the new product to a client on the morning it is released... without informing the development team.
2. Release when there has been no set test plan put into operation.
3. Make functionality changes in the days and weeks before release.
4. doc·u·men·ta·tion /ˌdɒkyəmɛnˈteɪʃən, -mən-/ Pronunciation Key [dok-yuh-men-tey-shuhn, -muhn-]

This is going to be a long afternoon...

No comments: