Avoid three silos
By Tomas Filip on October 28, 2020 in the DevOps
It can be quite tricky and it can happen very quickly that you create a third DevOps silo between Development & Operations.
Do NOT name a team “DevOps team”
Calling your team as “DevOps team” will lead people to associate the DevOps philosophy with a specific role. Do you want to start doing automation? Do you want to start making changes in general?
...and don‘t hire people for “DevOps” job. Don't let your people associate the DevOps philosophy with a specific role in your company.
It's just latest team or job title sparkling buzzword. You need to define your expectations.
Raise a few DevOps questions first
Do you want to start doing automation?
Hire automation engineer with DevOps mindset
Do you want to start making changes in general?
Hire specific roles with DevOps mindset
By Tomas Filip on October 26, 2020 in the DevOps
Related posts to DevOps
“DevOps” is NOT a job title
By Tomas Filip on October 06, 2020 in the DevOps
... and DevOps is NOT even a methodology. It’s a philosophy, it’s a state of mind. When you are looking for “DevOps”, what exactly you want want to find? What do you want to achieve? A lot of processes are manual and it is necessary to automate? Or do you need some cultural change in general?
DevOps is NOT just about automation
By Tomas Filip on September 27, 2020 in the DevOps
Do you think you are DevOps when you have some automation? DevOps is NOT just about automation, scripts or pipelines... it's not something you can start overnight or by hiring one DevOps person.