Continuous Delivery Foundation cdCon 2022, 24 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Lightning Talk: Safe to Fail Continuous Delivery Culture - Sylvia Lobo, Digital14

Description

For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/

Lightning Talk: Safe to Fail Continuous Delivery Culture - Sylvia Lobo, Digital14
Virtual Track

Speakers: Sylvia Lobo
Building a new software product and deploying it in Cloud is a highly innovative and creative process. Things simply don't go to plan all the time, setbacks and failures are inevitable along the way. What makes a difference is how a team deals with them. Each failure is an opportunity to reassess, make a change and try a different approach. In order to succeed, testing teams must become resilient to failure. They must focus on the learning outcomes that they present.

A

Hello and welcome to the cdcon to the safe to fail and devops culture.

A

A little bit about me. I'm sylvia lubo, I'm a project manager with digital protein. You can hit me up on twitter and linkedin and thank you so much for giving me your precious time to hear about a field to save culture.

A

Typically, what we have noticed are the visceral reaction to failure. Is you will be ashamed? You will not be given the unsafety net in order to go ahead and do your experiments or you will have to hide or dump it on another or unsuspecting colleague or teammate.

A

But I would definitely like to ask you all: is it okay to fail?

A

When I was working as a devops engineer, I was dismayed when I disclosed to the team that I had failed as a result of that failure to deploy a jenkins cicd pipeline to the production environment, I was delegated to more junior rules. It was humiliating, but that failure taught me to experiment.

A

It taught me that it was okay to fail.

A

I strongly believe that if you do not fail, you do not grow.

A

I would definitely like to ask everyone here to pause for a moment and think should failures be welcomed, because the person for failure did not have einstein inventing the light bulb.

A

A few suggestions pointers that you can use to embrace failure. One of the easiest way that I have noticed is prototyping.

A

It gives you a fair idea of what you're going to build, and it also sets up the expectation from the team that this is a prototype. Another one would be to build a concept pinata. So, for example, if we have to deploy two of communities, um how do we do that hey?

A

This is what I think I built this in my spare time, and this is what I possibly presume would happen.

A

So you are experimenting and also learning. Another favorite is to have a demolition derby.

A

What if we take away what we have built, which is not working and then try to look at the bits in a different way, so that we can experiment and learn at the same time, a better version always sets you in a fail-safe environment. This is very important for folks who want to learn who want to grow.

A

A risk register is definitely not a viable for those who have failed or a notebook for those who have not been successful with their projects.

A

For instance, when I was experimenting with microsoft, azure for building the ci cd pipelines me, including the other teammates, had no clue of what to expect or how to go about it, but each one of us came with a positive growth mindset and that, and that alone helped me to build and deploy to microsoft, azure choosing the ci cd pipelines out of the box with azure.

A

Yes, I know it. Devops is fast and easy, but what I would really recommend is to use the fast approach acronym as frame it, accept it, seek it and think how you can make better out of it.

A

Of course, like all organizations, we cannot burn money on experiments that fail, but if you do not experiment, it will be difficult to go ahead and do anything of value.

A

I would rather put this safe culture as a strategic, accountable, flexible and expectation free environment where people are free to build and break and learn and grow. That's when you bring the best version of yourself to work, I'm pretty sure you all have questions for me.

A

I will be more than happy to take any questions you have now or maybe later. Thank you.