<img height="1" width="1" style="display:none" src="https://alb.reddit.com/snoo.gif?q=CAAHAAABAAoACQAAACi3UkU6AA==&amp;s=hMfJ_f7PVQOiL2csDznj0MZz_-_Sym2oeAYASWsHW4c=">

Kalle Sirkesalo

Kalle_Sirkesalo

Kalle Sirkesalo

Eficode ROOT

Kalle Sirkesalo is the Platform Director at Eficode. With his strong track record in IT and DevOps, he has helped many small and large companies to build, automate, and scale their DevOps environments. Kalle describes himself as a fast learner workaholic, driven by self-improvement.

Session: There’s no nice way to say this: Your DevOps has gone horribly wrong

On a regular basis, my co-workers and I get called into a customer meeting to discuss their DevOps problems and trying to find solutions. Have you ever been in a meeting an known exactly the solution, but also known that saying it out loud will lead you to get kicked out of the room? Well, this is a story of DevOps being misused to the point that it ended up shooting the team in the foot. The team had a test environment and continuous deployment capability but this was precisely what was making the problem ever more serious in this case. The issue was velocity or rather, a lack of velocity.

The team had decided it was their test cases and the solutions they were coding, so that’s what we were there too evaluate. I started the discussion by asking them to explain how they develop a feature. After hearing this, I realized that the only option for stability would be to throw away all the code that is not in master and to inform the business that all of the code that is not in production should now be seen as obsolete and that they can let go 2 of the 3 teams for few months.

Join me in this talk to hear what the situation was we were confronted with, what factors led to it, and where we ended up in the end. You might also like to hear how we tried to explain this to a team that did not understand the depth of the problem they had. There was no nice way to say it. Or maybe there was.