Accepting there is no end state
It is fair to expect that, at any point in time, there will be one or more improvements that teams want to make to their applications, toolchains, or way of working. To cope with this, it is recommended to not keep changing everything all of the time.
Instead, try to implement changes in batches or a series of well-defined steps. Also, note there is a natural order to things. It is impossible to practice continuous deployment (CD) without having a proper continuous integration (CI) process first. Also, adopting infrastructure as code (IaC) will deliver the most value when a CD process for application code is already in place. Next, automating governance and security measures works best when having infrastructure and configuration code is common practice. Once all of these practices have been implemented, new things will come up on the radar—future improvements that may be necessary.
Besides this series of improvements, it is also important...
