The problem statement: at least 8 teams across department involved to deliver a new feature, with an average of 4-6 week. It becomes an issue when the senior management team has made a decision that they’re moving to cloud service. Should they do lift and shift, or should they adopt DevOps to revolutionise the way of working? Lift and shift seems to be a default option if the team has no idea; if you want DevOps, you have to know what’s your goal and fight hard. In our practise, senior management has played an important rule to get people agreed.

Top 5 priorities to be addressed along the DevOps journey:

1. Different goals;

2. Ownership: Access and Permissions;

3. Job security;

4. Organisation structure;

5. Compliance requirement.

As well as how to address these priorities; this is a long process and it could go back and forth, people needs to find their foot in the new world and they want to be valued.

At last, I am going to share the methodologies to measure the result for the project as well as the team to ensure it’s a sustainable process. The tool set includes: quantify the value for automation; devOps skill matrix.