DevOps is primarily about changing the culture to accelerate innovation and business success
DevOps is not necessarily new, many organizations have already done DevOps for more than 4 years, but it is only now about to reach mainstream adoption
Increased agility
Faster deployments
Improved customer experience
Increase in revenue/profits
IDC MaturityScape: DevOps — Progressing Through the Stages
Stage
Guidance
Ad hoc
Determine core values of IT's culture across areas such as measurement, collaboration, empathy, risk taking, teamwork, sharing, communication, and trust.
Evaluate leadership and staff skill sets to determine whom might be able to lead DevOps integrated teams and fill roles.
Identify key business stakeholders that will support DevOps teams and projects.
Document existing cost structure (and models) for delivery of key applications across the developer, test, and operations teams.
Map and document processes, reduce fragmentation, and start to standardize workflows.
Opportunistic
Standardize processes and start to work in unified DevOps teams to identify a common language for automated processes and tasks.
Identify existing legacy tools in use across silos; plan for automation heavily in areas such as testing, release, deployment, monitoring, and security.
Define the customer, business, technology, and staffing metrics that will drive DevOps projects and define success.
Automate configuration and change management processes; target development and operations teams via collaborative discussions.
Repeatable
Use automation tools for DevOps projects; create a jointly developed road map between development and operations teams
Identify areas of process integration; map value streams.
Create unified DevOps teams, with shared responsibilities, goals, and objectives.
Develop visualization techniques and dashboards to drive communications and measure progress with metrics.
Create automated development and deployment processes that use self-service portals created by operations teams.
Managed
Collect and integrate INFOSEC input into product design and development.
Collect customer insights and use it to impact product quality and features.
Use data from monitoring tools, such as APM suites and logging tools, to inform business decisions.
Create a center of enablement for DevOps to drive projects, budget allocations, standard operating model, and communicate successes.
Create integrated automated processes between development and operations teams; document a singular automation strategy.
Optimized
Change cultural values that stress teamwork, trust, empathy, and an acceptance of failure.
Focus on sustainable competitive advantage.
Have INFOSEC teams that makes consumable, pre-approved libraries and tools available for use by DevOps teams.
Develop customer feedback mechanisms across the SDLC to drive innovative new product development.
Create "automate everything" policies as the standard operating model for development and operations.
IDC MaturityScape: DevOps — Progressing Through the Stages
Stage
Guidance
Ad hoc
Determine core values of IT's culture across areas such as measurement, collaboration, empathy, risk taking, teamwork, sharing, communication, and trust.
Evaluate leadership and staff skill sets to determine whom might be able to lead DevOps integrated teams and fill roles.
Identify key business stakeholders that will support DevOps teams and projects.
Document existing cost structure (and models) for delivery of key applications across the developer, test, and operations teams.
Map and document processes, reduce fragmentation, and start to standardize workflows.
Opportunistic
Standardize processes and start to work in unified DevOps teams to identify a common language for automated processes and tasks.
Identify existing legacy tools in use across silos; plan for automation heavily in areas such as testing, release, deployment, monitoring, and security.
Define the customer, business, technology, and staffing metrics that will drive DevOps projects and define success.
Automate configuration and change management processes; target development and operations teams via collaborative discussions.
Repeatable
Use automation tools for DevOps projects; create a jointly developed road map between development and operations teams
Identify areas of process integration; map value streams.
Create unified DevOps teams, with shared responsibilities, goals, and objectives.
Develop visualization techniques and dashboards to drive communications and measure progress with metrics.
Create automated development and deployment processes that use self-service portals created by operations teams.
Managed
Collect and integrate INFOSEC input into product design and development.
Collect customer insights and use it to impact product quality and features.
Use data from monitoring tools, such as APM suites and logging tools, to inform business decisions.
Create a center of enablement for DevOps to drive projects, budget allocations, standard operating model, and communicate successes.
Create integrated automated processes between development and operations teams; document a singular automation strategy.
Optimized
Change cultural values that stress teamwork, trust, empathy, and an acceptance of failure.
Focus on sustainable competitive advantage.
Have INFOSEC teams that makes consumable, pre-approved libraries and tools available for use by DevOps teams.
Develop customer feedback mechanisms across the SDLC to drive innovative new product development.
Create "automate everything" policies as the standard operating model for development and operations.