Reverse development
For my next project, I’m going to try the following software development method:
This draws upon elements of Test Driven Development and Spiral Model but tries to be lighter-weight. Requirements gathering is eschewed in favour of domain expertise. The screencast building and documentation process is used as a springboard for mockups and graphic designs, and to force user interaction think-through prior to coding.
Any thoughts?
