Visual Studio Team Foundation Server 2012: Adopting Agile Software Practices: From Backlog to Continuous Feedback [NOOK Book]

Overview

Use Visual Studio® Team Foundation Server 2012 and Agile Methods to Deliver Higher Value Software Faster

This is the definitive guide to applying agile development and modern software engineering practices with Visual Studio Team Foundation Server 2012—Microsoft’s complementary Application Lifecycle Management (ALM) platform. Written by the Microsoft Visual Studio product owner and a long-time Team Foundation Server implementation specialist, it focuses on solving real ...

See more details below
Visual Studio Team Foundation Server 2012: Adopting Agile Software Practices: From Backlog to Continuous Feedback

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK 7.0
  • Samsung Galaxy Tab 4 NOOK 10.1
  • NOOK HD Tablet
  • NOOK HD+ Tablet
  • NOOK eReaders
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac

Want a NOOK? Explore Now

NOOK Book (eBook)
$28.79
BN.com price
(Save 20%)$35.99 List Price

Overview

Use Visual Studio® Team Foundation Server 2012 and Agile Methods to Deliver Higher Value Software Faster

This is the definitive guide to applying agile development and modern software engineering practices with Visual Studio Team Foundation Server 2012—Microsoft’s complementary Application Lifecycle Management (ALM) platform. Written by the Microsoft Visual Studio product owner and a long-time Team Foundation Server implementation specialist, it focuses on solving real development challenges, systematically eliminating waste, improving transparency, and delivering better software more quickly and painlessly.

Coverage includes

• Accelerating the “flow of value” to customers, with a transparent backlog, PowerPoint Storyboarding, VS 2012 feedback requests, and a “usability lab” right into your customers’ hands

• Driving quality upstream to uncover hidden architectural patterns, ensure cleaner code, fix multiple recurring “cloned” bugs at once, ensure the definition of done with continuous integration and deployment in a reliable build process

• Eliminating “no repro” bugs with VS 2012’s six powerful mechanisms for more accurate fault identification and use of virtualized test environments

• Using Scrum or other Agile methods with Process Templates effectively across distributed teams in large organization by automating burndowns and dashboards to identify “early warning signals” of emerging problems with quality or maintainability

• Staying in the groove by storing the state of your work and environment with shelvesets, to let you handle interruptions smoothly

• Leveraging VS 2012’s new support for multiple Microsoft and open source unit testing frameworks in your IDE and continuous integration pipeline

• Performing exploratory testing to uncover bugs in surprising places and testing immersive Windows 8 apps

• Rapidly improving team development and collaboration with the hosted Team Foundation Service

Whatever your development role, this book will help you apply modern software development practices using Visual Studio Team Foundation Server 2012 to focus on what really matters: building soft­ware that begins delivering exceptional value sooner and keeps delighting customers far into the future.

Read More Show Less

Product Details

  • ISBN-13: 9780133119183
  • Publisher: Pearson Education
  • Publication date: 9/25/2012
  • Series: Microsoft Windows Development Series
  • Sold by: Barnes & Noble
  • Format: eBook
  • Edition number: 3
  • Pages: 320
  • Sales rank: 730,025
  • File size: 41 MB
  • Note: This product may take a few minutes to download.

Meet the Author

Sam Guckenheimer, Product Owner for the Microsoft Visual Studio product line strategy, acts as chief customer advocate, responsible for end-to-end external design of new Visual Studio releases. He has 30 years’ experience as software architect, developer, tester, product manager, project manager, and executive. Before joining Microsoft, he was Director of Product Line Strategy at Rational Software Corporation, now the Rational Division of IBM. He holds five patents on software lifecycle tools, is a frequent conference speaker, and Phi Beta Kappa graduate of Harvard. Neno Loje has been an independent Application Lifecycle Management (ALM) consultant and Visual Studio Team Foundation Server (TFS) specialist for seven years, helping many companies establish team environments and development processes with Visual Studio.

Read More Show Less

