Home > Store

Agile Software Engineering with Visual Studio: From Concept to Continuous Feedback, 2nd Edition

Register your product to gain access to bonus material or receive a coupon.

Agile Software Engineering with Visual Studio: From Concept to Continuous Feedback, 2nd Edition

eBook (Watermarked)

  • Sorry, this book is no longer in print.
  • Includes EPUB and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    Adobe Reader PDF The popular standard, used most often with the free Acrobat® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

Not for Sale

Description

  • Copyright 2012
  • Dimensions: 7" x 9-1/8"
  • Edition: 2nd
  • eBook (Watermarked)
  • ISBN-10: 0-13-293084-6
  • ISBN-13: 978-0-13-293084-0

Using agile methods and the tools of Visual Studio 2010, development teams can deliver higher-value software faster, systematically eliminate waste, and increase transparency throughout the entire development lifecycle. Now, Microsoft Visual Studio product owner Sam Guckenheimer and leading Visual Studio implementation consultant Neno Loje show how to make the most of Microsoft’s new Visual Studio 2010 Application Lifecycle Management (ALM) tools in your environment.

This book is the definitive guide to the application of agile development with Scrum and modern software engineering practices using Visual Studio 2010. You’ll learn how to use Visual Studio 2010 to empower and engage multidisciplinary, self-managing teams and provide the transparency they need to maximize productivity. Along the way, Guckenheimer and Loje help you overcome every major impediment that leads to stakeholder dissatisfaction—from mismatched schedules to poor quality, blocked builds to irreproducible bugs, and technology “silos” to geographic “silos.”

Coverage includes
• Accelerating the “flow of value” to customers in any software project, no matter how large or complex
• Empowering high-performance software teams and removing overhead in software delivery
• Automating “burndowns” and using dashboards to gain a real-time, multidimensional view of quality and progress
• Using Visual Studio 2010 to reduce or eliminate “no repro” bugs
• Automating deployment and virtualizing test labs to make continuous builds deployable
• Using Test Impact Analysis to quickly choose the right tests based on recent code changes
• Working effectively with sources, branches, and backlogs across distributed teams
• Sharing code, build automation, test, project and other data across .NET and Java teams
• Uncovering hidden architectural patterns in legacy software, so you can refactor changes more confidently
• Scaling Scrum to large, distributed organizations

Whatever your discipline, this book will help you use Visual Studio 2010 to focus on what really matters: building software that delivers exceptional value sooner and keeps customers happy far into the future.

Foreword by Ken Schwaber

It is my honor to write a foreword for Sam’s book,  Agile Software Delivery with Visual Studio. Sam is both a practitioner of software development, as well as a scholar. I have worked with Sam for the last two years to merge Scrum with modern engineering practices and an excellent toolset, Microsoft’s VS 2010. We are both indebted to Aaron Bjork of Microsoft, who developed the Scrum template that instantiates Scrum in VS 2010 through the Scrum Template.

I do not want Scrum to be prescriptive. I left many holes, such as what as the syntax and organization of the Product Backlog, the engineering practices that turned Product Backlog items into a potentially shippable increment, and the magic that would create self-organizing teams. Sam has superbly described one way of filling in these holes in his book. He describes the techniques and tooling, as well as the rationale of the approach that he prescribes. He does this in detail, with scope and humor. Since I have worked with Microsoft since 2004 and Sam since 2009 on these practices and tooling, I am delighted. Our first launch was a course, the Professional Scrum Developer .NET course, that taught developers how to use solid increments using modern engineering practices on VS 2010 — working in self-organizing, cross-functional teams. Sam’s book is the bible to this course and more, laying it all out in detail and philosophy. If you are on a Scrum Team building software with .NET technologies, this is the book for you. If you are using Java, this book is compelling enough to read anyway, and maybe worth switching to .NET.

When we devised and signed the Agile Manifesto in 2001, our first value was “Individuals and interactions over processes and tools.”  Well, we have the processes and tools nailed for the Microsoft environment. In Sam’s book, we have something developers, who are also people, can use to understand the approach and value of the processes and tools. Now the really hard work, people. After twenty years of being treated as resources, becoming accountable, creative, responsible people is hard.  Our first challenge will be the people who manage the developers. They could use the metrics from the VS 2010 tooling to micro-manage the processes and developers, squeezing the last bit of creativity out and leaving Agility flat. Or, they could use the metrics from the tools to understand the challenges facing the developers. They could then coach and lead them to a better, more creative and productive place. This is the challenge of any tool. It may be excellent, but how it is used will determine its success.

Thanks for the book, Sam.

Praise for Agile Software Engineering with Visual Studio

“Agile dominates projects increasingly from IT to product and business development, and Sam Guckenheimer and Neno Loje provide pragmatic context for users seeking clarity and specifics with this book. Their knowledge of past history and current practice, combined with acuity and details about Visual Studio’s agile capabilities, enable a precise path to execution. Yet their voice and advice remain non-dogmatic and wise. Their examples are clear and relevant, enabling a valuable perspective to those seeking a broad and deep historical background along with a definitive understanding of the way in which Visual Studio can incorporate agile approaches.”
—Melinda Ballou, Program Director, Application Lifecycle Management and Executive Strategies Service, International Data Corporation (IDC)

