Quality Programming
Frequency of IterationsIterations should be frequent without churning. Business rules change twice a year, prioritization changes quarterly and deliveries 6-10 times per year.
Explicit Design CriteriaProgrammers need guidelines to help make difficult tradeoffs while programming. The criterion should be reliability first, then compatibility, performance, and finally features. With this message from management, programmers can be expected to produce a consistent and dependable style of program Frequent User TestingThe biggest danger is to deliver a working system that doesn't do what the client needs or wants. Even when code does what the user wants, it seldom meets expectations. To minimize this risk, pre-releases of revised software to selected clients early will identify issues and get customer acceptance. |
