![]() |
| This article co-authored with Roel Hodzelmans |
More and more organisations are moving towards a DevOps based organisational model, putting more and more responsibility into the hands of the teams delivering software. As part of that change - and the need due to the markets moving faster and faster - more and more organisations are investing into means to release more milestones into production faster. Therefore one of the main goals within these organisations is to automate, audit, secure and ensure correct repeatability of actions.
To make that more concrete in our world of software development, we're now talking about how to implement processes that ensure our software is correct, verified, and authorized to be put into production for end customer usage. Delivering software requires that both developers and operations find common ways of merging their processes to enable faster delivery and smoother change management.
Let's look at defining and implementing the four-eyes principle in a DevOps automation process.






