You only have to change one thing to make DevOps work, EverythingKen Mugrage
The speaker discusses changes organizations can make to enable DevOps. They recommend: redefining terminology to fit the organization; structuring teams around products rather than functions; using modern architectures like microservices and containers; and implementing continuous delivery practices to deploy changes safely and frequently. The overarching message is that changing organizational culture and structure, not just processes or tools, is key to making DevOps work.
It's Not Continuous Delivery If You Can't Deploy Right NowKen Mugrage
This document contains notes from a presentation on continuous delivery. It discusses the importance of continuous integration and deployment practices, including deploying incomplete work using techniques like feature toggles. It also covers managing risk through practices like canary releases and dark launching. Continuous delivery is defined as the ability to deploy any changes, from features to bug fixes, to production or users quickly and sustainably. Continuous integration is described as a prerequisite, with notes on ensuring code is integrated at least daily and that broken builds are fixed quickly.
You only have to change on thing to do the DevOps, everythingKen Mugrage
In this talk I point out several areas of focus when making the transition to a DevOps culture, and point out why it’s important that you change everything.
Continuous Delivery Sounds Great but it Won't Work HereJez Humble
Since the Continuous Delivery book came out in 2010, it's gone from being a controversial idea to a commonplace... until you consider that many people who say they are doing it aren't really, and there are still plenty of places that consider it crazy talk.
In this session Jez will present some of the highlights and lowlights of the past six years listening to people explain why continuous delivery won't work, and what he learned in the process.
The Secrets of High Performance IT, Featuring Jez HumbleSerena Software
The document is a presentation by Jez Humble on the secrets of high performance IT. Some of the key points discussed include:
- Chef is an automation and delivery platform used to build, manage, and deploy infrastructure and applications.
- The highest correlations with IT performance are having code/configurations in version control, getting failure alerts from monitoring, daily code merges by developers, and having win-win relationships between dev and ops teams.
- Characteristics of high performing IT include proactive monitoring, peer-reviewed change approval, version controlling everything, high trust culture between dev and ops.
- Continuous integration, deployment pipelines, and building quality in from the start are important concepts.
- Organizational culture
01 why of dev ops - devopsguys - magentys - finalDevOpsGroup
This document discusses the reasons for adopting a DevOps approach and methodology. It outlines how business and technology environments have changed, putting pressure on development and operations teams. DevOps is presented as a way to help organizations react to these changes and deliver business value across the entire product lifecycle through practices like automation, collaboration, and continuous delivery. The document argues that DevOps can help organizations reduce costs and time-to-market while improving productivity.
Walk This Way - An Introduction to DevOpsNathen Harvey
This document provides an introduction to DevOps. It defines DevOps as a cultural and professional movement where development and operations teams work together towards common goals by leveraging ideas from other industries to enable continuous delivery. The document discusses that DevOps is about establishing a collaborative culture, automating processes, measuring outcomes, and sharing knowledge. It emphasizes that DevOps is not a job title or team, but a way of working. The closing section provides a call to action to bring development and operations teams together by taking a whole-systems view and establishing trust between teammates.
You only have to change one thing to make DevOps work, EverythingKen Mugrage
The speaker discusses changes organizations can make to enable DevOps. They recommend: redefining terminology to fit the organization; structuring teams around products rather than functions; using modern architectures like microservices and containers; and implementing continuous delivery practices to deploy changes safely and frequently. The overarching message is that changing organizational culture and structure, not just processes or tools, is key to making DevOps work.
It's Not Continuous Delivery If You Can't Deploy Right NowKen Mugrage
This document contains notes from a presentation on continuous delivery. It discusses the importance of continuous integration and deployment practices, including deploying incomplete work using techniques like feature toggles. It also covers managing risk through practices like canary releases and dark launching. Continuous delivery is defined as the ability to deploy any changes, from features to bug fixes, to production or users quickly and sustainably. Continuous integration is described as a prerequisite, with notes on ensuring code is integrated at least daily and that broken builds are fixed quickly.
You only have to change on thing to do the DevOps, everythingKen Mugrage
In this talk I point out several areas of focus when making the transition to a DevOps culture, and point out why it’s important that you change everything.
Continuous Delivery Sounds Great but it Won't Work HereJez Humble
Since the Continuous Delivery book came out in 2010, it's gone from being a controversial idea to a commonplace... until you consider that many people who say they are doing it aren't really, and there are still plenty of places that consider it crazy talk.
In this session Jez will present some of the highlights and lowlights of the past six years listening to people explain why continuous delivery won't work, and what he learned in the process.
The Secrets of High Performance IT, Featuring Jez HumbleSerena Software
The document is a presentation by Jez Humble on the secrets of high performance IT. Some of the key points discussed include:
- Chef is an automation and delivery platform used to build, manage, and deploy infrastructure and applications.
- The highest correlations with IT performance are having code/configurations in version control, getting failure alerts from monitoring, daily code merges by developers, and having win-win relationships between dev and ops teams.
- Characteristics of high performing IT include proactive monitoring, peer-reviewed change approval, version controlling everything, high trust culture between dev and ops.
- Continuous integration, deployment pipelines, and building quality in from the start are important concepts.
- Organizational culture
01 why of dev ops - devopsguys - magentys - finalDevOpsGroup
This document discusses the reasons for adopting a DevOps approach and methodology. It outlines how business and technology environments have changed, putting pressure on development and operations teams. DevOps is presented as a way to help organizations react to these changes and deliver business value across the entire product lifecycle through practices like automation, collaboration, and continuous delivery. The document argues that DevOps can help organizations reduce costs and time-to-market while improving productivity.
Walk This Way - An Introduction to DevOpsNathen Harvey
This document provides an introduction to DevOps. It defines DevOps as a cultural and professional movement where development and operations teams work together towards common goals by leveraging ideas from other industries to enable continuous delivery. The document discusses that DevOps is about establishing a collaborative culture, automating processes, measuring outcomes, and sharing knowledge. It emphasizes that DevOps is not a job title or team, but a way of working. The closing section provides a call to action to bring development and operations teams together by taking a whole-systems view and establishing trust between teammates.
Application Security Epistemology in a Continuous Delivery WorldJames Wickett
CD Summit - Austin, from DevOps Connect
Desc:
Over the years, application security (appsec) has made progress, but it has also made some considerable mis-steps. Appsec focuses almost solely on developer awareness and secure development training as remediation. This isn’t sustainable and arguably does little good. There is a better way, but we have to separate ourselves from the core assumptions we have made that got us here.
http://www.devopsconnect.com/events/cd-summit-austin/
DevOpsGuys Performance Testing with APM Tools workshopDevOpsGroup
A set of static slides that accompanied a "Live Demo" of using APM tools (AppDynamics) during load testing to isolate a performance issue, fix it, de-deploy and compare the improvement. This presentation accompanies the workshop held at the NCC Group Web Performance event in March 2014. Videos should be available on the NCC Group Community website - http://community.nccgroup-webperf.com/
The document describes a DevOps game called the Marshmallow Challenge where teams compete to build the tallest freestanding structure using spaghetti that can support a marshmallow on top. The game aims to teach DevOps principles like collaboration, continuous learning, and applying feedback. It discusses how different groups like kindergarten students versus business students or engineers perform. The rules and process for playing the game are provided along with learnings around integrating development, operations, testing and more.
Presentation at Mastering SAP 21st May 2017
Struggling with agile at scale? Thinking about scaling agile beyond the team? Want to learn from others’ mistakes? There is a lot to be learnt from those who have successfully hitchhiked their way through the galaxy of scaled agile. This session celebrates the scaled agile hitchhiker, the people who bravely tried ideas that were occasionally brilliant but often plain stupid. You will laugh, you will cry but you will also walk away with a nice long list of ideas not to try when scaling agile!
• Seven failure patterns in scaling agile
• An understanding of why these patterns lead to less than optimal results
• Tips on how to avoid falling into these failure patterns
This document summarizes one manager's journey to implement continuous integration and continuous delivery practices at an organization. It describes facing numerous setbacks and challenges along the way, including personnel issues and resistance to change. The results were improved deployment processes with consistent deployments every two weeks that finished earlier and made rollbacks and issue identification easier. Lessons learned include prioritizing culture and testing over tools and considering feature toggles or dark launches.
DevOpsGuys FutureDecoded 2016 - is DevOps the AnswerDevOpsGroup
This document provides information about DevOps and digital transformation. It discusses how DevOps can help organizations transform by moving from traditional command and control models to more collaborative and iterative approaches. A DevOps operating model is proposed that uses multi-disciplinary product delivery teams and platform teams to continuously deliver value to customers. Microsoft tools that can support a DevOps transformation are also highlighted. The document concludes by demonstrating how to deploy a Docker container cluster on Azure using DevOps techniques.
Agile Data Warehousing at Telstra, TDWI Melbourne, October 2013Em Campbell-Pretty
This document summarizes a presentation given by Em Campbell-Pretty at TDWI Melbourne Chapter in October 2013 about implementing an agile approach to data warehousing at Telstra. The key results of adopting agile methods included reducing delivery cycle times from 12 months to 3 months, increasing delivery frequency to fortnightly, decreasing costs by 50%, and achieving on-time and on-budget deliveries with high customer satisfaction and team morale. Campbell-Pretty outlined how Telstra structured their teams, implemented Scrum practices, and embraced lean principles like respect for people, continuous process flow, and continuous improvement to successfully transition their large enterprise data warehouse to an agile model.
We thought we were doing continuous delivery and then... Suzie Prince
Are you sure you are doing continuous delivery? Yeah right! We thought we were too. The journey to continuous delivery (CD) is long, winding and always evolving. Like with many things we thought we had achieved all we could with continuous delivery and then... our business model changed, and then...
Originally presented at QCon New York June 2016 https://qconnewyork.com/ny2016/ny2016/presentation/we-thought-we-were-doing-continuous-delivery-and-then.html
Continuous Integration: A bittersweet love story Suzie Prince
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
Originally presented at DevOpsDays Raleigh https://www.devopsdays.org/events/2016-raleigh/program/suzie-prince/
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/
The document discusses principles of continuous delivery (CD) and DevOps. It defines CD as integrating work frequently through automated builds and tests so software can be released at any time. DevOps is described as development and operations teams working together across the entire product lifecycle to quickly and reliably deliver higher quality software. The document provides examples of how not to implement DevOps and emphasizes that CD and DevOps are about culture, freedom, responsibility and empathy rather than just tools or processes.
Combining Speed of Delivery and Quality in Complex SystemsManuel Pais
Talk presented at the 2017 opening session of UNED's Masters of Computer Engineering.
Agenda
1. The Need for Speed (aka DevOps)
2. Failure = Quality in Complex Systems
3. Survival of High-Performing Cultures
The Phoenix Project DevOps Simulation - Paul WilkinsonPink Elephant
ncorporating DevOps – The Phoenix Project Simulation
Businesses are demanding ever shorter release cycles for new applications. Traditionally ‘Operations’ is seen as a barrier with lengthy bureaucratic controls and delays in provisioning production systems. DevOps is a growing movement for shortening development and deployment and integrating Development and Operations. However, this requires a mind-set shift, new behaviours and a cultural shift in both Development and Operations. Traditionally suspicious of each other, they must now work closely together. Yet many companies are struggling to adopt and deploy DevOps and how to change the culture.
The “Phoenix Project” Simulation game is based upon The Phoenix Project. Parts Unlimited is in trouble. Newspaper reports reveal the poor financial performance of the organisation. The only way forward to not only save the company but to make it competitive and profitable is “The Phoenix Project” which represents an IT enabled business transformation, with Retail Operations as the business owner of this project. The VP of IT Operations is asked to take the lead of the IT department and ensure that “The Phoenix Project” will be a success. But the VP of IT Operations is facing a tremendous amount of work. A huge backlog of issues, features and projects. Are you up for the challenge…?
The document discusses DevOps principles and practices to accelerate flow, including making work visible, limiting work in progress, reducing batch sizes, keeping everything in source control, and automating everything. It provides examples of how implementing these principles through practices like visual boards, WIP limits, continuous delivery, infrastructure as code, and automated testing can help reduce lead times and improve productivity. Links are included for additional reference materials on DevOps.
DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.
Putting Devs On-Call: How to Empower Your TeamVictorOps
A main tenet of DevOps is bridging the gap between the Dev team and the Ops team. One way to accomplish this is to include devs in the on-call rotation. While this may sound difficult, it’s not impossible to do…as our guide demonstrates.
We profile four companies that have successfully transitioned their dev team to being on-call and their stories can provide examples for how you too can do it.
Design Systems are a valuable asset to product teams of all sizes. They unify applications, creating a single “source of truth” for UI elements, UX principles, content strategy guidelines, and re-usable code for the components. Design Systems also add business value by reducing redundancy, outlining a strategic product vision, and keeping design and development in sync across products.
Integrating the Design System and building collaboration into the product development process is key to the success for the lifetime of the products.
Learning Outcomes:
- Define the Design System
- Learn to sell the Design System to business leaders
- Integrate the Design System into an Agile development process
- Design an application and build a Design System
Building and Scaling High Performing Technology Organizations by Jez Humble a...Agile India
This document discusses building and scaling high-performing technology organizations through agile practices and DevOps. It touches on topics like creating value streams across projects, challenges with going agile at an enterprise level, the importance of principles like test-driven development, and building a culture of learning from failures. It also provides links to research on metrics like lead time for changes and deploy frequency that correlate with high performance.
Want to do the DevOps? Change Everything - Ken Mugrage - DevOpsDays Tel Aviv ...DevOpsDays Tel Aviv
Implementing DevOps can sound relatively simple. You just get the latest configuration management tool, implement the latest container orchestration or move to the cloud, right?
The truth is that a successful adoption means a series of intertwined changes, all of which are required.
Application Security Epistemology in a Continuous Delivery WorldJames Wickett
CD Summit - Austin, from DevOps Connect
Desc:
Over the years, application security (appsec) has made progress, but it has also made some considerable mis-steps. Appsec focuses almost solely on developer awareness and secure development training as remediation. This isn’t sustainable and arguably does little good. There is a better way, but we have to separate ourselves from the core assumptions we have made that got us here.
http://www.devopsconnect.com/events/cd-summit-austin/
DevOpsGuys Performance Testing with APM Tools workshopDevOpsGroup
A set of static slides that accompanied a "Live Demo" of using APM tools (AppDynamics) during load testing to isolate a performance issue, fix it, de-deploy and compare the improvement. This presentation accompanies the workshop held at the NCC Group Web Performance event in March 2014. Videos should be available on the NCC Group Community website - http://community.nccgroup-webperf.com/
The document describes a DevOps game called the Marshmallow Challenge where teams compete to build the tallest freestanding structure using spaghetti that can support a marshmallow on top. The game aims to teach DevOps principles like collaboration, continuous learning, and applying feedback. It discusses how different groups like kindergarten students versus business students or engineers perform. The rules and process for playing the game are provided along with learnings around integrating development, operations, testing and more.
Presentation at Mastering SAP 21st May 2017
Struggling with agile at scale? Thinking about scaling agile beyond the team? Want to learn from others’ mistakes? There is a lot to be learnt from those who have successfully hitchhiked their way through the galaxy of scaled agile. This session celebrates the scaled agile hitchhiker, the people who bravely tried ideas that were occasionally brilliant but often plain stupid. You will laugh, you will cry but you will also walk away with a nice long list of ideas not to try when scaling agile!
• Seven failure patterns in scaling agile
• An understanding of why these patterns lead to less than optimal results
• Tips on how to avoid falling into these failure patterns
This document summarizes one manager's journey to implement continuous integration and continuous delivery practices at an organization. It describes facing numerous setbacks and challenges along the way, including personnel issues and resistance to change. The results were improved deployment processes with consistent deployments every two weeks that finished earlier and made rollbacks and issue identification easier. Lessons learned include prioritizing culture and testing over tools and considering feature toggles or dark launches.
DevOpsGuys FutureDecoded 2016 - is DevOps the AnswerDevOpsGroup
This document provides information about DevOps and digital transformation. It discusses how DevOps can help organizations transform by moving from traditional command and control models to more collaborative and iterative approaches. A DevOps operating model is proposed that uses multi-disciplinary product delivery teams and platform teams to continuously deliver value to customers. Microsoft tools that can support a DevOps transformation are also highlighted. The document concludes by demonstrating how to deploy a Docker container cluster on Azure using DevOps techniques.
Agile Data Warehousing at Telstra, TDWI Melbourne, October 2013Em Campbell-Pretty
This document summarizes a presentation given by Em Campbell-Pretty at TDWI Melbourne Chapter in October 2013 about implementing an agile approach to data warehousing at Telstra. The key results of adopting agile methods included reducing delivery cycle times from 12 months to 3 months, increasing delivery frequency to fortnightly, decreasing costs by 50%, and achieving on-time and on-budget deliveries with high customer satisfaction and team morale. Campbell-Pretty outlined how Telstra structured their teams, implemented Scrum practices, and embraced lean principles like respect for people, continuous process flow, and continuous improvement to successfully transition their large enterprise data warehouse to an agile model.
We thought we were doing continuous delivery and then... Suzie Prince
Are you sure you are doing continuous delivery? Yeah right! We thought we were too. The journey to continuous delivery (CD) is long, winding and always evolving. Like with many things we thought we had achieved all we could with continuous delivery and then... our business model changed, and then...
Originally presented at QCon New York June 2016 https://qconnewyork.com/ny2016/ny2016/presentation/we-thought-we-were-doing-continuous-delivery-and-then.html
Continuous Integration: A bittersweet love story Suzie Prince
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
Originally presented at DevOpsDays Raleigh https://www.devopsdays.org/events/2016-raleigh/program/suzie-prince/
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/
The document discusses principles of continuous delivery (CD) and DevOps. It defines CD as integrating work frequently through automated builds and tests so software can be released at any time. DevOps is described as development and operations teams working together across the entire product lifecycle to quickly and reliably deliver higher quality software. The document provides examples of how not to implement DevOps and emphasizes that CD and DevOps are about culture, freedom, responsibility and empathy rather than just tools or processes.
Combining Speed of Delivery and Quality in Complex SystemsManuel Pais
Talk presented at the 2017 opening session of UNED's Masters of Computer Engineering.
Agenda
1. The Need for Speed (aka DevOps)
2. Failure = Quality in Complex Systems
3. Survival of High-Performing Cultures
The Phoenix Project DevOps Simulation - Paul WilkinsonPink Elephant
ncorporating DevOps – The Phoenix Project Simulation
Businesses are demanding ever shorter release cycles for new applications. Traditionally ‘Operations’ is seen as a barrier with lengthy bureaucratic controls and delays in provisioning production systems. DevOps is a growing movement for shortening development and deployment and integrating Development and Operations. However, this requires a mind-set shift, new behaviours and a cultural shift in both Development and Operations. Traditionally suspicious of each other, they must now work closely together. Yet many companies are struggling to adopt and deploy DevOps and how to change the culture.
The “Phoenix Project” Simulation game is based upon The Phoenix Project. Parts Unlimited is in trouble. Newspaper reports reveal the poor financial performance of the organisation. The only way forward to not only save the company but to make it competitive and profitable is “The Phoenix Project” which represents an IT enabled business transformation, with Retail Operations as the business owner of this project. The VP of IT Operations is asked to take the lead of the IT department and ensure that “The Phoenix Project” will be a success. But the VP of IT Operations is facing a tremendous amount of work. A huge backlog of issues, features and projects. Are you up for the challenge…?
The document discusses DevOps principles and practices to accelerate flow, including making work visible, limiting work in progress, reducing batch sizes, keeping everything in source control, and automating everything. It provides examples of how implementing these principles through practices like visual boards, WIP limits, continuous delivery, infrastructure as code, and automated testing can help reduce lead times and improve productivity. Links are included for additional reference materials on DevOps.
DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.
Putting Devs On-Call: How to Empower Your TeamVictorOps
A main tenet of DevOps is bridging the gap between the Dev team and the Ops team. One way to accomplish this is to include devs in the on-call rotation. While this may sound difficult, it’s not impossible to do…as our guide demonstrates.
We profile four companies that have successfully transitioned their dev team to being on-call and their stories can provide examples for how you too can do it.
Design Systems are a valuable asset to product teams of all sizes. They unify applications, creating a single “source of truth” for UI elements, UX principles, content strategy guidelines, and re-usable code for the components. Design Systems also add business value by reducing redundancy, outlining a strategic product vision, and keeping design and development in sync across products.
Integrating the Design System and building collaboration into the product development process is key to the success for the lifetime of the products.
Learning Outcomes:
- Define the Design System
- Learn to sell the Design System to business leaders
- Integrate the Design System into an Agile development process
- Design an application and build a Design System
Building and Scaling High Performing Technology Organizations by Jez Humble a...Agile India
This document discusses building and scaling high-performing technology organizations through agile practices and DevOps. It touches on topics like creating value streams across projects, challenges with going agile at an enterprise level, the importance of principles like test-driven development, and building a culture of learning from failures. It also provides links to research on metrics like lead time for changes and deploy frequency that correlate with high performance.
Want to do the DevOps? Change Everything - Ken Mugrage - DevOpsDays Tel Aviv ...DevOpsDays Tel Aviv
Implementing DevOps can sound relatively simple. You just get the latest configuration management tool, implement the latest container orchestration or move to the cloud, right?
The truth is that a successful adoption means a series of intertwined changes, all of which are required.
Kris Buytaert gave a talk on DevOps at DrupalCon Munich in 2012. He discussed how the silos between development and operations created problems, and how the DevOps movement aims to break down those barriers through automation, collaboration, and continuous delivery. DevOps is not defined by specific tools but by cultural and process changes like integrating operations work into the entire software lifecycle from early on. The talk covered challenges like managing data and environments across different stages and how tools like Vagrant and configuration management can help address them.
Diversity, Inclusive Mindsets, and ArchitectureTracy Lee
This document discusses creating a more inclusive culture and architectures for tech companies and development teams. It argues that diversity matters for product design because different perspectives can help identify overlooked issues. It provides tips for building an inclusive culture, such as changing meeting norms and finding common ground beyond work. The document also introduces the concept of inclusive architectures, with pillars like defined processes, frameworks, abstractions, mentorship and state machines that can make projects more accessible and sustainable.
From the talk of the same name given first at UX Cambridge 2016.
An exploration into the creation of a design system, and the unexpected consequences for the field of UX.
Join well known industry thought leaders and experts from local New York companies for a 1/2 day event focused on the latest and greatest in DevOps practices.
The Unicorn Project and the Five Ideals.pdfVMware Tanzu
The document discusses several topics related to DevOps ideals:
1. It defines the fourth ideal of psychological safety as enabling an environment where people feel safe to take risks and try new ideas without fear of negative consequences.
2. It discusses research on high-performing teams from Google and others that identified psychological safety as a key factor in team performance.
3. It highlights the importance of a "generative" culture over a "bureaucratic" or "pathological" culture according to the Westrum typology of organizational culture.
Aufbau von agilen und effizienten IT Organisationen mit DevOpsAWS Germany
IT-Landschaften und -Applikationen werden zunehmend komplexer. Als Folge dessen haben Entwicklungsteams ihre Software-Entwicklungsprozesse mit der Zeit entsprechend weiterentwickelt. Autonome und selbstbestimmte Teams treten vermehrt in den Vordergrund und folgen einem agilen Ansatz und Prinzipien, die dem "Lean Software Development" entstammen. Dieser Wandel hat sich bis hin zu den Operationsteams vollzogen und so die Grenzen zwischen Entwicklung und Betrieb verschwimmen lassen.
Unter dem Begriff "DevOps" versteht man heute eine Menge an Werkzeugen, Prozessen, Best Practices, und auch Unternehmensleitlinien, die IT-Organisationen agiler und effizienter machen. Zwar sind die Werkzeuge und die Methodik unter DevOps Fachleuten gut verstanden, jedoch ergeben sich aufgrund des traditionellen IT-Betriebs (Mode 1 IT) oft nicht die versprochenen Vorteile, wie erhöhte Agilität und Flexibilität.
AWS bietet Ihnen eine flexible Plattform, auf deren Basis Unternehmen wie Netflix, Airbnb, Zalando und viele andere, DevOps Praktiken und Prozesse mit großem Erfolg umsetzen konnten.
Dieses Webinar nimmt die verschiedenen Elemente von DevOps genauer unter die Lupe und erklärt wie sie der Grundstein für diese Erfolgsgeschichten wurden.
JavaOne 2015 Devops and the Darkside CON6447Steve Poole
So you get DevOps. You like the idea and think it’s important. The trouble is that others in your team don’t. This session will help you understand how to convince your team of the benefits of DevOps. Packed with facts and figures, the presentation works through the common challenges Java teams face when moving to a DevOps model and outlines how to address them. It also shows you how to balance evangelism against pragmatism when championing DevOps in your organization. You’ll learn how others have made the transition to DevOps and understand what mistakes to avoid when doing so. Whether you need to know how to be a DevOps evangelist or simply want to understand why DevOps is important, this session is for you.
Video in Russian: http://www.youtube.com/watch?v=cJFVAbWZInE
Talk given with Agile-Latvia.org at TSI.lv for CS students, revealing Agile principles through real life stories and examples.
Devops & Agility - Build the Culture, Get the Tools, Win the Day - Dundee Tec...David Walker
DevOps involves development and operations engineers collaborating throughout the entire service lifecycle from design to deployment and support. It builds upon agile principles by applying them throughout the entire workflow. Implementing DevOps requires cultural changes across the entire organization where teams work together towards shared goals. Automation, lean principles, continuous monitoring and improvements are key aspects of DevOps.
From DevOps to Operations Science discusses the transition from traditional IT operations to a DevOps model where development and operations teams work collaboratively. It outlines this transition in three acts: (1) how software became the interface for customer interactions; (2) how DevOps practices like continuous delivery helped businesses adapt by delivering better customer experiences faster; and (3) how successful companies build a culture of empowerment and accountability, treat failures as learning opportunities, and remove barriers to speed through technology and culture.
Fast and Good: Alternate Approaches to Quality at Etsy - STPCon fall 2011Noah Sussman
Etsy's mission is to empower small businesses and make the global economy more fair and sustainable. The presentation discusses Etsy's alternative approach to quality which focuses on optimizing for recovery from failures rather than prevention, making many small code deployments, emphasizing testing, and maintaining a culture where failures are seen as opportunities to improve.
AppSec Pipelines and Event based SecurityMatt Tesauro
Matt Tesauro discusses moving application security (AppSec) beyond traditional security testing towards event-based security using continuous integration/continuous delivery (CI/CD) pipelines and automation. Key points include:
- Implementing AppSec pipelines that automate security tasks using tools like Docker to increase efficiency and consistency while reducing friction between AppSec and development teams.
- Treating individual security findings as tests that are run continuously via tools like Jenkins to quickly determine when issues are fixed.
- With increased automation and efficiency, one company increased the number of application assessments from 44 in 2014 to over 400 in 2016 while reducing AppSec staffing levels.
DevOps role in engineering organization (Dive into DevOps)Provectus
Kyrylo Perevozchykov — Software Engineer at DataRobot.
Title: DevOps role in engineering organization
Abstract: Many of modern engineering organizations very much rely on the DevOps. Every organization has their understanding of what DevOps is. The goal of this talk is clarifying what is DevOps is, how it’s been used to solve a real-life problem and about possible future of that term.
The document summarizes Adrian Cockcroft's experience giving talks about Netflix's approach to technology over time. It notes that initially people reacted skeptically, saying Netflix's approach was crazy and wouldn't work (2009-2010). Later, people said it could only work for large companies like Netflix (2011). By 2012, people said they wanted to adopt a similar approach but couldn't. The document outlines key lessons learned from Cockcroft's time at Netflix, including that speed wins in the marketplace and removing friction from product development helps enable faster innovation.
The document discusses problems with traditional software development approaches and proposes an alternative approach focused on continuous delivery. It argues that current practices prioritize resource utilization, projects, and technical possibilities over delivering value. Instead, it advocates for minimizing work-in-progress, focusing on flow over batching, establishing stable teams to continuously deliver working software, and making decisions based on learning rather than upfront estimates. The overall message is that software development needs to shift from a project mindset to prioritizing the delivery of valuable, working code.
Practical DevOps & Continuous Delivery – A Webinar to learn in depth on DevO...Hugo Messer
After the grant success of the C-level event "I/O: Intelligent Outsourcing", Bridge Global is conducting a free webinar under BEAM (Bridge Events And Meets) on September 6th, 2017.
We designed this webinar as a must-attend event for those who are looking for a kick-start moment to lead their organization into the DevOps environment. It attracted several attendees from all parts of the world. They all sat back and learned valuable insights on DevOps culture and practices.
People are tired of hearing the countless amount of suggestions and opinions while contemplating to start their DevOps journey. This webinar helped its attendees in getting rid of all kinds of apprehensions related to the topic.
Topics Covered
DevOps vs. Traditional Approach.
Addressing the Delivery Challenges.
Why Continuous Integration and Continuous Delivery is so relevant?
DevOps vs Release Management.
Best Practices.
Similar to DevOps isn't something you buy - DevOpsDays Cape Town (20)
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdfVALiNTRY360
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Unlock the Secrets to Effortless Video Creation with Invideo: Your Ultimate G...The Third Creative Media
"Navigating Invideo: A Comprehensive Guide" is an essential resource for anyone looking to master Invideo, an AI-powered video creation tool. This guide provides step-by-step instructions, helpful tips, and comparisons with other AI video creators. Whether you're a beginner or an experienced video editor, you'll find valuable insights to enhance your video projects and bring your creative ideas to life.
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...kalichargn70th171
In today's fiercely competitive mobile app market, the role of the QA team is pivotal for continuous improvement and sustained success. Effective testing strategies are essential to navigate the challenges confidently and precisely. Ensuring the perfection of mobile apps before they reach end-users requires thoughtful decisions in the testing plan.
Project Management: The Role of Project Dashboards.pdfKarya Keeper
Project management is a crucial aspect of any organization, ensuring that projects are completed efficiently and effectively. One of the key tools used in project management is the project dashboard, which provides a comprehensive view of project progress and performance. In this article, we will explore the role of project dashboards in project management, highlighting their key features and benefits.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdfBaha Majid
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
WWDC 2024 Keynote Review: For CocoaCoders AustinPatrick Weigel
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
The Key to Digital Success_ A Comprehensive Guide to Continuous Testing Integ...kalichargn70th171
In today's business landscape, digital integration is ubiquitous, demanding swift innovation as a necessity rather than a luxury. In a fiercely competitive market with heightened customer expectations, the timely launch of flawless digital products is crucial for both acquisition and retention—any delay risks ceding market share to competitors.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesQuickdice ERP
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Malibou Pitch Deck For Its €3M Seed Roundsjcobrien
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
Microservice Teams - How the cloud changes the way we workSven Peters
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
2. @kmugrage
TODAY’S TALK
▸ What is DevOps?
▸ Organizational Concerns
▸ Architectural Concerns
▸ Continuous Delivery
▸ There’s no test, but there is homework
3. @kmugrage
WHO AM I?
▸ From Seattle, Washington, USA
▸ Technology Evangelist at ThoughtWorks
▸ DevOpsDays Organizer
▸ Infrequent blogger at ken.wtf and gocd.org
7. @kmugrage
“DEVOPS: A CULTURE WHERE PEOPLE,
REGARDLESS OF TITLE OR BACKGROUND, WORK
TOGETHER TO IMAGINE, DEVELOP, DEPLOY AND
OPERATE A SYSTEM.”
–Me
https://kenmugrage.com/2017/05/05/my-new-definition-of-devops/
9. @kmugrage
“ANY ORGANIZATION THAT DESIGNS A SYSTEM
(DEFINED BROADLY) WILL PRODUCE A DESIGN
WHOSE STRUCTURE IS A COPY OF THE
ORGANIZATION'S COMMUNICATION STRUCTURE.”
–Mel Conway
http://www.melconway.com/Home/Conways_Law.html
14. @kmugrage
“YOU BUILD IT, YOU RUN IT”
–Werner Vogels, Amazon
https://queue.acm.org/detail.cfm?id=1142065
15. @kmugrage
“GIVING DEVELOPERS OPERATIONAL RESPONSIBILITIES HAS GREATLY ENHANCED THE QUALITY OF THE SERVICES, BOTH FROM
A CUSTOMER AND A TECHNOLOGY POINT OF VIEW. THE TRADITIONAL MODEL IS THAT YOU TAKE YOUR SOFTWARE TO THE WALL
THAT SEPARATES DEVELOPMENT AND OPERATIONS, AND THROW IT OVER AND THEN FORGET ABOUT IT. NOT AT AMAZON.
YOU BUILD IT, YOU RUN IT.
THIS BRINGS DEVELOPERS INTO CONTACT WITH THE DAY-TO-DAY OPERATION OF THEIR SOFTWARE. IT ALSO BRINGS THEM INTO
DAY-TO-DAY CONTACT WITH THE CUSTOMER. THIS CUSTOMER FEEDBACK LOOP IS ESSENTIAL FOR IMPROVING THE QUALITY OF
THE SERVICE.”
–Werner Vogels, Amazon
https://queue.acm.org/detail.cfm?id=1142065
17. @kmugrage
MONOLITHS CAN BE HARD
▸ All functionality is in one process
▸ Scale by replicating the monolith on multiple
servers
https://www.thoughtworks.com/insights/blog/microservices-nutshell
18. @kmugrage
DEVELOP SMALLER PIECES
MICROSERVICE ARCHITECTURE
▸ Each element of functionality is in a separate
service
▸ Scale by distributing these services across
servers, replicating as needed
https://www.thoughtworks.com/insights/blog/microservices-nutshell
21. @kmugrage
THE HEART OF DOING EVOLUTIONARY ARCHITECTURE
IS TO MAKE SMALL CHANGES, AND PUT IN
FEEDBACK LOOPS THAT ALLOW EVERYONE TO LEARN
FROM HOW THE SYSTEM IS DEVELOPING.
Martin Fowler
Foreword to Building Evolutionary Architecture
23. @kmugrage
CAR AS A SERVICE
https://www.k3syspro.com/cloud-computing-choosing-right-deployment-method/
24. @kmugrage
AN EXAMPLE OF PLATFORM AS A SERVICE
CLOUD.GOV
▸ Official service of the US Government
▸ 325 required security controls
▸ 269 handled by cloud.gov
▸ 42 shared
▸ 15 handled by customer
https://cloud.gov/overview/technology/responsibilities/
25. @kmugrage
THE CLOUD IS JUST SOMEBODY ELSE’S
COMPUTER
Someone at every single DevOpsDays conference
29. @kmugrage
CONTINUOUS DELIVERY IS THE ABILITY TO GET CHANGES OF
ALL TYPES—INCLUDING NEW FEATURES, CONFIGURATION
CHANGES, BUG FIXES AND EXPERIMENTS—INTO
PRODUCTION, OR INTO THE HANDS OF
USERS, SAFELY AND QUICKLY IN A SUSTAINABLE WAY.
Jez Humble
https://continuousdelivery.com/
33. @kmugrage
CI THEATRE
The ThoughtWorks tech radar recently
recommended putting a hold on the tech team
anti-pattern, CI Theatre. CI Theatre describes the
illusion of practicing continuous integration (CI)
while not really practicing it.
https://www.gocd.org/2017/05/16/its-not-CI-its-CI-theatre/
34. @kmugrage
CI THEATRE
In our study only 10% of participants
acknowledged that having a CI server
was not the same as practicing CI.
https://www.gocd.org/2017/05/16/its-not-CI-its-CI-theatre/
40. @kmugrage
EXAMPLES OF THINGS WHICH ARE BAD
▸ Deploying insecure software
▸ Deploying non-performant software
▸ Deploying non-complying software
▸ Deploying ineffective software
41. @kmugrage
…OF THE 106 COMPONENTS PER APPLICATION, THE
REPORT’S ANALYSIS REVEALED AN AVERAGE OF 24 (I.E.,
23%) HAVE KNOWN CRITICAL OR SEVERE SECURITY
VULNERABILITIES…
Derek Weeks
http://blog.sonatype.com/2015/06/rework-is-choking-software-2015-state-of-the-software-supply-chain-report/
42. @kmugrage
THE PURPOSE OF A CONTINUOUS
DELIVERY PIPELINE IS TO KILL A
RELEASE CANDIDATE
Me, and a lot of other people
45. @kmugrage
SUMMARY
▸ You’ve come to the right place to learn more
▸ Ideas for open space conversations
▸ “DevOps” as a title or team name
▸ It’s not CI if you’re not pushing to master every day
▸ Build or Buy your PAAS?
46. THANK YOU!
For more information about our products
https://www.thoughworks.com/products/
https://www.gocd.org/