DevOps on the Microsoft Stack

This book tells you everything you need to know to help your organization implement DevOps on the Microsoft platform. You will learn how to use Visual Studio, Visual Studio Team Services, and Azure to implement a complete DevOps process in your company. You will learn about Agile Project Management, Continuous Integration, Continuous Delivery, Technical Debt Management, Automatic Testing and Monitoring, and see how all these areas fit together. DevOps is important for organizations that want to make the best use of their resources and avoid costly mistakes. Teams that embrace DevOps deploy code up to 30 times more frequently than their competition and less than 50% of their deployments fail according to Puppet Labs State of DevOps survey. DevOps on the Microsoft Stack shows you how to help your organization implement DevOps, covering the tooling they will need and how to make everything work together while following best practices. The focus is not only on technology but also on the cultural issues that teams will face when implementing DevOps. The author's goal is to not only show you which tooling there is but help you to successfully use everything together to implement DevOps in your projects and organization. In this book, you'll learn: What DevOps is and how it can help development teams How to use Visual Studio, Visual Studio Team Services, and Azure to setup a DevOps process How to introduce DevOps to your organization and how to overcome problems Contents at a Glance 4 Contents 6 Foreword 12 About the Author 14 About the Technical Reviewers 16 Acknowledgments 18 Preface 20 Part I: Getting Started 21 Chapter 1: What Is DevOps? 22 Why Are We Doing DevOps? 22 Assessing Your DevOps Capability 25 Summary 27 Chapter 2: Introducing Azure and Visual Studio Team Services 28 Understanding the Microsoft Cloud: Azure 28 IaaS, PaaS, and SaaS 29 Security 30 Using Visual Studio Team Services 33 Security 34 The Need for Training 35 Summary 35 Part II: Plan 36 Chapter 3: Agile Project Management: The Importance of Communication 37 Agile Project Management 37 Agile Tooling 40 Sprints 40 Product Backlog Items 42 Tasks 45 Impediments 46 Bugs 48 Capacity 50 Team Rooms 54 Achieving Traceability with Developers 57 Summary 59 Chapter 4: Managing User Feedback: Knowing What to Build 60 Why We Need Better Communication 60 Creating Storyboards with PowerPoint 61 Involving Stakeholders in Feedback Management 64 Summary 70 Chapter 5: Advanced Agile Project Management 71 Kanban and Lean 71 Portfolio Management 83 Summary 91 Chapter 6: Dashboards and Reporting 92 Queries 92 Using the Search Box 92 Work Item Queries 94 Charts 98 Code Search 104 Dashboards 107 Alerts and Notifications 108 Summary 111 Part III: Code and Build 112 Chapter 7: Setting Up Version Control 113 Introducing Version Control 113 Using Team Foundation Version Control (TFVC) 117 Workspace 117 Checking in a Changeset 120 Get Latest and Merge Conflicts 124 History, Annotations, and CodeLens 125 Shelvesets and Suspending Your Work 128 Branches 133 Check-In Policies 136 Using the Git Version Control System 138 Clone 138 Commit and Push 139 Fetch and Pull 141 Branch 142 Pull Request 144 Choosing a Branching Strategy 148 Branch Scenarios 148 Feature Toggles 149 Summary 150 Chapter 8: Managing Technical Debt 151 Running Code Analysis 152 Code Metrics 155 Lines of Code 156 Cyclomatic Complexity 158 Coupling 158 Depth of Inheritance 160 Calculating Code Metrics 160 Finding Duplications 161 Validating the Architecture 163 Create and Run Unit Tests 166 Creating Custom Code Analyzers with Roslyn 170 Summary 174 Chapter 9: Implementing Continuous Integration 175 Configuring a Continuous Integration Build 176 Installing and Configuring Build Agents 187 Creating Custom Tasks 189 Using SonarQube 195 Summary 201 Chapter 10: Creating and Sharing Packages 202 What Are Packages? 202 Package Management for Visual Studio Team Services 208 Summary 214 Part IV: Test, Deploy, and Monitor 215 Chapter 11: Integrating Testers into DevOps 216 Manual Testing Through Web Access 216 Microsoft Test Manager 227 Automated Testing 231 Summary 240 Chapter 12: Implementing Continuous Delivery with Release Management 241 Understanding the Deployment Pipeline 241 Setting Up Automatic Releases with Release Management 242 Deploying Web Sites 256 Understanding Containers 266 Summary 269 Chapter 13: Using Application Insights 270 What Is Application Insights? 270 Configuring Monitoring for Your Application 272 Availability Monitoring 278 Usage Monitoring 281 Diagnose Failures and Exceptions 283 Summary 284 Chapter 14: The Path Forward 285 The Basics 285 Stepping It Up 288 Finishing Touches 289 Summary 290 Index 291

A radical approach to getting IT projects done faster and cheaper than anyone thinks possible

Software in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don't. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking.

The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it's good to fail early—all with no risk greater than thirty days.

• The productivity gain vs traditional "waterfall" methods has been over 100% on many projects
• Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the "Scrum" technique for building software in 30 days
• Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement

Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible.

