Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Accelerate DevOps with GitHub
  • Toc
  • feedback
Accelerate DevOps with GitHub

Accelerate DevOps with GitHub

By : Michael Kaufmann
5 (11)
close
Accelerate DevOps with GitHub

Accelerate DevOps with GitHub

5 (11)
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)
close
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

Tests and compliance

Most compliance standards, such as ISO26262 for automotive or GAMP for pharma, follow the V-Model as a development process. The V-Model requires the user and system requirements to be decomposed and specifications to be created at different levels of detail. This is the left-hand side of the V. It also requires all the levels to be validated to ensure that the system fulfills the requirements and specifications. This is the right-hand side of the V. Both sides can be seen in Figure 12.8:

Figure 12.8 – Validation in the V-Model

This model must be combined with risk analysis, which is performed at every level of detail. Many documents must be signed during the release phase. This leads to a slow waterfall process with long specification, development, and release phases.

But the standards are based on good practices – and if your practices are better than the ones in the standard, you can justify that in the audits. The standards...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete