This document provides 10 tips for taking control of software delivery through DevOps practices before it is too late. The tips include over-communicating your DevOps plan, defining the pace of your applications, killing dependencies at all costs, not creating new "legacy" applications, and setting a high bar for new initiatives. An example project is used to illustrate how good DevOps intentions can deteriorate over time due to project pressures. Ensuring your methodology encourages DevOps is emphasized to avoid creating new legacy applications.
The world of IT is shifting rapidly towards DevOps with analysts predicting the majority of companies will adopt DevOps practices in the next few years. In fact, in a recent study on DevOps by International Data Corp. (IDC), they believe that DevOps will be adopted (in either practice or discipline) by 80% of Global 1000 organizations by 2019!
Forming a DevOps team seems like a natural step, but the idea of creating a dedicated DevOps team has ignited anger in the community. Why? What's the concern? Is a DevOps team evil? Completely necessary? A necessary Evil?
Join IBM UrbanCode's Eric Minick to learn the pitfalls of creating bad DevOps teams, and successful approaches of good ones. Along the way, we’ll explore other heresies such as using tools to change culture.
Evolution of the DevOps Quality Management OfficeCapgemini
This document discusses the evolution of the DevOps Quality Management Office (QMO). It outlines the vision of continuous business-driven testing to reduce the time between development and operations. Key aspects of the DevOps-driven testing approach include continuous integration and delivery, lean techniques, standardization, test optimization, and establishing a hybrid test organization. The document also compares traditional vs DevOps testing approaches and provides examples of DevOps testing success levers. It proposes that the QMO can advise on developing a DevOps strategy and roadmap to improve throughput, availability, and time to market.
This document discusses DevOps concepts including the teams involved in DevOps (development, build/release, QA, application, and OS teams), DevOps processes like continuous integration, continuous delivery, and continuous deployment, and DevOps tools. It defines DevOps as a culture and set of practices that promote collaboration between development and operations teams.
from 0 to continuous delivery in 30 minutesAgileSparks
In this session we will explore the full continuous delivery cycle from check-in to production using set of popular tools. During the session the attendees will be introduced to a set of tools and practices that enable continuous delivery from the technical point of view.
DevOps is a practice that promotes collaboration between development and operations teams. It aims to allow for faster delivery of features and fixes through closer collaboration and automation of processes. Benefits of DevOps include faster time to market, increased availability, higher deploy rates, and better collaboration among teams. Traditionally, development and operations teams worked in silos with handoffs of work and a lack of communication, which led to delays and issues. DevOps aims to break down these silos through practices like automation, continuous integration and deployment, and shared goals.
DevOps – the future of Agile – why, what, how? Agile Israel 2014Yuval Yeret
DevOps is the new favorite buzzword in many organizations. We will understand what it is all about, why it is necessary and what makes it so popular, how it is related to Agile, some pitfalls/myths, and most importantly some concrete steps organizations can take to become a more DevOps-oriented organization and enjoy benefits like more frequent less painful software deployments and operation and better collaboration between Dev and Ops organizations.
http://agileisrael2014.com/devops-the-future-of-agile/
This document provides guidance on transitioning an organization to a DevOps model. It discusses how organizational structures can impact technical designs based on Conway's Law. It then covers common anti-patterns when shifting to DevOps like relying on a single consultant. The document proposes using a logical rather than structural view of the organization and modeling it after Spotify's Guild model. It offers tips for facilitating collaboration between teams and overcoming challenges to change. Finally, it addresses technical transition topics like security as code and environment consistency. The overall message is that organizational change requires clear communication, addressing business needs, facilitating cross-team work, and setting ambitious yet achievable goals.
The world of IT is shifting rapidly towards DevOps with analysts predicting the majority of companies will adopt DevOps practices in the next few years. In fact, in a recent study on DevOps by International Data Corp. (IDC), they believe that DevOps will be adopted (in either practice or discipline) by 80% of Global 1000 organizations by 2019!
Forming a DevOps team seems like a natural step, but the idea of creating a dedicated DevOps team has ignited anger in the community. Why? What's the concern? Is a DevOps team evil? Completely necessary? A necessary Evil?
Join IBM UrbanCode's Eric Minick to learn the pitfalls of creating bad DevOps teams, and successful approaches of good ones. Along the way, we’ll explore other heresies such as using tools to change culture.
Evolution of the DevOps Quality Management OfficeCapgemini
This document discusses the evolution of the DevOps Quality Management Office (QMO). It outlines the vision of continuous business-driven testing to reduce the time between development and operations. Key aspects of the DevOps-driven testing approach include continuous integration and delivery, lean techniques, standardization, test optimization, and establishing a hybrid test organization. The document also compares traditional vs DevOps testing approaches and provides examples of DevOps testing success levers. It proposes that the QMO can advise on developing a DevOps strategy and roadmap to improve throughput, availability, and time to market.
This document discusses DevOps concepts including the teams involved in DevOps (development, build/release, QA, application, and OS teams), DevOps processes like continuous integration, continuous delivery, and continuous deployment, and DevOps tools. It defines DevOps as a culture and set of practices that promote collaboration between development and operations teams.
from 0 to continuous delivery in 30 minutesAgileSparks
In this session we will explore the full continuous delivery cycle from check-in to production using set of popular tools. During the session the attendees will be introduced to a set of tools and practices that enable continuous delivery from the technical point of view.
DevOps is a practice that promotes collaboration between development and operations teams. It aims to allow for faster delivery of features and fixes through closer collaboration and automation of processes. Benefits of DevOps include faster time to market, increased availability, higher deploy rates, and better collaboration among teams. Traditionally, development and operations teams worked in silos with handoffs of work and a lack of communication, which led to delays and issues. DevOps aims to break down these silos through practices like automation, continuous integration and deployment, and shared goals.
DevOps – the future of Agile – why, what, how? Agile Israel 2014Yuval Yeret
DevOps is the new favorite buzzword in many organizations. We will understand what it is all about, why it is necessary and what makes it so popular, how it is related to Agile, some pitfalls/myths, and most importantly some concrete steps organizations can take to become a more DevOps-oriented organization and enjoy benefits like more frequent less painful software deployments and operation and better collaboration between Dev and Ops organizations.
http://agileisrael2014.com/devops-the-future-of-agile/
This document provides guidance on transitioning an organization to a DevOps model. It discusses how organizational structures can impact technical designs based on Conway's Law. It then covers common anti-patterns when shifting to DevOps like relying on a single consultant. The document proposes using a logical rather than structural view of the organization and modeling it after Spotify's Guild model. It offers tips for facilitating collaboration between teams and overcoming challenges to change. Finally, it addresses technical transition topics like security as code and environment consistency. The overall message is that organizational change requires clear communication, addressing business needs, facilitating cross-team work, and setting ambitious yet achievable goals.
What does a Maturity Curve for Enterprise Adoption of Agile and DevOps look like? Where would an organization like yours rank on the curve? Are there specific areas of improvement you might want to consider?
DOES15 - Sherry Chang - Intel’s Journey to Large Scale DevOps Transformation Gene Kim
Sherry Chang, Enterprise Architect, Intel
Is it possible to transform large enterprises with 100’s of in-flight projects across myriad technology stacks and entrenched processes, requiring massive workforce re-skilling? In this session, I’ll share approaches we employed to increase the likelihood of success through DevOps adoption by:
-Offering of a common Continuous Delivery Service, similar to industry offerings from Codeship.io, CloudBees, and others
-Establishing a Maturity Model to help teams incrementally adopt DevOps practices
-Coaching teams through Kaizen sessions to eliminate bottlenecks and waste in their value stream
What are the Cool Kids Doing With Continuous Delivery?CA Technologies
Building a solid application delivery tool chain is no easy task. The popularity of infrastructure configuration management tools like Puppet, Chef, Salt and others are a direct result of the explosion of virtual machines needing to be maintained, configured and provisioned. Learn how you can leverage these trends and combine infrastructure configuration and release automation to build an enterprise class continuous delivery solution for your business.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
From the the teams struggling with DevOps to experienced professionals trying to make a shift to DevOps, this presentation helps in how understanding how DevOps makes Deliveries faster and accurate
A high level introduction to DevOps. Explains what it is, how popular DevOps has become, why DevOps is popular, how DevOps differs from traditional approaches and some next steps to implementation.
DevOps adoption can be bottom-up or top-down, but requires buy-in from management and alignment with business goals. The document describes strategies for implementing DevOps practices aligned to business objectives, including focusing on culture, automation, measurement, and sharing. DevOps stresses communication and collaboration between software developers and IT operations to accelerate delivery of quality software through practices like continuous integration, delivery, and deployment.
Jonny wooldridge DevOps Large and SmallJwooldridge
This document provides details about the speaker's experience leading a large DevOps transformation project at Marks & Spencer, a large UK retailer. Some key points:
- He introduced practices like continuous integration, DevOps, and behavior driven development to a 650-person project team working on a £150 million project.
- Among the successes were establishing a software factory for efficient code management and regular release trains. Challenges included integrating legacy systems and complex test environments.
- The document discusses where teams fall on a scale from "Legacy Zone" to "Cool Zone" based on their agile practices and independently deployable software. Moving more teams to continuous delivery is an ongoing effort.
This document discusses DevOps from the perspective of Erno Aapa, a DevOps consultant. It outlines some common misunderstandings about DevOps, such as thinking it is a role or team. The document then discusses the history of approaches like Agile, Scrum, and Continuous Integration that influenced DevOps. It explains how DevOps gives companies the capability to experiment and deploy changes rapidly and safely. The benefits of DevOps include faster deployments, improved collaboration between Dev and Ops teams, and the ability to get feedback from customers to continuously improve.
DevOps by the Numbers - How to Approach the Measurement and Metrics of Your C...XebiaLabs
There’s no mistaking how important initiatives like DevOps and Continuous Delivery have become to organizations seeking to gain a competitive edge. But without the right metrics, enterprises that have adopted DevOps or Continuous Delivery strategies have no way of measuring their effectiveness in the context of their digital transformation goals. So what are the right measures that can answer questions like “are we getting better at delivering high-quality software faster and at scale?” and “has all this effort been worth it?!”
Learn ways to better measure the processes and output of your DevOps and Continuous Delivery transformation.
You'll also learn:
How to identify the best metrics for various stakeholders in your software development lifecycle
How to measure and demonstrate the business value and effectiveness of DevOps and Continuous Delivery processes and programs
How to address some of the challenges along your process that these metrics and KPI's may reveal
HP Discover Session BB2160: Agile DevOps Continuous DeliveryCapgemini
This document discusses how businesses need faster time-to-market and time-to-value for new functionality. It outlines challenges with traditional waterfall development approaches and notes that Agile development helps but that releasing software still takes too long. HP Software solutions for continuous delivery, DevOps, and automation are presented to help bridge the gaps between development and operations for faster software releases while maintaining quality. These include solutions for lab management, application release acceleration, and enterprise collaboration.
This document provides an overview of agile software development. It discusses the problems traditional software development methods can cause and how agile development aims to address these issues through iterative development and frequent delivery of working software. Key aspects of agile like Scrum, its roles, events and principles are explained. The advantages of agile are noted as well as some potential disadvantages.
This document provides information about a presentation titled "Integrating Automated Testing into DevOps" given by Jeff Payne of Coveros, Inc. It includes biographical information about Jeff Payne, an agenda for the presentation, and content that will be covered, including definitions of DevOps, common DevOps terminology, automated testing for continuous integration and continuous delivery, environments for testing, common tools used, and demos of automated testing.
DOES16 London - Darren Hague - SAP’s DevOps Journey: From Building an App to ...Gene Kim
Darren Hague, Cloud Infrastructure Architect, SAP
SAP has been using a DevOps & Continuous Delivery approach for building its web and mobile apps for several years, and is now building and running a global cloud at the scale needed to support the digital transformation needs of its customers. This talk recaps the story of how SAP originally adopted DevOps practices before moving on to describe how the Cloud Infrastructure Services team is building and operating its 3rd generation cloud automation system using microservices, containers and open-source software.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
Enterprise Devops Presentation @ Magentys Seminar London May 15 2014Jwooldridge
Thanks to Liam and the crew from Magentys for arranging a fantastic evening of presentations on all things DevOps.
Attached is my presentation from the event on Enterprise Devops.
For those of you who missed it:
“Join the crowd of 100 industry leaders across the Retail, Finance and Digital sectors for an exciting evening of talks in London’s Tech City on DevOps. Enjoy networking with a chilled beer alongside the experts who are making DevOps work and those who want to make it work.
Whether you’re a corporate or start-up, DevOps should be a hot topic so listen to how the experts are achieving great things, hear their views on the trends and discuss the future of DevOps.”
Jonny
enterprisedevops.com
Developing a Testing Strategy for DevOps SuccessDevOps.com
To achieve rapid time-to-market, businesses have embraced DevOps, which places a premium on speed and efficiency. But speed is not the only measure of DevOps success. To release better software faster, enterprises must optimize testing strategy and embed a culture of quality within their DevOps processes.
In this webinar, you will learn:
How to transform QA from a bottleneck to a speed enabler
How to integrate quality and increase visibility throughout the SDLC
How to help your VPs and Directors gauge the success of their current quality initiatives
This document provides an introduction to DevOps fundamentals and principles. It discusses how DevOps aims to improve collaboration between development and operations teams. It notes that DevOps was being adopted more by development teams initially. It also highlights some of the business costs of bugs and issues in production environments, and how DevOps can help improve efficiency, reduce costs, and accelerate business agility.
For a beginner, this is a good quality pictorial representation of DevOps and DevOps Center of Excellence.
Opex Software focuses on consulting, implementation and development of DevOps tools and platforms. Have helped small and large data centers! This presentation talks about Continuous Integration, Continuous Delivery at a high level. For detailed presentations and flows, please ping us.
Thanks again, Enjoy!
There are many resources out there that walk you through the process of setting up distributed systems, queuing and asynchronous processes — with and without NServiceBus.
Despite all the online education, teams continue to make the same common mistakes when designing and implementing microservices architecture. While the mistakes can have devastating consequences, they are easy to avoid when approached intentionally.
Jeffrey Palermo and Justin Self share their experiences in overcoming common microservices pitfalls and show how NServiceBus naturally encourages better architecture, such as easy adherence to SOLID principles.
Learn:
* What a microservice really is (and is not)
* What mistakes teams commonly make
* How to avoid the pitfalls and design more robust and scalable architecture
* How to equip your team for a microservices architecture
The document discusses the opportunity and challenges of adopting DevOps practices in an enterprise setting. While DevOps can provide benefits like faster delivery, increased quality, and agility, transformation is difficult for enterprises due to technical, governance, cultural, organizational, and process-related reasons. These include legacy systems, silos between teams, lack of automation, and risk management concerns. The document argues that DevOps adoption is necessary for enterprises to thrive in today's software-focused market, and that the transformation requires changes across organizational culture, processes, and technology. It provides examples of tools that can help, such as automation, self-service capabilities, and microservices architecture.
What does a Maturity Curve for Enterprise Adoption of Agile and DevOps look like? Where would an organization like yours rank on the curve? Are there specific areas of improvement you might want to consider?
DOES15 - Sherry Chang - Intel’s Journey to Large Scale DevOps Transformation Gene Kim
Sherry Chang, Enterprise Architect, Intel
Is it possible to transform large enterprises with 100’s of in-flight projects across myriad technology stacks and entrenched processes, requiring massive workforce re-skilling? In this session, I’ll share approaches we employed to increase the likelihood of success through DevOps adoption by:
-Offering of a common Continuous Delivery Service, similar to industry offerings from Codeship.io, CloudBees, and others
-Establishing a Maturity Model to help teams incrementally adopt DevOps practices
-Coaching teams through Kaizen sessions to eliminate bottlenecks and waste in their value stream
What are the Cool Kids Doing With Continuous Delivery?CA Technologies
Building a solid application delivery tool chain is no easy task. The popularity of infrastructure configuration management tools like Puppet, Chef, Salt and others are a direct result of the explosion of virtual machines needing to be maintained, configured and provisioned. Learn how you can leverage these trends and combine infrastructure configuration and release automation to build an enterprise class continuous delivery solution for your business.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
From the the teams struggling with DevOps to experienced professionals trying to make a shift to DevOps, this presentation helps in how understanding how DevOps makes Deliveries faster and accurate
A high level introduction to DevOps. Explains what it is, how popular DevOps has become, why DevOps is popular, how DevOps differs from traditional approaches and some next steps to implementation.
DevOps adoption can be bottom-up or top-down, but requires buy-in from management and alignment with business goals. The document describes strategies for implementing DevOps practices aligned to business objectives, including focusing on culture, automation, measurement, and sharing. DevOps stresses communication and collaboration between software developers and IT operations to accelerate delivery of quality software through practices like continuous integration, delivery, and deployment.
Jonny wooldridge DevOps Large and SmallJwooldridge
This document provides details about the speaker's experience leading a large DevOps transformation project at Marks & Spencer, a large UK retailer. Some key points:
- He introduced practices like continuous integration, DevOps, and behavior driven development to a 650-person project team working on a £150 million project.
- Among the successes were establishing a software factory for efficient code management and regular release trains. Challenges included integrating legacy systems and complex test environments.
- The document discusses where teams fall on a scale from "Legacy Zone" to "Cool Zone" based on their agile practices and independently deployable software. Moving more teams to continuous delivery is an ongoing effort.
This document discusses DevOps from the perspective of Erno Aapa, a DevOps consultant. It outlines some common misunderstandings about DevOps, such as thinking it is a role or team. The document then discusses the history of approaches like Agile, Scrum, and Continuous Integration that influenced DevOps. It explains how DevOps gives companies the capability to experiment and deploy changes rapidly and safely. The benefits of DevOps include faster deployments, improved collaboration between Dev and Ops teams, and the ability to get feedback from customers to continuously improve.
DevOps by the Numbers - How to Approach the Measurement and Metrics of Your C...XebiaLabs
There’s no mistaking how important initiatives like DevOps and Continuous Delivery have become to organizations seeking to gain a competitive edge. But without the right metrics, enterprises that have adopted DevOps or Continuous Delivery strategies have no way of measuring their effectiveness in the context of their digital transformation goals. So what are the right measures that can answer questions like “are we getting better at delivering high-quality software faster and at scale?” and “has all this effort been worth it?!”
Learn ways to better measure the processes and output of your DevOps and Continuous Delivery transformation.
You'll also learn:
How to identify the best metrics for various stakeholders in your software development lifecycle
How to measure and demonstrate the business value and effectiveness of DevOps and Continuous Delivery processes and programs
How to address some of the challenges along your process that these metrics and KPI's may reveal
HP Discover Session BB2160: Agile DevOps Continuous DeliveryCapgemini
This document discusses how businesses need faster time-to-market and time-to-value for new functionality. It outlines challenges with traditional waterfall development approaches and notes that Agile development helps but that releasing software still takes too long. HP Software solutions for continuous delivery, DevOps, and automation are presented to help bridge the gaps between development and operations for faster software releases while maintaining quality. These include solutions for lab management, application release acceleration, and enterprise collaboration.
This document provides an overview of agile software development. It discusses the problems traditional software development methods can cause and how agile development aims to address these issues through iterative development and frequent delivery of working software. Key aspects of agile like Scrum, its roles, events and principles are explained. The advantages of agile are noted as well as some potential disadvantages.
This document provides information about a presentation titled "Integrating Automated Testing into DevOps" given by Jeff Payne of Coveros, Inc. It includes biographical information about Jeff Payne, an agenda for the presentation, and content that will be covered, including definitions of DevOps, common DevOps terminology, automated testing for continuous integration and continuous delivery, environments for testing, common tools used, and demos of automated testing.
DOES16 London - Darren Hague - SAP’s DevOps Journey: From Building an App to ...Gene Kim
Darren Hague, Cloud Infrastructure Architect, SAP
SAP has been using a DevOps & Continuous Delivery approach for building its web and mobile apps for several years, and is now building and running a global cloud at the scale needed to support the digital transformation needs of its customers. This talk recaps the story of how SAP originally adopted DevOps practices before moving on to describe how the Cloud Infrastructure Services team is building and operating its 3rd generation cloud automation system using microservices, containers and open-source software.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
Enterprise Devops Presentation @ Magentys Seminar London May 15 2014Jwooldridge
Thanks to Liam and the crew from Magentys for arranging a fantastic evening of presentations on all things DevOps.
Attached is my presentation from the event on Enterprise Devops.
For those of you who missed it:
“Join the crowd of 100 industry leaders across the Retail, Finance and Digital sectors for an exciting evening of talks in London’s Tech City on DevOps. Enjoy networking with a chilled beer alongside the experts who are making DevOps work and those who want to make it work.
Whether you’re a corporate or start-up, DevOps should be a hot topic so listen to how the experts are achieving great things, hear their views on the trends and discuss the future of DevOps.”
Jonny
enterprisedevops.com
Developing a Testing Strategy for DevOps SuccessDevOps.com
To achieve rapid time-to-market, businesses have embraced DevOps, which places a premium on speed and efficiency. But speed is not the only measure of DevOps success. To release better software faster, enterprises must optimize testing strategy and embed a culture of quality within their DevOps processes.
In this webinar, you will learn:
How to transform QA from a bottleneck to a speed enabler
How to integrate quality and increase visibility throughout the SDLC
How to help your VPs and Directors gauge the success of their current quality initiatives
This document provides an introduction to DevOps fundamentals and principles. It discusses how DevOps aims to improve collaboration between development and operations teams. It notes that DevOps was being adopted more by development teams initially. It also highlights some of the business costs of bugs and issues in production environments, and how DevOps can help improve efficiency, reduce costs, and accelerate business agility.
For a beginner, this is a good quality pictorial representation of DevOps and DevOps Center of Excellence.
Opex Software focuses on consulting, implementation and development of DevOps tools and platforms. Have helped small and large data centers! This presentation talks about Continuous Integration, Continuous Delivery at a high level. For detailed presentations and flows, please ping us.
Thanks again, Enjoy!
There are many resources out there that walk you through the process of setting up distributed systems, queuing and asynchronous processes — with and without NServiceBus.
Despite all the online education, teams continue to make the same common mistakes when designing and implementing microservices architecture. While the mistakes can have devastating consequences, they are easy to avoid when approached intentionally.
Jeffrey Palermo and Justin Self share their experiences in overcoming common microservices pitfalls and show how NServiceBus naturally encourages better architecture, such as easy adherence to SOLID principles.
Learn:
* What a microservice really is (and is not)
* What mistakes teams commonly make
* How to avoid the pitfalls and design more robust and scalable architecture
* How to equip your team for a microservices architecture
The document discusses the opportunity and challenges of adopting DevOps practices in an enterprise setting. While DevOps can provide benefits like faster delivery, increased quality, and agility, transformation is difficult for enterprises due to technical, governance, cultural, organizational, and process-related reasons. These include legacy systems, silos between teams, lack of automation, and risk management concerns. The document argues that DevOps adoption is necessary for enterprises to thrive in today's software-focused market, and that the transformation requires changes across organizational culture, processes, and technology. It provides examples of tools that can help, such as automation, self-service capabilities, and microservices architecture.
This document discusses scaling DevOps practices to the enterprise level. It addresses implications for people and teams, including moving from siloed teams to cross-functional DevOps teams aligned with products. It also covers implications for application portfolios, including prioritizing applications based on rate of change and cost of change. Additionally, the document outlines integrating security practices into DevOps through DevSecOps and provides examples of implementing static code analysis, PCI compliance, and SOX compliance checks into the DevOps pipeline.
Managing microservices - MLN's Notes from Chris Richardson@NGiNX Blog techMurthy Mln
This document discusses managing microservice infrastructure. Key points include:
- Microservices have a hexagonal architecture with business logic and REST APIs. They use an API gateway and have loose database coupling.
- Benefits include independent deployability, scalability, and fault tolerance, but complexity arises from distribution and interdependency.
- Service discovery uses registries like Eureka or Consul to enable service-to-service communication. Distributed data management requires polygot persistence across services.
- Inter-process communication avoids an enterprise service bus and uses REST, messaging queues, or asynchronous requests. Technology platforms include Cloud Foundry, Mesos, Netflix OSS, and RabbitMQ.
This presentation shares a perspective on how Enterprises are succeeding at DevOps based on observations gained through collaborating with leaders across many companies.
This document discusses DevOps and accelerating enterprise software delivery. It outlines key trends like cloud, mobile, and big data that are increasing demand for faster software delivery. The lack of continuous delivery impacts businesses by causing delays, budget overruns, and slow feedback. The document proposes adopting a DevOps approach to integrate development and operations in order to accelerate software delivery, balance priorities like speed and quality, and reduce feedback time. It describes people and tools aspects of DevOps implementation.
In this introductory webinar session, we developed how DevOps is improving the agility and the performance of a development organisation, emphasizing on how those practices enable to meet the demands of the business. The benefits of using AWS in the context of DevOps are also covered, along with the cost impact. We also explain practical case studies and outline the areas that will be developed in the following sessions.
The document discusses enabling enterprise DevOps at scale. It describes how traditional rigid structures and silos can be replaced with a DevOps transformation involving people, tools, and processes. Continuous delivery is highlighted as an important process that delivers value through automated testing and deployment. Implementing DevOps at scale requires establishing the right culture and skills through coaching, training, collaborative spaces and transparency. Automating the toolchain is also key to support the new ways of working.
This document discusses how PayPal uses Docker and PaaS to support the scale of its operations, which include 165 million active accounts and processing over 12.5 million payment transactions daily. It describes challenges such as firewall blocking and Elasticsearch issues in production environments. The solutions implemented registry high availability using Supervisord, Nginx, and Swift storage. It also discusses using Dockerized development environments for consistency and simulating production.
This document discusses best practices for DevOps transformations from EMC. It provides examples of challenges companies face with traditional IT approaches and how DevOps can help address these. It outlines a methodology for incremental DevOps adoption starting with single applications and expanding to enterprise-wide. It also discusses the value EMC can provide through DevOps services, tools, and expertise.
The document is a presentation by Mike Kavis on deriving value from enterprise DevOps. It discusses how DevOps aims to build better quality software faster and more reliably through collaboration between development and operations teams. It outlines some common misperceptions of DevOps and explains that the most fundamental goal is to remove waste from processes like redundant work and wait times. The presentation also examines what is driving DevOps from both a business perspective of faster deployments and fewer failures, and a technology perspective of new cloud-based architectures requiring more automation and collaboration across teams. It argues that DevOps needs a culture shift toward continuous improvement and removing waste from systems through automation.
This document discusses strategies for implementing DevOps practices within large enterprises. It notes that DevOps requires cultural change to break down silos between development and operations teams. Executive leadership is needed to get teams on the "same page" and defend the initiative. A pilot project was used to prove the value of DevOps and gain support. Subsequent releases introduced new practices over time to address business challenges. The document emphasizes focusing on feedback loops, collaboration, and continual learning and experimentation when adopting DevOps within a large organization.
Gene Kim, an award winning CTO, researcher and DevOps author will share his top learnings on how effective leaders are driving DevOps change, as well as the skills he believes every technology leader needs to help their organizations survive and win in the marketplace.
For more information, please visit http://cainc.to/Nv2VOe
Continuous Delivery & DevOps in the EnterpriseEberhard Wolff
Continuous Delivery and DevOps have a different value proposition in the Enterprise and therefore must be implemented differently. This presentation ta
The document discusses adopting DevOps practices at enterprise scale, outlining three patterns of DevOps adoption: driving business agility, scaling for the enterprise across hybrid environments, and driving innovation through rapid experimentation and feedback using techniques like containerization and microservices. It provides examples and case studies of organizations addressing bottlenecks in their development and deployment processes by applying practices like continuous integration, deployment automation, test automation, and service virtualization.
This document discusses patterns of organizational structure and adoption for enterprise DevOps teams. It describes common organizational structure patterns such as separate development and operations teams, renaming operations to DevOps, and forming combined DevOps teams. It also outlines adoption patterns like starting with small automation efforts, using the strangler pattern to transition applications to the cloud, conducting a DevOps maturity model gap analysis, and ultimately enabling DevOps self-service. The document provides examples and considerations for various DevOps organizational structures and adoption approaches in enterprises.
Adopting DevOps in an organization can start in many ways but from the technical perspective, a solid continuous integration environment is the mandatory foundation for many of the tools used by a DevOps team. This webinar shows how to build a continuous integration environment on Amazon Web Services (AWS) using services such as Amazon EC2, Amazon RDS and AWS CloudFormation. We also cover the benefits of using Amazon VPC to enable VPN access to the environment components, such as the source code repository, or the issue tracking database.
Demos included in this webinar:
- Building a core continuous integration environment with components such as Jenkins, Git and Bugzila, using Amazon EC2, Amazon RDS and Amazon CloudFormation.
- Baseline maintenance of the continuous integration environment.
View the Recording: http://youtu.be/5dJxhX1ChT4
Enterprise DevOps at Scale with AWS | AWS Public Sector Summit 2016Amazon Web Services
Ellucian has been migrating its entire organization from a myriad of software delivery mechanisms, many of them manual, to a highly automated and advanced suite of DevOps tools. Using tools such as Jenkins, Terraform, and Ansible along with native AWS tooling, we have built a highly customized DevOps pipeline on top of the AWS platform. In this talk, we go over some of the challenges we have faced and also discuss our thoughts on the evolution of DevOps and the emerging patterns of managing AWS-based environments.
DOES14 - Jonny Wooldridge - The Cambridge Satchel Company - 10 Enterprise Tip...Gene Kim
Jonny Wooldridge, CTO, The Cambridge Satchel Company at the DevOps Enterprise Summit 2014
View video: https://www.youtube.com/watch?v=CzUTztwcc58
View Jonny Wooldridge's blog: http://www.enterprisedevops.com
Following 3.5 years building a DevOps capability and culture at M&S I will be condensing the experience down to 10 Enterprise DevOps tips that are relevant to companies of all sizes and complexities. Bringing start-up lean thinking to an enterprise was never going to be easy but the lessons learned are relevant to us all.
Manchester ITExpo Talk: DevOps large and small - Cambridge SatchelJwooldridge
This document summarizes the experience of the author in leading large and small DevOps projects. For the large project at Marks & Spencer, the author introduced Continuous Integration, DevOps and Behavior Driven Development practices to a team of 650 working on 65 applications over 4 years. Challenges included legacy systems, complex test environments and vendors without DevOps practices. For the small project at Cambridge Satchel, the author helped launch a new website on a redesigned technology and team model based on DevOps principles in under 2 months, leading to increased sales. The document provides tips for starting a DevOps transformation including defining independently deployable layers, focusing investment where it matters most, and setting a high bar for new initiatives.
2i recently attended a DevOps Summit in London to learn more about how different companies have implemented DevOps. Read our overview to gain a better understanding of the DevOps operating model.
This document discusses an approach to DevOps. It outlines some of the challenges faced in a pre-DevOps environment like SLA violations and burnout. It then discusses how adopting a DevOps mindset can enable faster delivery while maintaining quality. Key aspects of DevOps include treating other teams as customers, establishing feedback loops, and including time for improvement. Metrics like lead time, deployments, and customer satisfaction are important. The document provides examples of DevOps practices from Spotify and references for further information.
Software development (Dev) and IT operations (Ops) are the roots of the term "DevOps" (Ops). The term refers to a culture change that will enable the continuous delivery of high-quality software and reduce the development cycle. It is primarily distinguished by shared ownership, automated workflow, and quick feedback principles. As a result, all phases of the software development cycle, not just a few, must be understood by the team members.
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...Agile Montréal
Agile Project Management: From Agile Teams to Agile Organizations
We will present the tools and strategies for adopting agile project management practices that connect business, management and delivery teams. We propose a framework that maintains an executive focus on managing investment and risk, introduces enterprise-level agile product development lifecycle and separates project governance from operational delivery while loosely coupling these activities.
À propos de Steve Mercier
Steve est un professionnel du développement de produits logiciels, comptant plus de 20 ans d’expérience. Il a développé et mis en place des lignes de production logicielles assurant une meilleure efficacité de livraison, une adhésion croissante aux meilleures pratiques définies et une qualité accrue des produits entraînant la satisfaction des clients. Il applique les méthodes de travail Agile au quotidien depuis bientôt 10 ans. Il aime les défis techniques, apprécie être responsable de livrer, avec des gens de talents, en équipe, des produits qui comptent vraiment. Au fil des années il s'est spécialisé dans les champs suivants: Bonnes pratiques de développement de logiciel, Intégration et livraison continue, Lignes de production logicielles, Infrastructure gérée comme du code, Méthodes Agile et amélioration continue. Il oeuvre en ce moment comme gestionnaire d’une équipe de 15 DevOps bourrés de talent chez Lightspeed.
À propos de Jean-Paul Chauvet
President, Lightspeed
With over 20 years' experience as a marketing and sales executive in the technology sector, JP has been a key element in the continued growth of Lightspeed. By developing and leading Lightspeed's product strategy, go-to-market direction and taking a direct approach to engaging independent businesses, he has helped Lightspeed increase revenue, strengthen partner relations and achieve success month over month.
Agile & DevOps - It's all about project successAdam Stephensen
The document provides information on DevOps practices and tools from Microsoft. It discusses how DevOps enables continuous delivery of value through integrating people, processes, and tools. Benefits of DevOps include more frequent and stable releases, lower change failure rates, and empowered development teams. The document provides examples of DevOps scenarios and recommends discussing solutions and migration plans with Microsoft.
Scaling Awesome - 10 Actionable Strategies for Technology TransformationChef
This document provides 10 strategies for technology transformation organized around the principles of Agile, Lean, and DevOps (ALDO). The strategies are: 1) Create cross-functional teams focused on customer delivery; 2) Create a vision based on real customer needs; 3) Update products regularly to maintain competitive differentiation; 4) Create full-stack teams serving single products; 5) Involve compliance teams early in projects; 6) Operate at high velocity to respond quickly to new requirements; 7) Manage infrastructure configurations with code; 8) Support expert knowledge sharing across projects; 9) Identify team learning objectives in sprint planning; 10) Transform problems incrementally within existing projects. The overall approach is to deliver software continuously in small increments
my understanding of fundamentals of DevOps and how it relates conceptually to Agile, Scrum, Kanban, etc.
SlideShare does not allow uploading a new version of existing presentation. Hence I have to upload the new verson.
Goto https://www.slideshare.net/nitinbhide/devops-understanding-core-concepts for latest version.
DevOps is a practice that aims to break down barriers between development and operations teams. It originated as teams adopted Agile methodologies and moved toward continuous delivery of software. DevOps aims to speed up delivery through practices like continuous integration, infrastructure as code, and breaking down silos between teams. The document outlines the history and benefits of DevOps, including increased speed, reliability, collaboration and security. It also defines key DevOps practices and provides examples of how they work.
Geecon Microservices 2015 - Swimming upstream in the container revolutionBert Jan Schrijver
Bert Jan Schrijver presented on Malmberg's transition to containerless continuous delivery. Key points include:
1) Malmberg faced issues with slow communication between development and operations due to differences in infrastructure and culture.
2) They established an expert DevOps team and defined 10 principles to guide their approach, such as ensuring the master branch is always releasable and using infrastructure as code.
3) Challenges in the transition included resistance to change and scaling infrastructure limits. Lessons focused on communication, automation, and giving teams freedom.
4) Benefits of the new approach included increased agility, availability, and cost reductions through automation and scaling. The presentation concluded with ideas
This document discusses the differences between waterfall and agile development approaches for SAP projects. It notes that it is not an "either/or" debate, as both approaches have advantages and neither is suitable for all situations. The document outlines some of the benefits of each approach, such as shorter time to market with agile but more extensive testing and change management with waterfall. It then discusses five fundamentals for becoming more agile with SAP: creating an enabling environment, building an agile development model, using smart bundling strategies, automating processes and shifting testing left, and focusing on culture change.
Automation is critical for DevOps workflows to achieve velocity, consistency, and scale. Describing infrastructure as code allows automation platforms to provision servers and resources quickly according to policies. This ensures consistency across environments and enables scaling up or down on demand. Automation eliminates manual tasks, standardizes environments, builds release pipelines, and improves collaboration between development and operations for faster delivery.
Many entrepreneurs consider DevOps solutions useful for startups and technology companies. The reason behind this notion is the chief objective of DevOps implementation, which is to help companies build their culture or establish cloud-native roots. However, the reality is completely different! Best practices in DevOps are beneficial for all enterprises irrespective of their sizes.
Read the full article - https://www.silvertouch.com/blog/enterprise-devops-importance-and-key-benefits-you-need-to-know/
Java Forum Nord 2015 - Swimming upstream in the container revolutionBert Jan Schrijver
Bert Jan Schrijver discusses how educational publisher Malmberg transitioned from a traditional operations model to a container-based continuous delivery model. Key points include establishing expert DevOps teams, defining principles like keeping the master branch releasable at all times and implementing infrastructure as code, and addressing challenges like cultural resistance to change and ensuring availability without depending on external operations experts. Benefits of the new approach include increased agility, continuity, and cost reductions through higher levels of automation and monitoring.
In Data Engineer’s Lunch #68, Will Angel, Technical Product Manager at Caribou Financial, will provide an introduction to DevOps practices and tooling including testing, deployment automation, logging, monitoring, and DevOps principles. Additionally, we will discuss some of the ways that DevOps for data engineering is different from conventional application development.
Accompanying Blog: Coming Soon!
Accompanying YouTube: https://youtu.be/eBtrOv_qLHQ
Sign Up For Our Newsletter: http://eepurl.com/grdMkn
Join Data Engineer’s Lunch Weekly at 12 PM EST Every Monday:
https://www.meetup.com/Data-Wranglers-DC/events/
Cassandra.Link:
https://cassandra.link/
Follow Us and Reach Us At:
Anant:
https://www.anant.us/
Awesome Cassandra:
https://github.com/Anant/awesome-cassandra
Email:
solutions@anant.us
LinkedIn:
https://www.linkedin.com/company/anant/
Twitter:
https://twitter.com/anantcorp
Eventbrite:
https://www.eventbrite.com/o/anant-1072927283
Facebook:
https://www.facebook.com/AnantCorp/
Join The Anant Team:
https://www.careers.anant.us
Continuous Testing: A Key to DevOps SuccessTechWell
As IT organizations adopt a DevOps strategy, continuous testing (CT) becomes a key ingredient of the DevOps ecosystem. CT enables faster release cycles, more changes per release, upfront isolation of risks, and reduced operations costs. The approach to scale the traditional automation testing infrastructure, test environments, and test data management requires a culture shift using new tools and techniques. Sujay Honnamane discusses a CT strategy for aspiring and already implemented DevOps organizations. Sujay shares examples of tools, techniques, and practical solutions that include continuous integration using the Jenkins CI server, service virtualization through CA Lisa tools, automated code coverage analysis to create impact-based tests, automated test script load balancing for effective use of test environments, and faster test cycles, providing a holistic approach/workflow for CT. Sujay and his teams have successfully implemented CT for several clients in their DevOps journey to achieve a repeatable and highly predictable software delivery process.
Cutting Edge on Development Methodologies in ITAndrea Tino
The document provides an overview of the evolution of software development methodologies from Waterfall to Agile and DevOps. It discusses how software development moved from a sequential Waterfall model to iterative Agile methodologies as business needs changed and requirements became more dynamic. It then explains how DevOps further merged development and operations teams to enable continuous delivery in highly connected, microservices-based architectures needed to support modern digital businesses. Key practices like continuous integration, delivery, infrastructure as code, and monitoring are also summarized.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Enterprise DevOps
1. Software
is
eating
the
enterprise
10
DevOps
tips
to
help
you
take
control
before
it’s
too
late
Jonny Wooldridge, CTO
2. Me:
CTO
Head of Web Engineering
Director of Platform Development
Lead Developer / Head of Development
Web Master / Lead Java Developer
2014
Board Advisor
2011
2007
2003
1999
3. Marks
&
Spencer
Founded
1884,
85,000
staff
£10.3
Bn
group
revenues
! 2011-2014 introduced DevOps to international omni-channel retailer
Marks & Spencer as part of a successful £150 Million retail re-platforming
project. The importance of DevOps now understood at board level.
! 650 Member project team, 65 new or modified applications.
! On time and on budget.
! The control of the software delivery lifecycle via Devops principles IMHO
kept the programme on the rails.
4. Cambridge
Satchel
Founded
2008,
120
Staff
£10M
total
revenues
£100M
by
2017
! Now back in start-up world at Cambridge Satchel but the enterprise
lessons are key to building a successful and relevant technology
strategy which has longevity and agility.
! $20 Million index ventures investment - clean sheet with technology
online, in store, in manufacturing and in the warehouse.
! Lessons learned in Enterprise DevOps applied everyday.
9. Over
Communicate
your
plan
What are you aiming for and what
value
will it bring?
Paces
within
enterprise
applica/ons
So2ware
Factory
/
Tooling
Why invest in DevOps, BDD, Automation?
A very valid question whether large enterprise or start-up
10. Over
Communicate
your
plan
elevator.
! Plan your attack and be prepared for the
! Make friends across the business. You have no time for
enemies. You will have to call in favours.
! Keep it simple even when it’s hard. Simple metrics.
! << Show it working to bring it to life >>
! Use Diagrams and keep in your back pocket.
! You get noticed in an enterprise if you care. So care (a lot).
11. Over
Communicate
your
plan
and the team
“It’s all about the code”
Application code, Test code, Configuration code, Script code,
infrastructure code, 3rd Party Binaries!
12. Over
Communicate
your
plan
High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Team
So[ware
Agile/Lean
prac^ces
Great
So[ware
Good
prac^ces
Good
So[ware
Poor
working
prac^ces
Poor
So[ware
Bad
working
prac^ces
Bad
So[ware
13. Over
Communicate
your
plan
High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
$$$
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
$$$$
$$
$
Understand
the
cost
to
the
organisa^on
of
slow
releases
Integra^on
test
costs
Cost
of
rework
Cost
of
delay
and
hand
off
Cost
of
building
the
wrong
thing
Cost
of
not
asking
the
right
ques^on
15. Define
the
pace
of
your
apps.
“Let’s do DevOps” << Grass roots desire from IT
Energising
“What the..” << Middle managers
Distracting
“Why can’t we release 10x a day” << Board Directors
Scary – expectation setting required
18. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Not
all
applica^ons
should
be
treated
in
the
same
way
Understand
the
pace
layers
of
your
apps
and
governance
needed
How
good
are
the
major
vendor
Ecommerce
and
Finance/ERP
systems?
Define
the
pace
of
your
applica^ons
Front
End UI!
Finance!
Systems!
Payment!
Order !
Mgt!
Core!
Ecomm!
Digital!
Asset!
Cust.!
Mgt!
Apps!
API
API
API
API
API
API
API
API
19. High
The team’s level
of agile working
practices
(Agile/lean)
You
want
to
be
here!
For
everything?
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Fight
the
right
bafles
with
your
legacy
Where
you
invest
your
$$
is
cri^cal.
Invest
in
DevOps
where
it
mafers.
Define
the
pace
of
your
applica^ons
DevOps
without
legacy
is
easy.
Front
End UI!
Finance!
Systems!
Payment!
Order !
Mgt!
Core!
Ecomm!
Digital!
Asset!
Cust.!
Mgt!
Apps!
20. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Moving
exis^ng
legacy
apps
to
faster
delivery
is
hard
Don’t
make
the
mistake
of
over
promising!
Trying
to
improve
all
of
your
applica^ons
just
won’t
be
prac^cal.
Define
the
pace
of
your
applica^ons
Really?
Legacy
Zone
22. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Components
have
no
dependencies
that
require
tes^ng
in
a
shared
test
environment
with
corporate
applica^ons
Many
corporate
dependencies
that
require
tes^ng
with
each
other
and
co-‐ordina^on
of
data
/
process
Kill
dependencies
at
all
cost
Legacy
Zone
23. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Reduce
your
legacy
and
create
new
capability
Reduce
size
and
complexity
of
slow
moving
applica^ons
Kill
dependencies
at
all
cost
E.g.
consider
crea^ng
a
Front
End
separa^on
layer
enabling
parts
to
be
independently
released
NEW
Legacy
Zone
24. Kill
dependencies
at
all
cost
Great Book.
Everyone now wants to deploy a
‘minimum viable product’
Define ‘viable’ in an enterprise
25. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Many
organisa^ons
want
to
be
lean
and
get
value
to
their
customers
quickly
Understand
what
is
really
a
viable
MVP
Kill
dependencies
at
all
cost
A
change
considered
fast
is
now
very
slow
as
it
needs
to
be
coordinated
with
a
corporate
release.
Legacy
Zone
NEW
26. Kill
dependencies
at
all
cost
! Only when you have end
to
end
visibility
of
speed of delivery across your ecosystem will
you be able to define an MVP.
! Product Owners need to understand
the
dependencies to prioritise.
27. Kill
dependencies
at
all
cost
! Understand
ALL
of
your
dependencies: Obsessively understand
and control your dependencies. It is your dependencies with other
applications, particularly corporate systems that will slow you down.
Try to avoid the dreaded corporate Integrated Test phase.
! Decouple
your
applicaIons
&
architecture:
– create services and
separate the layers of your application wherever possible.
! Decouple
your
people:
Give your teams more responsibility end to
end and greater autonomy. Remove dependencies on other teams
wherever possible.
28. Kill
dependencies
at
all
cost
! Integrate
with
3rd
parIes
carefully. Bad choices with 3rd
party integrations can kill your speed of deployment as you can
become dependent on their deployment cycles, which ultimately
slow your own.
! Stubbing: Intelligent stubs can be a good solution but is hard
and requires a strategy on ownership.
! TesIng
is
easier
with
less
dependencies:
Test scenario
complexity is reduced, test data alignment is less onerous with
fewer external dependencies.
30. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
An
example
project:
part
1
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
STEP
1:
Start
with
good
inten^ons
In
this
example
the
team
are
aware
of
DevOps
and
start
automa^ng
build/deploy/
test
and
using
Con^nuous
Integra^on.
The
Opera^ons
team
are
involved
early.
Enterprise
Project
Methodology/
Governance/Finance
promotes
integrated
test
phases
and
big
bang
deployment.
The
inten^on
is
to
deploy
independently
hence
it’s
posi^on
on
the
grid.
The
plan
is
to
think
about
Con^nuous
Delivery
later
in
the
project
Don’t
create
new
‘legacy’
NEW
Legacy
Zone
31. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
An
example
project:
part
2
Level of Independently testable and
deployable software
Low
High
STEP
2:
The
inevitable
project
pressures
show
up
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
The
team
is
under
pressure
and
func^onality
is
priori^sed
over
keeping
automated
test
and
deployment
scripts
updated.
Ops
team
not
as
engaged
as
they
had
been.
The
team
tried
BDD
but
did
not
con^nue
with
it
as
the
value
wasn’t
being
seen.
Project
Manager
requests
a
detailed
plan
for
all
tasks
un^l
go-‐live.
Agility
starts
to
slip.
Technical
debt
increases.
Don’t
create
new
‘legacy’
NEW
Legacy
Zone
32. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
An
example
project:
part
3
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
STEP
3:
Find
corporate
legacy
dependencies
The
applica^on
was
on
track
to
be
delivered
but
new
dependencies
are
found
(e.g
with
corporate
repor^ng
and
finance
systems
or
corporate
middleware)
The
new
applica^on
is
now
^ed
into
a
corporate
release
cycle.
Importantly
the
applica^on
might
now
always
be
^ed
into
corporate
release
cycle
un^l
the
dependencies
are
broken
(if
that
is
possible)
Don’t
create
new
‘legacy’
Legacy
Zone
NEW
33. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Set
the
bar
high
for
new
ini^a^ves
/
programmes
When
a
new
ini^a^ve
comes
along
and
a
new
team
is
built
to
deliver
it
set
the
bar
high
with
DevOps
opera^onal
requirements
and
ways
of
working.
Encompass:
• Behaviour
Driven
Development
• Con^nuous
Integra^on
• Con^nuous
Delivery
• Full
automa^on
• Robust
configura^on
management
Don’t
create
new
‘legacy’
NEW
Legacy
Zone
34. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Ensure
your
corporate
project
methodology
encourages
DevOps..
…else
you’ll
create
legacy
every
^me
Don’t
create
new
‘legacy’
Legacy
Zone
NEW
How
do
you
measure
success
of
your
projects?
35. Don’t
create
new
‘legacy’
! <<
Make
end-‐to-‐end
process
a
deliverable
>>:
You need to find a way to
ensure that the full end to end process of delivering software is part of the project. If it is not
the teams will lose focus and potentially slip into traditional ways of working that are more
familiar.
! Product
Teams
vs
Project
Teams:
Product teams are far more likely to want the
end-to-end process to be fast, for the software to have low levels of technical debt and be
easily supportable.
! Legacy
≠
old:
Many teams, and perhaps the majority in an Enterprise (even those using
agile methods) are set up to deliver legacy. It might be functionally rich and value creating
legacy, but it will be difficult to move into continuous delivery.
! Coaching
and
Mentors:
It is crucial that help is on hand to show the teams what
good looks like and to keep them on track both from a team point of view and technology
37. DevOps
is
not
just
an
IT
problem
! Project
Methodology.
A gated Waterfall based project
methodology will lead to a focus on dates not necessarily value creation
and customer satisfaction.
! HR,
recruitment
and
rewards
- in the same way that Agile was
disruptive, DevOps is even more so as it affects the wider team and
end-to-end processes. Often organisational structures at a high level,
and the bonus and rewards received encourage silo thinking.
! Finance
&
Procurement
– funding allocation and total cost of
ownership. A better built app today is worth the investment but may not
get funding. Tool purchases can stall waiting on the procurement
process.
38. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Wrong
3rd
Party
Suppliers
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Enterprise
equilibrium
tends
to
push
your
DevOps
adop^on
backwards
DevOps
is
not
just
an
IT
Problem
Make
the
wrong
choice
and
the
forces
may
be
working
against
your
goal
Wrong
technology
of
faster
delivery.
choice
Wrong
hiring
policy
Wrong
contractual
&
financial
frameworks
Wrong
team
objecIves
&
rewards
40. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Cloud
Adop^on
Level of Independently testable and
deployable software
Low
High
A
shared
DevOps
capabilty
can
speed-‐up
other
team’s
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
DevOps
adop^on
A
shared
capability
to
assist
environment
crea^on
and
tool
setup
You
are
unique.
Think
for
yourself
Oil
the
enterprise
machine
by
removing
common
impediments
Automa^on
Ways
of
Working
Shared
Tooling
41. You
are
unique.
Think
for
yourself
High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
You’re
going
to
have
to
think
for
yourself.
?
There
are
s^ll
a
lot
of
areas
of
enterprise
DevOps
that
s^ll
need
to
be
answered
?
?
✔
Keep
an
open
mind
and
innovate
yourself
43. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
Expensive
Tooling
won’t
move
the
needle
on
its
own
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Wrapping
en^re
legacy
applica^ons
in
new
automa^on
deployment
so[ware
isn’t
the
answer.
Don’t
automate
your
legacy
processes!
Make
your
tools
work
for
you
Legacy
Zone
$$$
44. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
MULTIPLE
DIGITAL
TOOLSETS
Mul^ple
sets
of
tools
need
to
co-‐exist
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
New
Ways
of
working
dictate
new
flexible
connected
tooling
..specifically
don’t
be
^ed
to
your
corporate
toolset
Make
your
tools
work
for
you
Embrace
best
of
breed
Open
Source
and
make
sure
you
don’t
get
^ed
to
a
par^cular
tool..
TRADITIONAL
TOOLSET
45. Make
your
tools
work
for
you
! <<New
Digital
Toolset
>>:
Create a decoupled toolset of best of
breed tools. You don’t need the same tools for all paces.
! Don’t
be
held
back
by
corporate
toolset:
Corporate tools generally
don’t cut it
! Make
your
tools
work
for
you:
Don’t change the way you work
because you have a new tool. Make sure the tool works for you not
the other way around.
! Embrace
OpenSource
where
possible:
but don’t rule out paid for
products if it makes sense.
47. Build
a
So[ware
Factory
You wouldn’t manufacture any other product at scale with
ad-hoc methods and so little visibility and traceability
48. Build
a
So[ware
Factory
for
control
and
visibility
! Build
a
so^ware
factory,
why?
! Let developers focus
on
creaIvity
– the creative aspects of
writing code, not how their code gets into environments for
testing
! Connect
your
tooling
to get value and increase visibility.
Network affect.
! Don’t
forget
informaIon
security! Add them into your build
pipeline.
! Get visibility
of
everything
– visibility of every code commit,
every requirement, bug and release. Auditors will love you!
49. Build
a
so[ware
factory
! Thanks to Magentys for following factory slides:
! www.magentys.io
58. Build
a
So[ware
Factory
for
control
and
visibility
! Have insight into your offshore suppliers like never before
! Have control of your offshore suppliers like never before
! Software Delivery data and information in one place
59. MAKE
YOUR
PARTNERS
USE
YOUR
FACTORY
! Control
the
deliverables
from
your
partners
! Do you really understand who is working for you?
! Do you know the quality of the development?
! Maintain ownership of your delivery pipeline at all costs
! Force all suppliers through your
delivery
pipe
without exception
! Builds are created from your
code
repository and all 3rd Pary
binaries versioned and centrally stored.
! Again, if you show
you
care, your partners will care.
61. Start
Behaviour
Driven
Development
Today
! Absolute Game
Changer
in all companies I’ve introduced it
! BDD is more than TDD as it engages
the
business
– usually the
business switch off when talking tests
! Keeps DevOps
on
track
– forces the right kind of automation
! Keeps arIfact
aligned
with Code (Test code, Config, Test Data)
If you do nothing else today – read up on BDD.
62. PREPARE
TO
BE
THE
LARGE
TIP #10
ENTERPRISE
OF
TOMORROW
63. Prepare
to
be
the
large
Enterprise
of
tomorrow
..so as discussed earlier make the right choices
today with:
! Technology
! Hiring, Retention & Training
! Contracts & Procurement
! 3rd Party Suppliers and Vendors.
Make the correct choices to keep
on the correct DevOps trajectory
64. High
The team’s level
of agile working
practices
(Agile/lean)
Continuous
Delivery
Level of Independently testable and
deployable software
Low
High
So[ware
Design
Team
Low
Slow
Fast
Daily/Weekly
Independent
Monthly
Coordinated
Quarterly
Enterprise
Front
End UI!
Apps!
Cambridge
Satchel
Focus
on
systems
that
will
be
key
to
innova^on
We
will
be
here!
25%
Custom,
75%
SaaS
SaaS
solu^ons
where
possible
for
back
office
Strategy
to
stay
on
high
alert
for
crea^on
of
any
new
dependencies
or
Silos
Order !
Mgt!
65. Thanks
for
listening!
Thank
you
Jonny.wooldridge@cambridgesatchel.com
My
blog,
these
slides
and
other
musings
available
at:
www.enterprisedevops.com
/
www.enterprisedevops.io
67. Here’s
what
I
would
like
help
on
If you’ve got the answers to any of these I’d love to hear
from you:
! managing test data in complex environments where
systems need aligned data
! Ensuring your Behaviour Driven Development scripts
(e.g. gherkin files) can be easily version managed across
multiple branches of code.
! Out of the box DevOps Factories?