GCAPI. A DevOps transformation Story Pt. 1

…almost 1 year ago, when I first joined. I heard this:

“Hey, tell the other part of the team to check the PR”

Why is this sentence full of bad signs?

First of all, it clearly shows that we were not behaving as a team.
We were clearly not able to communicate transparently between us.
We were splitted in the tasks that we were doing, and we were not caring at all about what the “other part of the team” was doing.

This was known as the project that most DevOps broke/rotated. Why?

OK. This was happening:

Task	Besct Case Scenario	Worst Case Scenario
Create new Dev Environment	4 hours	5 days
Production deployments	4 features/ 2 weeks	5 days

And we turned that into:

Task	Besct Case Scenario	Worst Case Scenario
Create new Dev Environment	35 mins	1 hour
Production deployments	6 features every day	1 feature every day

Awesome. But how?

First. Why was this happening?

- Duplicated Scripts
- Gaps in communication
- Not well identified process

True stroy

We managed to improve a lot. Now we say things like:

This is the best team in the company I want to hep in other areas

and my personal favourite:

Nothing is breaking now

(Actually the last is not true because when nothing breaks, everyone is silent)