But, as you probably well know, many have failed in implementing DevOps and backed off from it. Based on our experience with over a hundred successful large-scale IT projects, dozens of which ran with DevOps, we dare to say that many expensive DevOps failures can be prevented just by taking care of some issues right from the start.

Before even considering implementing DevOps into large-scale IT projects, you need to understand what DevOps requires and what it can give at its best. Our recent blog post explains this in more detail. Shortly put: DevOps is neither a silver bullet for fixing traditional ways of working, nor a simple renaming of work titles or processes. It requires fundamental changes in how tens or hundreds of independent and autonomous teams work together towards the same goals.

Four issues you cannot bypass

Running a large-scale project is complex, no matter what framework you choose. To figure out if DevOps would be the appropriate way for you, take at least the following cornerstones into account.

1. Are you ready for DevOps?
   
   Typically, DevOps provides the most impressive results in the long term. Therefore, you need a shared understanding of goals, timeframe, level of ambition, and how much you are ready to invest before starting. You also should not forget your current competencies: to run DevOps full steam, cross-functional teams and automated platforms are required.

2. Do you have the competencies to implement DevOps?
   
   After the decision to implement DevOps, you need cross-functional teams with enough DevOps competence. Analyse your resources and the resources of your vendors. Evaluate and compare existing competencies to those desired. You may need to assign several team members to sufficiently cover such competence needs where experts are scarce. And at the end of the day, it is likely that you won’t find enough needed competency. But this does not mean you can’t proceed – read on to see why.

3. Does your management model drive continuous competence development?
   
   Instead of continuing to desperately seek people to fill your competency gaps, find people who can train and support others to fill the gaps. No matter how great a team you have, people will often need support in adopting the DevOps way of working in their daily work. In large-scale IT projects, the most efficient way to improve DevOps maturity has proven to be continuous competence development. Your management model needs to support this actively.

4. Are you progressing towards a true partnership?
   
   DevOps requires common goals, which all the parties involved are committed to. A culture of trust and collaboration is a must. Contracts should enhance partnership over confrontation. As we see, partnership-based, multi-vendor ecosystems will become more and more popular in the future. A new way to manage this kind of cooperation gently, yet firmly enough, is through collaborative governance.

DevOps is a model that requires us to renew in many ways. Learn more about our DevOps solutions and services.

Writers: Tomi Oinonen and Tapani Tirkkonen, experienced DevOps consultants and coaches, decided to sum up their experience from over a hundred large-scale IT projects to help business leaders get the most out of DevOps.