5 principles to becoming a collaborative agile devops team

Agile and devops are not just practices and technologies—they are designed to change how people in IT work together

Become An Insider

Sign up now and get FREE access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content. Learn more.

There’s a lot of work IT teams take on when committing to agile and devops practices. Agile teams are likely to mature and scale their practice by defining the scrum master roles, adding estimating practices, and maturing how they use agile management tools. Devops teams might start by implementing CI/CD pipelines, then implement automate testing, and then look to add more informative application-level monitoring and alerts.

You might hear a lot about the culture and mindset of IT organizations around agile and devops. If you’ve been around IT long enough then you’ve probably witnessed the struggle between development teams that want to release quickly and IT operations that wants to control changes so that infrastructure and applications run reliably. Agile and devops are not just practices and technologies—they are designed to change how people in IT work together.

As your IT organization is embarking on agile and devops transformations, how do you know that people are truly collaborating? How should teams behave differently and what should you be doing to advance the collaboration, culture and mindset of teams?

Here are five principles that will help guide this collaborative and culture transformation.

1. Collaborative teams solve the right problems good enough

Have you ever witnessed teams so focused on a technical solution that they lose site of what problem they are solving and why? Or how about when a problem is being worked on and there are key people left out of the conversation? What happens when teams overthink a technical problem and define a solution that’s overengineered or too complex to implement?

To continue reading this article register now