Software Engineering with Microsoft Visual Studio Team System by Juan J. Perez, Sam Guckenheimer | | NOOK Book (eBook) | Barnes & Noble
Software Engineering with Microsoft Visual Studio Team System

Software Engineering with Microsoft Visual Studio Team System

4.0 1
by Juan J. Perez, Sam Guckenheimer
     
 

View All Available Formats & Editions

Software Engineering with Microsoft Visual Studio Team System is written for any software team that is considering running a software project using Visual Studio Team System (VSTS), or evaluating modern software development practices for its use.

 

It is about the value-up paradigm of software development, which forms the basis

Overview

Software Engineering with Microsoft Visual Studio Team System is written for any software team that is considering running a software project using Visual Studio Team System (VSTS), or evaluating modern software development practices for its use.

 

It is about the value-up paradigm of software development, which forms the basis of VSTS: 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.

 

Sam Guckenheimer has been the chief customer advocate for VSTS, responsible for its end-to-end external design. He has written this book as 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.

 

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.

Product Details

ISBN-13:
9780132702140
Publisher:
Pearson Education
Publication date:
05/09/2006
Sold by:
Barnes & Noble
Format:
NOOK Book
Pages:
304
File size:
6 MB

Meet the Author

Sam Guckenheimer has 25 years of experience as architect, developer, tester, product manager, project manager, and general manager in the software industry in the U.S. and Europe. Currently, Sam is the group product planner for Microsoft Visual Studio Team System. In this capacity, he acts as chief customer advocate, responsible for the end-to-end external design of the next releases of these products. Prior to joining Microsoft in 2003, Sam was director of Product Line Strategy at Rational Software Corporation, now the Rational Division of IBM. He holds five patents on software lifecycle tools. A frequent speaker at industry conferences, Sam is a Phi Beta Kappa graduate of Harvard University. Sam lives in the Puget Sound area with his wife and three of his four children.

Customer Reviews

Average Review:

Write a Review

and post it to your social network

     

Most Helpful Customer Reviews

See all customer reviews >

Software Engineering with Microsoft Visual Studio Team System (Microsoft .NET Development Series) 4 out of 5 based on 0 ratings. 1 reviews.
Guest More than 1 year ago
The text appears to be at least as much about Microsoft Solutions Framework (MSF) than about Visual Studio Team System. Granted, there are numerous screen captures about the latter, with accompanying notes on their significance. But you can learn about MSF. Wherein Microsoft has positioned this to appeal to proponents of either Agile or CMMI. For readers possibly unfamiliar with both, Guckenheimer gives an explanation of the ideas behind MSF. Why it is often useful to do iterative development in a software project. And the advantages of this over a traditional waterfall methodology, which has been shown to be often too coarse grained and unrealistic. Plus, the idea of unit testing and verification testing is emphasised. These tests can be implemented independent of whether you also do any type of iterative development. They have standalone merit. Though their utility is enhanced when combined with rapid iteration. Even if you decide that VSTS is not for your group, the general approach of MSF may still be beneficial, especially if you are a Microsoft house.