Traditionally, development and operations are working towards different—and often contradictory—goals. Developers want creative freedom and the ability to innovate. They are generally under pressure to put out new code quickly to keep up with the fast pace of modern business. Operations wants to run that code in a way that is safe, accurate, and under control. Avoiding bugs and downtime can be difficult when deployments are happening quickly.
Both teams are right, and both teams are wrong.
Collaboration is to come together as a single team to address any problem in the program, which hinders the program goalkeeping customer focus in mind and solve them by owning them as their own problem as quickly as possible, without any blame game.
Collaboration teaches everyone to talk to each other, meet each other face to face, involve each other in their meetings, discussions, understand each other’s tasks, dependency and have transparency in work and work proactively to prevent the problems.
In our last tutorial we learned about Collaboration in DevOps, now will see how to develop Collaboration in DevOps.
Certain practices of DevOps facilitates the team to develop the mindset of collaboration amongst the team.
Version control – a single tool for the team, brings transparency.
Automation – learn from each other, be independent, common goal and thinking in the team.
Inducing a production mindset.
Monitoring performance in the life together.
