- Paperback: 304 pages
- Publisher: Addison-Wesley Professional; 1 edition (May 19, 2006)
- Language: English
- ISBN-10: 0321278720
- ISBN-13: 978-0321278722
- Product Dimensions: 7.1 x 0.7 x 9.1 inches
- Shipping Weight: 1.3 pounds (View shipping rates and policies)
- Average Customer Review: 7 customer reviews
- Amazon Best Sellers Rank: #4,568,795 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Software Engineering with Microsoft Visual Studio Team System 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
There is a newer edition of this item:
From the Back Cover
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.
“This is first and foremost a book about software engineering. In discussing flash points such as planning, documentation, governance, auditability, and organization, Sam presents the case for both agile and more formal practices, as well as describing the optimal conditions for each. Even though the material is presented in the context of VSTS, the guidance is universal.”
–Dr. Bill Curtis
chief process officer, Borland Software Corporation
“Sam Guckenheimer ushers in the era of trustworthy transparency that will revolutionize the way we manage software development projects.”
–David J. Anderson
author of Agile Management for Software Engineering
“This book is an eye opener: a door to a new era of software engineering.”
–Francis T. Delgado
senior program manager, Avanade
About 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.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
This book's intended goal is to be a solid, project manager-oriented, look at how to use VSTS to it's maximum advantage; and it attains that goal: you'll learn VSTS's tools and capabilities; and how to employ them to manage your software development efforts; but it is not intended to be an administrators guide on how to install, configure and debug the VSTS server or development environment(s).
To me, a major benefit of this book is that it is a great resource for selling your boss or upper management on the idea of initiating a pilot or "proof of concept" VSTS project - they will love the charts/graphs and reports that are shown in this book, and your "sales pitch" will benefit from the clear descriptions the author supplies as to how to read these charts or reports, and how to use them to keep yourself (and your superiors or clients) informed as to a project's status, and what bottlenecks or issues need to be addressed as the project progresses.
The text is relatively short - only 247 pages, which makes it a good weekend read - you aren't flooded with finicky details.
I also appreciated the "expected criticisms" section at the very end of the book: The author makes it clear that VSTS (at the time this book was written) is a brand new product, and will need a couple of releases to mature and reach its full potential. He also acknowledges that it will take time for a body of "field level" knowledge to accumulate as to how best to take advantage of innovations and technologies that are embodied in VSTS.
That awareness on the author's part, and the focus on why and how VSTS is designed to help you as a project manager, are what really help this book succeed: it will help you and your team be a more productive resource for your organization: building and delivering high quality software products on time and within budget using VSTS.
All in all, an excellent introduction to Project Management using Visual Studio Team System, and a book that will help you fully appreciate and exploit the capabilities and benefits of VSTS. 5 Stars!
The beginning discussion includes an overview of traditional project management techniques, such as gannt charts, earned-value-analysis, and task breakdowns. The author then explains how software products are intangible and unique, and goes on to cover agile methods. I was particularly impressed with his explanation of the 'value up' technique, which pulls together all of the agile concepts like measured running tested features and quick software releases.
Perhaps the best explanations are in the area of software metrics; how to measure bug count, code coverage, and work products completed vs. the product backlog. The view of metrics proposed in the book is surprisingly mature; the book discusses tradeoffs of various metrics and the concept of dysfunction. I was particularly surprised to find myself taking mental notes as I read the book, tracking all the new ideas to try in the office.
Of course, the title is "Software Engineering With Microsoft Visual Studio Team System", and all of the graphs and charts are generated using Microsoft Software. The book is not tutorial in nature; it concentrates on the essence of development, and not how to click what wizard to generate what graph. Instead, the examples demonstrate how the metrics are integrated within the Microsoft tool, and how much easier it would be to gather metrics within the team system. (Given the title, that has to be expected.)
Overall, I would recommend this for new college graduates without a background in software engineering, 'traditional' software engineers seeking an introduction to agile methods, or Quality Analysts seeking an introduction to Agile Metrics. Surprisingly enough, Team System is not a requisite; but if you are developing in MSVS Team System, I would upgrade it the review to 'highly recommended', or 4.5 stars.