Software Engineering with Microsoft Visual Studio Team System is written for a software team that is considering running a software project using Visual Studio Team System (VSTS). It is about the "why" of its guiding ideas, why they are presented in certain ways, and how they fit into the process of managing the software lifecycle. This book is the next best thing to having an onsite coach who can lead the team through a consistent set of processes. It is a framework for thinking about software projects in a way that can be directly tooled by VSTS. It presents essential theory and practical examples to describe a realistic process for IT projects. This is a book that any team using or considering VSTS should read.
Summary: 1-star if you are a developer/software engineer, 5-stars if you need a high-level introduction to VSTS.
This book reads like a "200/300 level" college text on software engineering filtered through the lens of the feature set of VSTS. It's great as a marketing tool, or if you need to understand the broad brush strokes of what VSTS can do for your development environment. That said, if you willingly paid the cover price for this book, one would assume that you already see the business value of VSTS (I received my copy free from a Microsoft rep).
Some program managers, business analysts, and technical managers needing an introduction to the capabilities of VSTS may find value in this book. Also, those seeking information to craft a sales pitch to management on why VSTS is of value may also like this book. However, most people (developers in particular) should steer clear of this work.
This was a good overview of integrated SDLC best practices. It was a pretty quick read and raised ideas/concepts that make me interested in tracking down other, more in-depth books on various specific SD topics.