Earlier this week we announced our #CompleteDevOps vision. Let's take a closer look at what that means, and how it's different from traditional DevOps.
Traditional vs. Complete DevOps
In the early days of software development the process of taking an idea to production was slow, insecure and vulnerable to errors. DevOps emerged as a way to foster collaboration and create faster iteration cycles with greater quality and security. As it sits today, DevOps is a set of practices at the intersection of development and operations. It was a huge step forward.
But it didn't go far enough.
Even with the adoption of DevOps, serious challenges continue to exist. Developers and operators used to be separate groups with separate tools. The people are now closer together but their tools are still apart. This hinders dev and ops teams from working together. Trying to glue their tools together with traditional DevOps applications doesn't solve the fundamental problem of having separate applications.
Why Complete DevOps?
Complete DevOps reimagines the scope of tooling to include both developers and operations teams in one unified solution. This dramatically reduces friction, increases collaboration, and drives a competitive advantage. Doing away with context switching and having all the necessary information in one place closes the loop and enables a better understanding of each team's needs.
To make our vision a reality, we're working on a number of new features and improving on existing ones. You can take an in-depth at some of these in our Head of Product Mark Pundsack's outline here, or watch the full presentation about our Complete DevOps vision below.
You can also browse the slides at your leisure:
Share your thoughts, comments, and questions about #CompleteDevOps with us on Twitter!