- 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.
[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft