Offboarding

Practice destroying and re-creating your applications
Contributed by

Patrick Carney

Johan Bonneau

Published September 09, 2019
Collection
2

What Is Offboarding?

Using Everything-as-Code by putting all infrastructure and configuration data into code, applications can be deployed in a repeatable and reliable fashion. Put it into action! Deploy code in one environment, and then re-deploy into another environment. Or destroy the first one and re-deploy :D

Why Do Offboarding?

To build resiliency and reliability for the automation of code deployment, thus resulting in less downtime and more throughput.

How to do Offboarding?

Practice on a cadence (1-3 weeks) in order to catch all the bugs! Keep repeating until all the bugs are caught! It gets easier each time, and everyone on the team should practice it for a shared understanding.

Look at Offboarding

Links we love

Check out these great links which can help you dive a little deeper into running the Offboarding practice with your team, customers or stakeholders.

Discuss with the Community


Open Practice Library Logo
Open Practice Library

powered by

Open Innovation Labs Logo
Connect with our Community:
Except where noted, content on this site is licensed under a Creative Commons Attribution 4.0 International license.