This blog is a companion to the book, Software Engineering with Microsoft Visual Studio Team System. This book is written for a software team that is considering running a software project using Visual Studio Team System (VSTS). This book is about the why, not the how. What are the guiding ideas behind VSTS? Why are certain ideas presented in certain ways? For example, why are so many things called work items? What does the metrics warehouse measure? Why would you use those particular reports?
In the blog, I plan to develop the ideas further and talk about their everyday application.