Possible Chapter Titles
- Speed Kills
- Requirements are Requirements
- Don't touch that stove (Design rules)
- Its Just Data
- Its Just a Website
- 1 great coder > 5 average coders
- Only You can Prevent Forest Fires (cfg mgt, src cntrl, build and deploy processes)
- Deja Vu (don't solve problems twice - use open source, buy, or re-use internal solutions)
- Divide and conquer (modularize components to improve speed of development and supportablity)
- Nothing is done until its documented
- Requirements Document (Provide template)
- Project Management (Must be web-based, collaborative UI - Provide template)
- Configuration Management (Structure of project folders, build and deploy plan. Provide an example in .Net an Java)
- Mock ups (Web UI mock-ups for customer sign-off. Reduce any potential confusion.)
- Proof of Concepts (Do the hard stuff first)
- Iterative Releases and Demos
- Environments
- Testing
- Help (Build your technical documentation into your software via html help modules)
- Production Migration Best Practices (Release steps in worksheet. Post production testing. Sign-offs. Support model)
- Support models.
