Some DevOps thought leaders have been promoting “NoOps,” which is the notion that IT resources can be provisioned in a fully automated way that does not require operations engineers to manage. There have been notable successes with this approach, but also some challenges. Can you have too much automation?

Quality has increasingly become a responsibility for not just one single segment of the team, but the team as a whole. It’s important for each member of a team to have some hand in making sure that what’s being developed works as intended as it goes through each individual progression.

The DevOps movement accelerates the delivery of high-quality features to customers. While that's great, there is a ton of work required to make it happen, with a high change curve to overcome—and perhaps the most critical change is to the way the developer works. Here's why this disruption is necessary.