{"id":22674270,"url":"https://github.com/wulfland/acceleratedevops","last_synced_at":"2025-04-05T00:05:50.218Z","repository":{"id":37077509,"uuid":"383720539","full_name":"wulfland/AccelerateDevOps","owner":"wulfland","description":"This is the companion repository for my book Accelerate DevOps with GitHub (2022). You can find all hands-on labs and other examples from the book here. Please reach out to me if something is broken.","archived":false,"fork":false,"pushed_at":"2024-12-16T18:06:19.000Z","size":9852,"stargazers_count":42,"open_issues_count":65,"forks_count":79,"subscribers_count":4,"default_branch":"main","last_synced_at":"2025-04-05T00:05:42.433Z","etag":null,"topics":["devops","github"],"latest_commit_sha":null,"homepage":"https://www.amazon.com/dp/B0B4DW7NSL/ref=cm_sw_r_tw_dp_B4DR80D2BBERYNSQ5V9C","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/wulfland.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2021-07-07T08:01:50.000Z","updated_at":"2025-02-02T05:52:22.000Z","dependencies_parsed_at":"2024-05-02T17:50:36.624Z","dependency_job_id":"f79ab264-28bd-4546-9d9e-950c021d6c57","html_url":"https://github.com/wulfland/AccelerateDevOps","commit_stats":{"total_commits":405,"total_committers":4,"mean_commits":101.25,"dds":0.3012345679012346,"last_synced_commit":"5eda667df4089e2841b3a331c653d26ebe4a388c"},"previous_names":[],"tags_count":13,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wulfland%2FAccelerateDevOps","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wulfland%2FAccelerateDevOps/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wulfland%2FAccelerateDevOps/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wulfland%2FAccelerateDevOps/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/wulfland","download_url":"https://codeload.github.com/wulfland/AccelerateDevOps/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247266563,"owners_count":20910836,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["devops","github"],"created_at":"2024-12-09T17:14:45.872Z","updated_at":"2025-04-05T00:05:50.195Z","avatar_url":"https://github.com/wulfland.png","language":"JavaScript","funding_links":["https://github.com/sponsors","https://github.com/sponsors/curl","https://github.com/sponsors/dennisdoomen","https://github.com/sponsors/JanDeDobbeleer"],"categories":[],"sub_categories":[],"readme":"# Accelerate DevOps with GitHub\n\n**Enhance Software Delivery Performance with GitHub Issues, Projects, Actions, and Advanced Security**\n\nThis is the companion repository for my book [Accelerate DevOps with GitHub](https://www.amazon.com/dp/B0B4DW7NSL/ref=cm_sw_r_tw_dp_B4DR80D2BBERYNSQ5V9C). You can find all hands-on labs and other examples from the book here. I also provide all the links and references from the chapters.\n\n## Part 1: Lean Management and Collaboration\n\nIn Part 1 you will learn how to reduce ballast from your development process and move to a lean and collaborative way of working that allows your teams to accelerate their value delivery. You’ll learn how to use GitHub to work together from everywhere effectively and use work insights and the right metrics to optimize your engineering productivity.\n\n### Chapter 1: Metrics that Matter\n\nIn this chapter I explain how to measure engineering velocity and developer productivity and how to make your DevOps acceleration measurable.\nThe following topics will are covered in this chapter:\n-\tWhy Accelerate?\n-\tEngineering Velocity\n-\tHigh Performance Companies\n-\tMeasuring metrics that matter\n-\tThe SPACE of Developer Productivity\n-\tObjectives and Key-Results\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Srivastava S., Trehan K., Wagle D. \u0026 Wang J. (April 2020). [Developer Velocity: How software excellence fuels business performance]( https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/developer-velocity-how-software-excellence-fuels-business-performance).\n- Forsgren N., Smith D., Humble J., Frazelle J. (2019). [DORA State of DevOps Report](https://www.devops-research.com/research.html#reports)\n- Brown A., Stahnke M. \u0026 Kersten N. (2020). [2020 State of DevOps Report](https://puppet.com/resources/report/2020-state-of-devops-report/)\n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- Coupland M (2021). DevOps Adoption Strategies: Principles, Processes, Tools, and Trends: Embracing DevOps through effective culture people, and processes (1st ed.) [E-book]. Packt.\n- Dina Graves Portman (2020). [Are you an Elite DevOps performer? Find out with the Four Keys Project]( https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance)\n- Forsgren N., Storey M.-A., Maddila C., Zimmermann T., Houck B., \u0026 Butler J. (2021). [The SPACE of Developer Productivity]( https://queue.acm.org/detail.cfm?id=3454124)\n- Grove, A. S. (1983). High Output Management (1st ed.). Random House Inc.\n- Grove, A. S. (1995). High Output Management (2nd ed.). Vintage.\n- Doerr, J. (2018). Measure What Matters: OKRs: The Simple Idea that Drives 10x Growth. Portfolio Penguin\n\n\u003c/details\u003e\n\n### Chapter 2: Plan, Track, and Visualize Your Work\n\nIn this chapter we will focus on organizing your work inside your team and apply Lean Principles. You’ll learn how GitHub Issues and Projects can help you to simplify your flow of work. \n\nIn this chapter we will cover the following topics:\n-\tWork is work\n-\tUnplanned work and rework\n-\tVisualizing your work\n-\tLimiting work in progress (WIP)\n-\tGitHub issues, labels, and milestones\n-\tGitHub projects\n\nHighlights:\n\n- Follow the [About GitHub markdown](https://github.com/wulfland/AccelerateDevOps/issues/232) for all updates on GitHub flavored markdown. See [this page](docs/about-markdown.md?plain=1) for the source and [rendered version](docs/about-markdown.md).\n- See the [issue templates](.github/ISSUE_TEMPLATE) in [action](../../issues/new/choose).\n- Check out the [Team Backlog](https://github.com/users/wulfland/projects/9) - an example for GitHub Projects.\n- See the [Azure Boards integration](https://dev.azure.com/wulfland/GitHub%20Integration/_boards/board/t/GitHub%20Integration%20Team/Issues)\n\n[![Board Status](https://dev.azure.com/wulfland/dc3f49e0-ea99-4a3a-b60c-772563921d52/e625f6c9-996b-4916-8e05-542c2cde028c/_apis/work/boardbadge/b675898f-85c1-4ee1-92b9-2f484b1256a0)](https://dev.azure.com/wulfland/dc3f49e0-ea99-4a3a-b60c-772563921d52/_boards/board/t/e625f6c9-996b-4916-8e05-542c2cde028c/Microsoft.RequirementCategory)\n\n[![Board Status](https://dev.azure.com/wulfland/dc3f49e0-ea99-4a3a-b60c-772563921d52/e625f6c9-996b-4916-8e05-542c2cde028c/_apis/work/boardbadge/b675898f-85c1-4ee1-92b9-2f484b1256a0?columnOptions=1)](https://dev.azure.com/wulfland/dc3f49e0-ea99-4a3a-b60c-772563921d52/_boards/board/t/e625f6c9-996b-4916-8e05-542c2cde028c/Microsoft.RequirementCategory/)\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n-\tTregubov A., Rodchenko N., Boehm B. \u0026 Lane J.A. (2017). [Impact of Task Switching and Work Interruptions on Software Development Processes]( https://www.researchgate.net/publication/317989659_Impact_of_task_switching_and_work_interruptions_on_software_development_processes)\n-\tWeinberg G.M. (1991), Quality Software Management: Systems Thinking (1st ed.). Dorset House \n-\t[GitHub issues](https://guides.github.com/features/issues/) and [about GitHub issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues)\n-\t[Markdown](https://guides.github.com/features/mastering-markdown/)\n-\t[Issue templates](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)\n-\t[GitHub projects](https://docs.github.com/en/issues/trying-out-the-new-projects-experience/about-projects)\n-\t[GitHub Jira integration](https://github.com/atlassian/github-for-jira)\n-\t[GitHub Azure Boards integration](https://docs.microsoft.com/en-us/azure/devops/boards/github)\n\n\u003c/details\u003e\n\n### Chapter 3: Teamwork and Collaborative Development\n\nA high performing team is more than the sum of its members, and it takes a high performing team to build products that people love.\nIn this chapter you’ll learn how to set up your team for high collaborative development using pull requests. You’ll learn what a pull request is and what features can help you to get a good code review workflow for your team.\nThe following are the core topics that we will cover in this chapter:\n-\tSoftware development is a team sport\n-\tThe heart of collaboration: the pull request\n-\tPropose changes using pull requests\n-\tPull request reviews\n-\tFinishing pull request\n-\tBest practices for code reviews\n\nHands-on exercices: ✋\n\n1. [Create a pull request](ch3_pull-request/Create-PullRequest.md)\n2. [Review Changes](ch3_pull-request/Review-Changes.md)\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n\nLink to the video on [how GitHub uses GitHub to collaborate](https://youtu.be/HyvZO5vvOas?t=3189).\n\n-\tCoyle D. (2018). The Culture Code: The Secrets of Highly Successful Groups (1st ed.). Cornerstone Digital\n-\tKim G., Humble J., Debois P. \u0026 Willis J. (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations (1st ed.). IT Revolution Press\n-\tScott Prugh (2014), [Continuous Delivery](https://www.scaledagileframework.com/guidance-continuous-delivery/).\n-\tChacon S. \u0026 Straub B. (2014). [Pro Git (2nd ed.)](https://git-scm.com/book/de/v2). Apress.\n-\tKaufmann M. (2021), Git für Dummies (1st ed., German). Wiley-VCH\n-\t[Git](https://en.wikipedia.org/wiki/Git)\n-\t[Pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)\n-\t[Code owners](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners)\n-\t[Branch protection](https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)\n-\t[Code review assignments](https://docs.github.com/en/organizations/ organizing-members-into-teams/managing-code-review-assignment-for-your-team)\n-\t[Auto-Merge](https://docs.github.com/en/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)\n-\t[Pull request reviews](https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)\n\n\u003c/details\u003e\n\n### Chapter 4: Asynchronous Work: Collaborate from Anywhere\n\nIn this chapter we’ll focus on synchronous and asynchronous work and how you can use the benefits of asynchronous workflows for a better collaboration in distributed, remote, and hybrid teams and a better cross-team collaboration.\nThe following are the topics that will be covered in the chapter:\n-\tComparing synchronous and asynchronous work\n-\tDistributed teams\n-\tCross-team collaboration\n-\t[GitHub Discussions](https://docs.github.com/en/discussions)\n-\t[GitHub Pages](https://docs.github.com/en/pages) and Wikis\n-\tWorking from everywhere with GitHub Mobile\n\nHighlights:\n\n- [Discussions](https://github.com/wulfland/AccelerateDevOps/discussions) in the main menu of this repository.\n- GitHub Pages: see [the rendered output](https://wulfland.github.io/AccelerateDevOps/) and check out the files in [/docs](docs) that are the source - especially the [_config.yml](/docs/_config.yml).\n- [Sample GitHub Wiki](https://github.com/wulfland/AccelerateDevOps/wiki).\n- Also see the sample pages for a ToC in [AsciiDoc](https://github.com/wulfland/AccelerateDevOps/wiki/AsciiDoc-ToC) and [MediaWiki](https://github.com/wulfland/AccelerateDevOps/wiki/MediaWiki-ToC).\n- A sample for navigation and ToC in a custom wiki can be found [here](ch4_customWiki/Home.md).\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n-\t[History of communication 1](https://en.wikipedia.org/wiki/History_of_communication) \n- [History of communication 2](https://www.g2.com/articles/history-of-communication)\n- [Time capsule: 150 years](https://www.elon.edu/u/imagining/time-capsule/150-years/)\n-\t[History in general](https://www.dhm.de/lemo/kapitel) (in German)\n-\t[World population growth](https://ourworldindata.org/world-population-growth)\n-\t[Hybrid work](https://www.microsoft.com/en-us/worklab/work-trend-index/hybrid-work) \n-\t[Work trend index](https://www.microsoft.com/en-us/worklab/work-trend-index)\n-\t[GitHub Discussions](https://docs.github.com/en/discussions)\n-\t[GitHub Pages](https://docs.github.com/en/pages)\n-\t[GitHub Mobile](https://github.com/mobile)\n\n\u003c/details\u003e\n\n### Chapter 5: The Influence of Open and Inner Source on Software Delivery Performance\n\nIn this chapter I explain the history of free and open-source software and why it has become so important over the last years. I will explain the impact it can have on your engineering velocity and how you can use the principles of open source for better cross-team collaboration in your company (inner source).\nThe chapter will cover:\n- History of free and open-source software\n- The difference between open source and open development\n- Benefits of embracing open source for companies\n- Implementing an open-source strategy\n- Open and inner source\n- Importance for insourcing\n- [GitHub Sponsors](https://github.com/sponsors)\n\nFeatured open-source projects to sponsor:\n\n- [curl](https://github.com/curl) is the example for an organization that you can sponsor. Curl is used every day by thousands of developers worldwide (sponsor [the project here](https://github.com/sponsors/curl)).\n- [Dennis Doomen](https://github.com/dennisdoomen) is the example for `Sponsor tiers`. He is the author of [FluentAssertions](https://github.com/fluentassertions/fluentassertions) - a .NET library I use in most of my C# projejcts ([sponsor Dennis here](https://github.com/sponsors/dennisdoomen)). \n- [Jan De Dobbeleer](https://github.com/jandedobbeleer) is the example for `Sponsorship goals`. He is the maintainer of [oh-my-posh](https://github.com/JanDeDobbeleer/oh-my-posh) - a highly customizable and extensible prompt theme engine for PowerShell ([sponsor Jan here](https://github.com/sponsors/JanDeDobbeleer)).\n\nAt the time writing the book, `GitHub Sponsors` was new and I worked with some of the mainters mentioned to set this up in a good way. So not all projects made it here - for example [oh-my-zsh](https://github.com/ohmyzsh/ohmyzsh), which I use every day and which was the inspiration for oh-my-posh.\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Greene T. C. (2001). [Ballmer: Linux is a cancer](https://www.theregister.com/2001/06/02/ballmer_linux_is_a_cancer/) \n- Warren T. (2020). [Microsoft: we were wrong about open source](https://www.theverge.com/2020/5/18/21262103/microsoft-open-source-linux-history-wrong-statement) \n- Raymond, E. S. (1999). The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary. O'Reilly Media.\n- O’Reilly (1998). FREEWARE LEADERS MEET IN FIRST-EVER SUMMIT O'Reilly Brings Together Creators of Perl, Apache,Linux and Netscape's Mozilla. [Press Release](https://www.oreilly.com/pub/pr/636) \n- OSI (2018). [Open Source Initiative - History of the OSI](https://opensource.org/history)\n- Richard S. (2021). [Why Open Source Misses the Point of Free Software](https://www.gnu.org/philosophy/open-source-misses-the-point.en.html) \n- Volpi M. (2019). [How open-source software took over the world](https://techcrunch.com/2019/01/12/how-open-source-software-took-over-the-world/) \n- Ahlawat P., Boyne J., Herz D., Schmieg F., \u0026 Stephan M. (2021). [Why You Need an Open Source Software Strategy](https://www.bcg.com/publications/2021/open-source-software-strategy-benefits) \n- [Inner Source](https://en.wikipedia.org/wiki/Inner_source) \n- [GitHub Sponsors](https://github.com/sponsors) \n\n\u003c/details\u003e\n\n## Part 2: Engineering DevOps Practices\n\nPart 2 explains the most important engineering practices for effective DevOps. You’ll learn how to use GitHub Actions to automate your release pipelines and other engineering tasks, how to work trunk-based and with feature-flags and how to shift left security and quality assurance.\n\n### Chapter 6: Automation with GitHub Actions\n\nThis chapter explains the importance of automation for quality and speed. It introduces you to GitHub Actions and how you can use them for any kind of automation – not only continuous delivery.\n\n- Overview of GitHub Actions \n- Workflows, pipelines, and actions\n- [YAML](https://yaml.org/) basics\n- The workflow syntax\n- Working with secrets\n- ✋ Hands-on: [Your first workflow](https://github.com/wulfland/getting-started)\n- ✋ Hands-on: [Your first action](https://github.com/actions/container-action)\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Humble J., \u0026 Farley, D. (2010). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Addison-Wesley Professional.\n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- [YAML](https://yaml.org/)\n- [GitHub Actions](https://docs.github.com/en/actions)\n- [GitHub Learning Lab](https://lab.github.com)\n- [Workflow syntax](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions)\n- [GitHub Marketplace](https://github.com/marketplace)\n\n\u003c/details\u003e\n\n### Chapter 7: Running Your Workflows\n\nIn this chapter, I’ll show you the different options for running your workflows. We’ll investigate hosted and self-hosted runners, and I’ll explain how you can tackle hybrid-cloud scenarios or hardware-in-the-loop tests using the different hosting options. I’ll also show you how to set up, manage, and scale self-hosted runners, and I’ll show you how you can approach monitoring and troubleshooting.\nThe following are the core topics that we will cover in this chapter:\n- Hosted runners\n- Self-hosted runners\n- Managing access with runner groups\n- Using labels\n- Scaling your self-hosted runners\n- Monitoring and troubleshooting\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- [Using GitHub-hosted runners](https://docs.github.com/en/actions/using-github-hosted-runners)\n- [Virtual environments](https://github.com/actions/virtual-environments) \n- [Hosting your own runners](https://docs.github.com/en/actions/hosting-your-own-runners)\n- A [curated list](https://jonico.github.io/awesome-runners) of awesome self-hosted GitHub Action runner solutions in a large comparison matrix.\n\n\u003c/details\u003e\n\n### Chapter 8: Managing Dependencies Using GitHub Packages\n\nThis chapter describes how you can use GitHub Packages, semantic Versioning together with GitHub Actions to manage dependencies between your teams and products.\nThe main topics are as follows:\n- GitHub Packages\n- ✋ Hands-on: [Use npm packages with Actions](https://github.com/wulfland/package-demo)\n- ✋ Hands-on: [Use Docker with Packages](https://github.com/wulfland/container-demo)\n- Apache Maven, Gradle, NuGet, and RubyGems packages\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- [Semantic versioning](https://semver.org/)\n- [Billing and pricing](https://docs.github.com/en/billing/managing-billing-for-github-packages/about-billing-for-github-packages)\n- [Access control and visibility](https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)\n- [Working with the registry (Container, Apache Maven, Gradle. NuGet, npm, RubyGems)](https://docs.github.com/en/packages/working-with-a-github-packages-registry)\n\n\u003c/details\u003e\n\n### Chapter 9: Deploy to Any Platform\n\nIn this chapter I'll show you how you can easily deploy to any cloud and any platform in a secure and compliant way.\nThe chapter will cover:\n- [Staged deployments](/../../actions/workflows/StagedDeployment.yml)\n- Automate your deployments\n- ✋ Hands-on: [Deploy to Azure App Service](ch9_release/Deploy_to_Azure_App_Service.md)\n- ✋ Hands-on: [Deploy to AWS Elastic Container Service (ECS)](ch9_release/Deploy_to_AWS_ECS.md)\n- ✋ Hands-on: [Deploy to Google Kubernetes Engine (GKE)](ch9_release/Deploy_to_GKE.md)\n- Infrastructure as Code\n- [Workflow templates](https://github.com/accelerate-devops/.github/tree/main/workflow-templates)\n- [Reusable workflows](.github/workflows/reusable.yml) and [how they are used](.github/workflows/reuse.yml)\n- Measuring success\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- [CI/CD](https://azure.microsoft.com/en-us/overview/continuous-delivery-vs-continuous-deployment/)\n- [Deployment rings](https://docs.microsoft.com/en-us/azure/devops/migrate/phase-rollout-with-rings)\n- [Deploying to Azure App Service](https://docs.github.com/en/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service)\n- [Deploying to Google Kubernetes Engine](https://docs.github.com/en/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine)\n- [Deploy to AWS Elastic Container Service](https://docs.github.com/en/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service)\n- [Security hardening your deployments](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments)\n- [Kubernetes Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/)\n- [Kubernetes Deployment Strategies](https://github.com/ContainerSolutions/k8s-deployment-strategies)\n- [Helm](https://helm.sh/)\n- [Kustomize](https://kustomize.io/)\n- [Infrastructure as Code](https://en.wikipedia.org/wiki/Infrastructure_as_code)\n- [Infrastructure as Code and environment or configuration drift](https://docs.microsoft.com/en-us/devops/deliver/what-is-infrastructure-as-code)\n- [Workflow templates](https://docs.github.com/en/actions/learn-github-actions/creating-workflow-templates)\n- [Reusable workflows](https://docs.github.com/en/actions/learn-github-actions/reusing-workflows)\n- [Four Keys Project](https://github.com/GoogleCloudPlatform/fourkeys/)\n\n\u003c/details\u003e\n\n### Chapter 10: Feature Flags and the Feature Lifecycle\n\nThis chapter explains how Feature Flags – or Feature Toggles - can help you to reduce complexity and manage the lifecycle of features and your software.The main topics of this chapter are:\n- What are Feature Flags\n- The lifecycle of features\n- The benefits of Feature Flags\n- Getting started with Feature Flags\n- Feature Flags and technical debt\n- Experimentation with Feature Flags\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Martin Fowler (2017). [Feature-Toggles (aka Feature Flags)](https://martinfowler.com/articles/feature-toggles.html) \n- [Comparison of Feature Flag Solutions](https://wulfland.github.io/FeatureFlags/)\n- [LaunchDarkly](https://launchdarkly.com/)\n- [Switchover](https://switchover.io/)\n- [VWO](https://vwo.com/)\n- [Split](https://www.split.io/)\n- [Flagship](https://www.flagship.io/)\n- [Unleash](https://www.getunleash.io/) and [on GitHub](https://github.com/Unleash/unleash)\n\n\u003c/details\u003e\n\n### Chapter 11: Trunk-based Development\n\nThis chapter explains the benefits of trunk-based development and introduces you to the best git workflows to accelerate your software delivery.\n\nThe chapter covers:\n- [Trunk-based development]( https://trunkbaseddevelopment.com)\n- Why you should avoid complex branching\n- Other git workflows\n- Accelerate with [MyFlow](https://writeabout.net/2021/12/21/myflow-a-successful-git-branching-model-for-devops-teams/)\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- [Trunk-based development]( https://trunkbaseddevelopment.com)\n- Git flow: Vincent Driessen (2010), [A successful Git branching model](https://nvie.com/posts/a-successful-git-branching-model/)\n- [GitLab flow](https://docs.gitlab.com/ee/topics/gitlab_flow.html)\n- Edward Thomson (2018). [Release Flow: How We Do Branching on the VSTS Team](https://devblogs.microsoft.com/devops/release-flow-how-we-do-branching-on-the-vsts-team/)\n- Aman Gupta (2015). [Deploying branches to GitHub.com](https://github.blog/2015-06-02-deploying-branches-to-github-com/) \n- [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow)\n- [GitHub CLI](https://cli.github.com/) \n\n\u003c/details\u003e\n\n## Part 3: Release with Confidence\n\nPart 3 explains how you can accelerate even further and release frequently with confidence by baking quality assurance and security into your release pipelines. This includes concepts like shifting left testing and security, testing in production, chaos engineering, DevSecOps, securing your software supply chain, and ring-based deployments.\n\n### Chapter 12: Shift Left Testing for Increased Quality\n\ntakes a closer look at the role of quality assurance and testing on developer velocity and shows how you can shift left testing with test automation. The chapter also covers testing in production and chaos engineering.\n\nMain topics in the chapter are:\n- Shift left testing with test automation\n- Eradicating flaky tests\n- Code coverage\n- Shift right – testing in production\n- Fault injection and chaos engineering \n- Tests and compliance\n- Test management in GitHub\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- Eran Kinsbruner (2018), Continuous Testing for DevOps Professionals: A Practical Guide From Industry Experts (Kindle Edition). CreateSpace Independent Publishing Platform.\n- Sam Laing (2015), [The Testing Manifesto](https://www.growingagile.co.za/2015/04/the-testing-manifesto/).\n- Wolfgang Platz, Cynthia Dunlop (2019), Enterprise Continuous Testing: Transforming Testing for Agile and DevOps (Kindle Edition), Independently published.\n- Tilo Linz (2014): Testing in Scrum (E-book), Rocky Nook.\n- Kaner C., Falk J., H. Q. Nguyen (1999), Testing Computer Software (2nd Edition) Wiley.\n- Roy Osherove (2009), The Art of Unit Testing (1st edition), Manning.\n- Martin Fowler (2007), [Mocks Aren't Stubs](https://martinfowler.com/articles/mocksArentStubs.html).\n- Müller, Matthias M.; Padberg, Frank (2017). About the Return on Investment of Test-Driven Development (PDF). Universität Karlsruhe, Germany.\n- Erdogmus, Hakan; Morisio, Torchiano (2014). On the Effectiveness of Test-first Approach to Programming. Proceedings of the IEEE Transactions on Software Engineering, 31(1). January 2005. (NRC 47445).\n- [Shift left to make testing fast and reliable](https://docs.microsoft.com/en-us/devops/develop/shift-left-make-testing-fast-reliable).\n- Martin Fowler (2011), [Eradicating Non-Determinism in Tests](https://martinfowler.com/articles/nonDeterminism.html).\n- Jordan Raine (2020). [Reducing flaky builds by 18x](https://github.blog/2020-12-16-reducing-flaky-builds-by-18x/).\n- John Micco (2016). [Flaky Tests at Google and How We Mitigate Them](https://testing.googleblog.com/2016/05/flaky-tests-at-google-and-how-we.html).\n- [Shift right to test in production](https://docs.microsoft.com/en-us/devops/deliver/shift-right-test-production).\n- Michael Nygard (2018). Release It! Design and Deploy Production-Ready Software (2nd Edition).  O'Reilly.\n\n\u003c/details\u003e\n\n### Chapter 13, Shift Left Security ad DevSecOps\n\nThis chapter takes a broader look at the role of security in software development and how you can bake security into the process and practice DevSecOps, zero-trust, and how you can shift left security. The chapter looks at common attack scenarios and how you can practice security and create awareness using attack simulations and red team | blue team exercises. The chapter also introduces you to GitHub Codespaces as a secure development environment in the cloud.\n\nThe key points that we will cover in this chapter are:\n- Shift left security\n- Assume breach, zero trust, and a security first mindset\n- Attack simulations\n- Red team | blue team exercises\n- Attack scenarios\n- GitHub Codespaces\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- IC3 (2020). [Internet Crime Report 2020](https://www.ic3.gov/Media/PDF/AnnualReport/2020_IC3Report.pdf).\n- IC3 (2019). [Internet Crime Report 2019](https://www.ic3.gov/Media/PDF/AnnualReport/2019_IC3Report.pdf).\n- [Data reaches in 2020](https://www.identityforce.com/blog/2020-data-breaches).\n- [Data breaches in 2021](https://www.identityforce.com/blog/2021-data-breaches).\n- Terranova \u0026 Microsoft (2021). [Gone Phishing Tournament - Phishing Benchmark Global Report 2021](https://terranovasecurity.com/gone-phishing-tournament/).\n- [GitHub Codespaces](https://docs.github.com/en/codespaces/).\n- [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference).\n\n\u003c/details\u003e\n\n### Chapter 14, Securing Your Code\n\nThis chapter describes how you can use GitHub Advanced Security to eliminate bugs, security, and compliance issues by performing static code analysis with CodeQL and other tools, successfully manage your software supply chain with Dependabot, and eliminate secrets in your code base using Secret Scanning.\n\nThe key topics in this chapter are:\n- Dependency management and Dependabot\n- Automate dependabot with GitHub Actions (see [auto-merge.yml](.github/workflows/auto-merge.yml) and [dependabot.yml](.github/dependabot.yml)) \n- Secret Scanning\n- [Code Scanning](.github/workflows/codeql-analysis.yml)\n- Writing your own CodeQL queries\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Keith Collins (2016). [How one programmer broke the internet by deleting a tiny piece of code](https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code/).\n- Tyler Eon (2016). [Kik, Left-Pad, and NPM — Oh My!](https://medium.com/@kolorahl/kik-left-pad-and-npm-oh-my-e6f216a22766)\n- Maya Kaczorowski (2020). [Secure at every step: What is software supply chain security and why does it matter?](https://github.blog/2020-09-02-secure-your-software-supply-chain-and-protect-against-supply-chain-threats-github-blog/)\n- [About the dependency graph](https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).\n- [About dependabot version updates](https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates).\n- [About secret scanning](https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning).\n- [About GitHub Advanced Security](https://docs.github.com/en/get-started/learning-about-github/about-github-advanced-security).\n- [About Code Scanning](https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning).\n- GitHub Blog (2021). [CodeQL code scanning: new severity levels for security alerts](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).\n- [Common Vulnerability Scoring System (CVSS)](https://www.first.org/cvss/v3.1/specification-document)\n- [CodeQL documentation](https://codeql.github.com/docs/)\n- [CodeQL Language Reference](https://codeql.github.com/docs/ql-language-reference)\n\n\u003c/details\u003e\n\n### Chapter 15, Securing Your Deployments\n\nThis chapter shows how you can secure deployments to your environments and how you can automate your complete release pipeline in a secure, compliant way to also meet regulatory requirements. The chapter covers Software Bills of Meterials (SBoM), code and commit signing, dynamic application security testing, and security hardening your release pipelines.\nWe will cover the following main topics in this chapter:\n- Container and infrastructure security scanning\n- Automate the infrastructure change process\n- Source code and infrastructure integrity\n- Signing commits and code\n- Dynamic Application Security Testing\n- Security hardening your release pipeline\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Kim G., Humble J., Debois P. \u0026 Willis J. (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations (1st ed.). IT Revolution Press\n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- Oladimeji S., Kerner S. M. (2021). [SolarWinds hack explained: Everything you need to know](https://whatis.techtarget.com/feature/SolarWinds-hack-explained-Everything-you-need-to-know).\n- Sudhakar Ramakrishna (2021). [New Findings From Our Investigation of SUNBURST](https://orangematter.solarwinds.com/2021/01/11/new-findings-from-our-investigation-of-sunburst/).\n- Crowdstrike blog (2021). [SUNSPOT: An Implant in the Build Process](https://www.crowdstrike.com/blog/sunspot-malware-technical-analysis/).\n- Eckels S., Smith J. \u0026 Ballenthin W. (2020). [SUNBURST Additional Technical Details](https://www.mandiant.com/resources/sunburst-additional-technical-details)\n- Souppaya M., Morello J., \u0026 Scarfone K. (2017). [Application Container Security Guide](https://doi.org/10.6028/NIST.SP.800-190).\n- National Telecommunications and Information Administration (NTIA), [Software Bill of Materials](https://www.ntia.gov/sbom).\n- Thomas Claburn (2018). [Check your repos... Crypto-coin-stealing code sneaks into fairly popular NPM lib (2m downloads per week)]( https://www.theregister.com/2018/11/26/npm_repo_bitcoin_stealer/).\n- Haymore A., Smart I., Gazdag V., Natesan D., \u0026 Fernick J. (2022). [10 real-world stories of how we’ve compromised CI/CD pipelines]( https://research.nccgroup.com/2022/01/13/10-real-world-stories-of-how-weve-compromised-ci-cd-pipelines/).\n- Rob Bos (2022). [Setup an internal GitHub Actions Marketplace](https://devopsjournal.io/blog/2021/10/14/GitHub-Actions-Internal-Marketplace.html)\n\n\u003c/details\u003e\n\n## Part 4: Software Architecture\n\nPart 4 is about the correlation of your software architecture and the communication in your organization. You’ll learn how to transform your monolith gradually to a loosely coupled, event-based architecture.\n\n### Chapter 16: Loosely Coupled Architecture and Microservices\n\nIn this chapter I’ll give you an overview of loosely coupled systems and how you can evolve your software and system design to achieve a high engineering velocity.\nThe following topics will be covered in this chapter:\n- Loosely coupled systems\n- Microservices\n- Evolutionary design\n- Event-based architecture\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- Lewis J. \u0026 Fowler M. (2014). [Microservices](https://martinfowler.com/articles/microservices.html). \n- Eric Evans (2003). Domain-Driven Design: Tackling Complexity in the Heart of Software. Addison-Wesley Professional.\n- Martin Fowler (2004). [StranglerFigApplication](https://martinfowler.com/bliki/StranglerFigApplication.html). \n- Michael T. Nygard (2017). Release It!: Design and Deploy Production-Ready Software. Pragmatic Programmers\n- Martin Fowler (2005). [Event Sourcing](https://martinfowler.com/eaaDev/EventSourcing.html). \n- Lucas Krause (2015). Microservices: Patterns and Applications – Designing Fine-Grained Services By Applying Patterns [Kindle Edition].\n  \n\u003c/details\u003e\n\n### Chapter 17: Empower Your Teams\n\nThis chapter is about the correlation of the communication structure of your organization and your system architecture (Conway’s law) and how you can use this to improve architecture, organization structure, and software delivery performance. It covers the two-pizza team, the Inverse Conway Maneuver, and a mono- versus multi-repo strategy for your code.\nThe following are the core topics in this chapter:\n- Conway's law\n- The two-pizza team\n- Inverse Conway Maneuver\n- Delivery cadence\n- Mono- or multi-repo strategy\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n  \n- Conway, Melvin (1968). [How do committees invent](http://www.melconway.com/Home/pdf/committees.pdf). \n- Raymond, Eric S. (1996). The New Hacker's Dictionary [3rd ed.]. MIT Press.\n- Amazon (2020): [Introduction to DevOps on AWS - Two-Pizza Teams](https://docs.aws.amazon.com/whitepapers/latest/introduction-devops-aws/two-pizza-teams.html). \n- Willink, J. \u0026 Leif Babin, L. (2017). Extreme Ownership: How U.S. Navy SEALs Lead and Win. Macmillan.\n- Miller, G. A. (1956). [The magical number seven, plus or minus two: Some limits on our capacity for processing information](http://psychclassics.yorku.ca/Miller/). \n- Cohn M. (2009). Succeeding with Agile: Software Development Using Scrum. Addison-Wesley\n- QSM (2011). [Team Size Can Be the Key to a Successful Software Project](https://www.qsm.com/process_improvement_01.html). \n- Karau, S. J., \u0026 Williams, K. D. (1993). [Social loafing: A meta-analytic review and theoretical integration. Journal of Personality and Social Psychology, 65(4), 681–706](https://doi.org/10.1037/0022-3514.65.4.681). \n- Robbins S. (2005). Essentials of organizational behavior. Prentice Hall.\n- Steiner, I. D. (1972). Group process and productivity. Academic Press Inc.\n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- Skelton M., and Pais M. (2019). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution.\n- Reinertsen D. (2009). The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing.\n- Medina A. M. (2021). [Remote debugging on Kubernetes using VS Code](https://developers.redhat.com/articles/2021/12/13/remote-debugging-kubernetes-using-vs-code).\n  \n\u003c/details\u003e\n\n## Part 5: Lean Product Management\n\nIn Part 5 you’ll learn the importance of lean product management, how to integrate customer feedback into your flow of work, and how to combine hypothesis-driven development with OKR.\n\n### Chapter 18: Lean Product Development and Lean Startup\n\nThis chapter is about the importance of lean product management at a product and feature level. It shows how you can incorporate customer feedback into your product management, create Minimal Viable Products, and how you can manage your enterprise portfolio.\nThis chapter covers:\n- Lean product development\n- Incorporate customer feedback\n- The Minimal Viable Product\n- Enterprise portfolio management\n- Business Model Canvas\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- Ward, Allen (2007). Lean Product and Process Development. Lean Enterprise Institute, US\n- Ries, Eric (2011). The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses [Kindl Edition]. Currency\n- Humble J., Molesky J. \u0026 O’Reilly B. (2015). Lean Enterprise: How High Performance Organizations Innovate at Scale [Kindle Edition]. O'Reilly Media.\n- Osterwalder, Alexander (2004). [The Business Model Ontology: A Proposition In A Design Science Approach](http://www.hec.unil.ch/aosterwa/PhD/Osterwalder_PhD_BM_Ontology.pdf).\n- Goodwin, Kim (2009). Designing for the Digital Age - How to Create Human-Centered Products and Services. Wiley.\n  \n\u003c/details\u003e  \n\n### Chapter 19: Experimentation and A|B-Testing\n\nThis chapter explains how you can evolve and continuously improve your products by conducting experiments to validate hypotheses through evidence-based DevOps practices like A|B-testing. It also explains how you can leverage OKR to empower your teams to conduct the right experiments and to build the right products.\nThe following topics will be covered in this chapter:\n- Conducting experiments with the scientific method\n- Effective A|B testing with GrowthBook and Flagger\n- Experimentation and OKR\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- [The Scientific Method](https://en.wikipedia.org/wiki/Scientific_method)\n- [Ring-based Deployments](https://docs.microsoft.com/en-us/azure/devops/migrate/phase-rollout-with-rings)\n- [Optimizely](https://www.optimizely.com/)\n- [Hubspot](https://www.hubspot.com/)\n- [GrowthBook](https://github.com/growthbook/growthbook)\n- [Flagger](https://flagger.app/)\n- Stefan Prodan: [GitOps recipe for Progressive Delivery with Flux v2, Flagger and Istio](https://github.com/stefanprodan/gitops-istio)\n\n  \u003c/details\u003e  \n  \n ## Part 6:  GitHub for your Enterprise\n\nIn Part 6 you’ll learn about the different hosting and pricing options of GitHub, how you can migrate to GitHub from other platforms, and best practices for structuring your teams and products inside GitHub Enterprise.\n\n### Chapter 20: GitHub: The Home for All Developer\n\nThis chapter explains how GitHub can serve as the holistic, open platform for your teams. It explains the different hosting options, pricing, and how you can integrate it in your existing toolchain.\nThe key topics are:\n- Hosting options and pricing\n- GitHub Connect\n- Hands-on: create your account on GitHub.com\n- Enterprise Security\n- GitHub Learning Labs\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n  \n- [Pricing](https://github.com/pricing) \n- [GitHub AE](https://docs.github.com/en/github-ae@latest/admin/overview/about-github-ae)\n- [SCIM](https://docs.github.com/en/enterprise-cloud@latest/rest/reference/scim)\n- [Enterprise Managed Users](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)\n- [Audit logs](https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)\n- [GitHub Learning Lab](https://lab.github.com)\n- [Microsoft Learn](https://docs.microsoft.com/en-us/learn)\n\n\u003c/details\u003e  \n\n### Chapter 21: Migrating to GitHub\n\nIf you are not a start-up, then you always have existing tools and processes that must be considered when moving to a new platform. In this chapter, we will discuss different strategies related to migrating to GitHub from different platforms.\nIn this chapter, we will cover the following:\n- Picking the right migration strategy\n- Achieving compliance with low-fidelity migrations\n- Synchronizing requirements for a smooth transition\n- Migrating from Azure DevOps with the GitHub Enterprise Importer\n- Migrating pipelines using Valet\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n  \n- [GitHub Importer](https://docs.github.com/en/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer). \n- [GitHub Enterprise Importer CLI](https://github.com/github/gh-gei).\n- [GitHub Valet CLI](https://github.com/github/gh-valet).\n- [migrating with GitHub Enterprise Importer](https://docs.github.com/en/early-access/github/migrating-with-github-enterprise-importer). \n- [GitHub Enterprise Server Importer](https://docs.github.com/en/enterprise-server@3.4/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations)\n- [ghe-migrator](https://docs.github.com/en/enterprise-server@3.4/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations). \n- [Tasktop](https://www.tasktop.com/). \n- [git-svn](https://git-scm.com/docs/git-svn).\n- [git-tfs](https://github.com/git-tfs/git-tfs).\n\n\u003c/details\u003e \n  \n### Chapter 22: Organize Your Teams\n  \nIn this chapter you’ll learn best-practices to structure your repositories and teams into organizations and enterprises to foster collaboration and facilitate administration.\nThe chapter covers:\n- GitHub scopes and namespaces\n- Structuring GitHub teams\n- Role-based access\n- Custom roles\n- Outside Collaborators\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- [About teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams).\n- [Base permissions](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization). \n- [Custom roles](https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).\n- [Outside collaborators](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization). \n- [Managing access to your repository](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person).\n\n\u003c/details\u003e \n  \n### Chapter 23: Transform Your Enterprise\n\nThe last chapter puts all the pieces together. The book gives you a lot of tools that you can use to drive a successful transformation and to gain developer velocity. But only if all pieces are put together the transformation will succeed. The chapter will explain, why many transformations fail, and what you shoud do to make your transformation a success.\n\nWe will cover the following topics:\n- Why many transformations fail\n- Start with WHY\n- Data-driven transformation\n\n\u003cdetails\u003e\u003csummary\u003eReferences and Links\u003c/summary\u003e\n\n- Simon Sinek (2011), Start With Why – How Great Leaders Inspire Everyone to Take Action, Penguin\n- Simon Sinek (2019), The Infinite Game, Penguin\n- Nadella, S., Shaw, G. \u0026 Nichols, J. T. (2017), Hit Refresh: The Quest to Rediscover Microsoft's Soul and Imagine a Better Future for Everyone, Harper Business\n- Srivastava S., Trehan K., Wagle D. \u0026 Wang J. (April 2020). [Developer Velocity: How software excellence fuels business performance](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/developer-velocity-how-software-excellence-fuels-business-performance). \n- Forsgren N., Humble, J., \u0026 Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (1st ed.) [E-book]. IT Revolution Press.\n- John P. Kotter (2008), A Sense of Urgency, Harvard Business Review Press\n- John P. Kotter (2012), Leading Change, Harvard Business Review Press\n- Volkswagen (2019): [Volkswagen with New Corporate Mission Statement Environment \"goTOzero\"](https://www.volkswagenag.com/en/news/2019/07/goTOzero.html).\n- Mezedes-Benz Group Media (2019): [“Ambition2039”: Our path to sustainable mobility](https://group-media.mercedes-benz.com/marsMediaSite/ko/en/43348842).\n- [Theory of constraints](https://www.leanproduction.com/theory-of-constraints). \n- Small World (2016): [Theory of constraints – Drum-Buffer-Rope](https://www.smallworldsocial.com/theory-of-constraints-104-balance-flow-not-capacity/).\n- de Vries, M., \u0026 van Osnabrugge, R. (2022): [Together we build an Engineering Culture](https://xpirit.com/together-we-build-an-engineering-culture/). XPRT Magazine #12. \n\n\u003c/details\u003e \n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwulfland%2Facceleratedevops","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fwulfland%2Facceleratedevops","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwulfland%2Facceleratedevops/lists"}