TFS, ALM, what’s in a name?

In response to my posts on Peer Reviews, Unit Testing & TDD, and Common Code Layout, someone noticed that all these posts were part of my Team Foundation Server Development Practices series, but not every post actually mentioned TFS. Obviously, he was right. The reason for using the TFS prefix is that our company is heavily using TFS as a platform for supporting Application Lifecycle Management. Most of the practices I talk about include a lot of practical advice on how to get the most out of the TFS product suite. Nevertheless, I’ve renamed the series to ALM Practices to better emphasis the real purpose of it. So what’s planned?

• Code Analysis & Coding Standards
• Refactoring
• Automatic Builds & Continuous Integration
• Checklists
• Work Item Tracking & Tracibility
• Architectural & Technological Audits
• Pair Programming