Machine generated contents note: Section I: Why Every Business In The World Can Produce Software In Thirty Days This sections reviews how many organization struggle to develop software and how Software in Thirty Day's approach can eliminate the underlying problem. Chapter 1: The Crisis in Software: The Wrong Process Produces The Wrong Results Find out why so many software projects fail and why traditional methods are ill-suited to software development. Chapter 2: Scrum: The Right Process Produces the Right Results Understand the shift in thinking necessary to eliminate software project failure and deliver software in 30 days. Chapter 3: Try It Yourself: The Pilot You are interested. Learn how to run a pilot project that will successfully help you determine what to do next. Chapter 4: What Can I Do? Learn what you, as a manager, can do to make Software in 30 Days successful. Section II: Why Every Business In The World Can Produce Software In Thirty Days This section address how you can implement and embed Software in Thirty Days in your organization. Chapter 5: Getting Started with Scrum Understand how Scrum works. Chapter 6: Scrum at the Project Level Learn how to launch Scrum on a single project. Chapter 7: Develop a Scrum Capability Learn how to develop a Scrum capability in your organization. Chapter 8: Scrum at the Enterprise Level Consider spreading Scrum throughout the enterprise. Appendices 1: Terminology Look up terminology used in this book 2: Scrum Guide Read the canonical guide to Scrum 3: A Playbook for Achieving Enterprise Agility A Scrum enterprise adoption playbook in use since 1995. "A radical approach to getting IT projects done faster and cheaper than anyone thinks possible, Software in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don't. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking. The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it's good to fail early--all with no risk greater than thirty days. The productivity gain vs traditional "waterfall" methods has been over 100% on many projects Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the "Scrum" technique for building software in 30 days Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible"-- Provided by publisher This book tells you everything you need to know to help your organization implement DevOps on the Microsoft platform. You will learn how to use Visual Studio, Visual Studio Team Services, and Azure to implement a complete DevOps process in your company. You will learn about Agile Project Management, Continuous Integration, Continuous Delivery, Technical Debt Management, Automatic Testing and Monitoring, and see how all these areas fit together. DevOps is important for organizations that want to make the best use of their resources and avoid costly mistakes. Teams that embrace DevOps deploy code up to 30 times more frequently than their competition and less than 50% of their deployments fail according to Puppet Labs State of DevOps survey. DevOps on the Microsoft Stack shows you how to help your organization implement DevOps, covering the tooling they will need and how to make everything work together while following best practices. The focus is not only on technology but also on the cultural issues that teams will face when implementing DevOps. The author s goal is to not only show you which tooling there is but help you to successfully use everything together to implement DevOps in your projects and organization. In this book, you'll learn: What DevOps is and how it can help development teamsHow to use Visual Studio, Visual Studio Team Services, and Azure to setup a DevOps processHow to introduce DevOps to your organization and how to overcome problems " Annotation "Bill is an IT manager at Parts Unlimited. It's Tuesday morning and on his drive into the office, Bill gets a call from the CEO. The company's new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill's entire department will be outsourced. With the help of a prospective board member and his mysterious philosophy of The Three Ways, Bill starts to see that IT work has more in common with manufacturing plant work than he ever imagined. With the clock ticking, Bill must organize work flow streamline interdepartmental communications, and effectively serve the other business functions at Parts Unlimited. In a fast-paced and entertaining style, three luminaries of the DevOps movement deliver a story that anyone who works in IT will recognize. Readers will not only learn how to improve their own IT organizations, they'll never view IT the same way again."--Provided by publisher A Radical Approach to Fast, Valuable, and LowRisk Software Development Software development doesn't have to be slow and expensive anymore. The Agile and Scrum software development method allows creation of the gamechanging software you need to grow your business - in 30 days or less. Projects that use it are three times more successful than those that dont, and the productivity gain versus traditional "waterfall" methods has been over 100 percent on many projects. For the business manager, the entrepreneur, or IT manager, Software in 30 Days explains how this unorthodox process works, how to get started, and how to succeed. Learn powerful concepts such as the "art of the possible," "bottomup intelligence," and why its good to fail early. With simple but profound shifts in thinking, you will be able to control risk, manage projects, and deliver your best work possible, faster and cheaper than ever before. Front Matter....Pages i-xix Front Matter....Pages 1-1 What Is DevOps?....Pages 3-8 Introducing Azure and Visual Studio Team Services....Pages 9-16 Front Matter....Pages 17-17 Agile Project Management: The Importance of Communication....Pages 19-41 Managing User Feedback: Knowing What to Build....Pages 43-53 Advanced Agile Project Management....Pages 55-75 Dashboards and Reporting....Pages 77-96 Front Matter....Pages 97-97 Setting Up Version Control....Pages 99-136 Managing Technical Debt....Pages 137-160 Implementing Continuous Integration....Pages 161-187 Creating and Sharing Packages....Pages 189-201 Front Matter....Pages 203-203 Integrating Testers into DevOps....Pages 205-229 Implementing Continuous Delivery with Release Management....Pages 231-259 Using Application Insights....Pages 261-275 The Path Forward....Pages 277-282 Back Matter....Pages 283-288 Telling you 'everything you need to know' to help your organization implement DevOps on the Microsoft platform, this book teaches how to use Visual Studio, Visual Studio Team Services and Azure to implement a complete DevOps process, including how to introduce DevOps to your organization and how to overcome problems. The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win is the third book by Gene Kim. The business novel tells the story of an IT manager who has ninety days to rescue an over-budget and late IT initiative, code-named The Phoenix Project. Wouter De Kort. Place Of Publication From The Publisher's Website (viewed July 28, 2016). Includes Index.