- Develop Iteratively - to reduce risk and improve quality
- Manage Requirements - because software requirements usually evolve rather than materialize
- Use Component Architectures - because we expect software to be flexible over time
- Model Visually - so that business people, and software people can develop a common understanding of the system requirements and design
- Continuously Verify Quality - because mistakes caught late in the process can cost 200 times more
- Manage Change - because change is an unavoidable fact of software development projects.
Thanks for attending my presentation. Resources I referenced: .Net 3.5 Enhancements Training Kit Download Overview of ASP.NET 3.5 Extensions Preview ASP.NET 3.5 Extensions Preview (unrelated) Central Ohio Application Lifecycle Management Group: COALMG Update 4/22/2008 : Props to Dan Hounshell for finding this CODODN video . I'm in there 2-3 times. Nice!
Comments