“Sam Guckenheimer and Neno Loje have forgotten more about software development processes than most development ‘gurus’ ever knew, and that’s a good thing! In Agile Software Engineering with Visual Studio, Sam and Neno distill the essence of years of hard-won experience and hundreds of pages of process theory into what really matters—the techniques that high performance software teams use to get stuff done. By combining these critical techniques with examples of how they work in Visual Studio, they created a de-facto user guide that no Visual Studio developer should be without.”
—Jeffrey Hammond, Principal Analyst, Forrester Research

“If you employ Microsoft’s Team Foundation Server and are considering Agile projects, this text will give you a sound foundation of the principles behind its agile template and the choices you will need to make. The insights from Microsoft’s own experience in adopting agile help illustrate challenges with scale and the issues beyond pure functionality that a team needs to deal with. This book pulls together into one location a wide set of knowledge and practices to create a solid foundation to guide the decisions and effective transition, and will be a valuable addition to any team manager’s bookshelf.”
—Thomas Murphy, Research Director, Gartner

“This book presents software practices you should want to implement on your team and the tools available to do so. It paints a picture of how first class teams can work, and in my opinion, is a must read for anyone involved in software development. It will be mandatory reading for all our consultants.”
—Claude Remillard, President, InCycle

“This book is the perfect tool for teams and organizations implementing agile practices using Microsoft’s Application Lifecycle Management platform. It proves disciplined engineering and agility are not at odds; each needs the other to be truly effective.”
—David Starr, Scrum.org

“Sam Guckenheimer and Neno Loje have written a very practical book on how Agile teams can optimize their practices with Visual Studio. It describes not only how Agile and Visual Studio work, but also the motivation and context for many of the functions provided in the platform. If you are using Agile and Visual Studio, this book should be a required read for everyone on the team. If you are not using Agile or Visual Studio, then reading this book will describe a place that perhaps you want to get to with your process and tools.”
—Dave West, Analyst, Forrester Research

“Sam Guckenheimer and Neno Loje are leading authorities on agile methods and Visual Studio. The book you are holding in your hand is the authoritative way to bring these two technologies together. If you are a Visual Studio user doing agile, this book is a must read.”
—Dr. James A. Whittaker, Software Engineering Director Google

“Agile development practices are a core part of modern software development. Drawing from our own lessons in adopting agile practices at Microsoft, Sam Guckenheimer and Neno Loje not only outline the benefits, but also deliver a hands-on, practical guide to implementing those practices in teams of any size. This book will help your team get up and running in no time!”
—Jason Zander, Corporate Vice President, Microsoft Corporation

Sample Content

Table of Contents

Foreword     xvii
Preface     xix
Acknowledgements      xxvi
About the Authors     xxvii

Chapter 1: The Agile Consensus      1
The Origins of Agile     1
Agile Emerged to Handle Complexity     2
Empirical Process Models      4
A New Consensus     4
Scrum     6
An Example     12
Summary     15
End Notes     16

Chapter 2: Scrum, Agile Practices, and Visual Studio     19
Visual Studio and Process Enactment      20
Process Templates     21
Process Cycles and TFS     23
Inspect and Adapt     36
Task Boards     36
Kanban     38
Fit the Process to the Project     39
Summary     42
End Notes     43

Chapter 3: Product Ownership     45
What Is Product Ownership?     46
Scrum Product Ownership     50
Release Planning     51
Qualities of Service     63
How Many Levels of Requirements     67
Summary     70
End Notes     70

Chapter 4: Running the Sprint     73
Empirical over Defined Process Control     75
Scrum Mastery     76
Use Descriptive Rather Than Prescriptive Metrics     81
Answering Everyday Questions with Dashboards     86
Choosing and Customizing Dashboards     94
Using Microsoft Outlook to Manage the Sprint      95
Summary     96
End Notes     96

Chapter 5: Architecture     99
Architecture in the Agile Consensus      100
Exploring Existing Architectures     103
Summary     121
End Notes     123

Chapter 6: Development     125
Development in the Agile Consensus     126
The Sprint Cycle     127
Keeping the Code Base Clean     128
Detecting Programming Errors Early     135
Catching Side Effects     152
Preventing Version Skew     160
Making Work Transparent     168
Summary     169
End Notes     171

Chapter 7: Build and Lab     173
Cycle Time     174
Defining Done     175
Continuous Integration     177
Automating the Build     179
Elimination of Waste     196
Summary     201
End Notes     202

Chapter 8: Test     203
Testing in the Agile Consensus     204
Testing Product Backlog Items     207
Actionable Test Results and Bug Reports     212
Handling Bugs     218
Which Tests Should Be Automated?     219
Automating Scenario Tests     220
Load Tests, as Part of the Sprint     225
Production-Realistic Test Environments      230
Risk-Based Testing     232
Summary     235
End Notes     236

Chapter 9: Lessons Learned at Microsoft Developer Division     239
Scale     240
Business Background     241
Improvements After 2005     245
Results     254
Law of Unintended Consequences     255
What’s Next?     259
End Notes     259

Chapter 10: Continuous Feedback     261
Agile Consensus in Action     262
The Next Version     263
Product Ownership and Stakeholder Engagement     264
Staying in the Groove     270
Testing to Create Value     275
TFS in the Cloud     275
Conclusion     276
End Notes     279

Index     281

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020