Table of Contents

Forewords xii

Preface xvi

Acknowledgments xxiii

About the Authors xxiv

1 The Agile Consensus 1

The Origins of Agile 2

Agile Emerged to Handle Complexity 2

Empirical Process Models 4

A New Consensus 5

Scrum 6

An Example 12

Self-Managing Teams 14

Summary 15

Endnotes 16

2 Scrum, Agile Practices, and Visual Studio 19

Visual Studio and Process Enactment 20

Process Templates 21

Process Cycles and TFS 24

Inspect and Adapt 37

Task Boards 37

Kanban 38

Fit the Process to the Project 39

Summary 42

Endnotes 43

3 Product Ownership 45

What Is Product Ownership? 46

Scrum Product Ownership 50

Release Planning 51

Qualities of Service 69

How Many Levels of Requirements 73

Summary 75

Endnotes 75

4 Running the Sprint 77

Empirical over Defined Process Control 78

Scrum Mastery 80

Use Descriptive Rather Than Prescriptive Metrics 86

Answering Everyday Questions with Dashboards 91

Choosing and Customizing Dashboards 98

Using Microsoft Outlook to Manage the Sprint 100

Summary 101

Endnotes 101

5 Architecture 103

Architecture in the Agile Consensus 104

Exploring Existing Architectures 107

Summary 124

Endnotes 126

6 Development 129

Development in the Agile Consensus 130

The Sprint Cycle 131

Keeping the Codebase Clean 132

Staying “in the Groove” 139

Detecting Programming Errors Early 143

Catching Side Effects 154

Preventing Version Skew 162

Making Work Transparent 170

Summary 171

Endnotes 173

7 Build and Lab 175

Cycle Time 176

Defining Done 177

Continuous Integration 179

Automating the Build 181

Automating Deployment to Test Lab 186

Elimination of Waste 199

Summary 203

Endnotes 204

8 Test 207

Testing in the Agile Consensus 208

Testing Product Backlog Items 211

Actionable Test Results and Bug Reports 215

Handling Bugs 223

Which Tests Should Be Automated? 223

Automating Scenario Tests 224

Load Tests, as Part of the Sprint 228

Production-Realistic Test Environments 234

Risk-Based Testing 236

Summary 238

Endnotes 239

9 Lessons Learned at Microsoft Developer Division 241

Scale 242

Business Background 243

Improvements after 2005 247

Results 256

Acting on the Agile Consensus 256

Lessons Learned 258

The Path to Visual Studio 2012 262

Endnotes 263

10 Continuous Feedback 265

Agile Consensus in Action 266

Continuous Feedback Allows Build/Measure/Learn 267

There’s No Place Like Production 269

Summary 271

Endnotes 274

Index 275

Read More Show Less

Customer Reviews

Average Rating 5
( 4 )
Rating Distribution

5 Star

(3)

4 Star

(1)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 4 Customer Reviews
  • Anonymous

    Posted June 4, 2014

    To Stan

    I think you should triple check posts. I caught spelling mistakes. People get irritated by that. I quadruple check posts sometimes. Besides, bad grammar and spelling usually irritate people pretty easily.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted June 4, 2014

    To stan

    When you say a 'bad' word, use the technique. Put < _ > inbetween the word. Like this: les < _ > bian. Without the spaces.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted June 4, 2014

    To stan

    Have a joke section or a riddle!

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted June 4, 2014

    |☺Suggestions!☺|

    Have a suggestion of some sort for The N-Logs? Here is where to do it! Anyone being a jackina.pse in suggestions will be ignored. And no, I did not just curse, cuz I don't curse. Look up jackina.pse without the . and see what it means if ya don't believe me! I am always open to SERIOUS suggestions (not junk like 'Stop being such a doofus')! I will take all suggestions into consideration, so if I don't use one, don't think I didn't even put it into thought!<p>

    ~Stan&#9786

    Was this review helpful? Yes  No   Report this review
Sort by: Showing all of 4 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)