Book Image

Accelerate DevOps with GitHub

By : Michael Kaufmann
Book Image

Accelerate DevOps with GitHub

By: Michael Kaufmann

Overview of this book

This practical guide to DevOps uses GitHub as the DevOps platform and shows how you can leverage the power of GitHub for collaboration, lean management, and secure and fast software delivery. The chapters provide simple solutions to common problems, thereby helping teams that are already on their DevOps journey to further advance into DevOps and speed up their software delivery performance. From finding the right metrics to measure your success to learning from other teams’ success stories without merely copying what they’ve done, this book has it all in one place. As you advance, you’ll find out how you can leverage the power of GitHub to accelerate your value delivery – by making work visible with GitHub Projects, measuring the right metrics with GitHub Insights, using solid and proven engineering practices with GitHub Actions and Advanced Security, and moving to event-based and loosely coupled software architecture. By the end of this GitHub book, you'll have understood what factors influence software delivery performance and how you can measure your capabilities, thus realizing where you stand in your journey and how you can move forward.
Table of Contents (31 chapters)
1
Part 1: Lean Management and Collaboration
7
Part 2: Engineering DevOps Practices
14
Part 3: Release with Confidence
19
Part 4: Software Architecture
22
Part 5: Lean Product Management
25
Part 6: GitHub for your Enterprise

Data-driven transformation

If you want your transformation to succeed, it is critical to measure the right metrics and to prove that the transformation really yields better results than the old system. That’s why, in Chapter 1, Metrics That Matter, I introduced the data points you can collect to know what to optimize first and to achieve small wins that will help you keep everyone motivated to continue with the DevOps transformation. Measuring the right data should always be the start. Optimizing something that is not a constraint is a waste of resources and can even have a negative impact. Let’s take adding caching to your application without proof that the operation was slowing down the system in the first place or of how much faster it can be when caching certain data, as an example. Caching introduces complexity and is a source of errors. So, maybe you did not optimize the system at all but made it worse by working based on assumptions. The same is true for your DevOps...