Readers will learn what they need to know to get started with VSTS, including:
The role of the value-up paradigm (versus work-down) in the software development lifecycle, and the meanings and importance of “flow”
The use of MSF for Agile Software Development and MSF for CMMI Process Improvement
Work items for planning and managing backlog in VSTS
Multidimensional, daily metrics to maintain project flow and enable estimation
Creating requirements using personas and scenarios
Project management with iterations, trustworthy transparency, and friction-free metrics
Architectural design using a value-up view, service-oriented architecture, constraints, and qualities of service
Development with unit tests, code coverage, profiling, and build automation
Testing for customer value with scenarios, qualities of service, configurations, data, exploration, and metrics
Effective bug reporting and bug assessment
Troubleshooting a project: recognizing and correcting common pitfalls and antipatterns
This is a book that any team using or considering VSTS should read.
Sam Guckenheimer describes key concepts from his latest book, Software Engineering with Microsoft Visual Studio Team System.