The document discusses how to better sell DevOps practices to organizations. It begins by describing the downward spiral of tensions between IT operations and development teams as applications become more fragile and difficult to deploy. It then provides suggestions for framing the problems organizations face in a way that shows how DevOps practices can help address significant business issues. The document concludes by highlighting examples of organizations successfully implementing DevOps and offers additional resources for learning more.
Why Everyone Needs DevOps Now: 15 Year Study Of High Performing Technology OrgsGene Kim
This presentation describes my interpretation of the Why and How of DevOps, and the key findings from my 15 year study of high-performing IT organizations, and how they simultaneously deliver stellar service levels and rapid implementation of new features into the production environment.
Organizations employing DevOps practices such as Google, Amazon, Facebook, Etsy and Twitter are routinely deploying code into production hundreds, or even thousands, of times per day, while providing world-class availability, reliability and security. In contrast, most organizations struggle to do releases more every nine months.
He will present how these high-performing organizations achieve this fast flow of work through Product Management and Development, through QA and Infosec, and into IT Operations. By doing so, other organizations can now replicate the extraordinary culture and outcomes enabling their organization to win in the marketplace.
Achieving Elite and High Performance DevOps Using DORA MetricsAggregage
How is your organization’s DevOps doing? Do you have strategies to both identify problems and improve performance? DevOps Research and Assessment (DORA) has identified four key metrics to help organizations understand where their DevOps stands and how it can reach an elite level of performance. In this upcoming webinar, Rollbar will teach you one way to become an elite performer: focusing on Continuous Code Improvement.
Companies that use the Continuous Code Improvement approach have a compact feedback loop that tells them when there’s a code issue that needs to be fixed, fixes it, then goes back to writing and running code. It’s an approach to maintaining and updating software applications that allows for faster deployments, fewer errors, and quicker fixes to problems.
This webinar shows how to accelerate code quality as an “Elite or High Performing” DevOps team with Continuous Code Improvement, and explains how this will:
• Increase the speed of your deployments
• Improve the stability of your software
• Build in security from the start
Why Everyone Needs DevOps Now: 15 Year Study Of High Performing Technology OrgsGene Kim
This presentation describes my interpretation of the Why and How of DevOps, and the key findings from my 15 year study of high-performing IT organizations, and how they simultaneously deliver stellar service levels and rapid implementation of new features into the production environment.
Organizations employing DevOps practices such as Google, Amazon, Facebook, Etsy and Twitter are routinely deploying code into production hundreds, or even thousands, of times per day, while providing world-class availability, reliability and security. In contrast, most organizations struggle to do releases more every nine months.
He will present how these high-performing organizations achieve this fast flow of work through Product Management and Development, through QA and Infosec, and into IT Operations. By doing so, other organizations can now replicate the extraordinary culture and outcomes enabling their organization to win in the marketplace.
Achieving Elite and High Performance DevOps Using DORA MetricsAggregage
How is your organization’s DevOps doing? Do you have strategies to both identify problems and improve performance? DevOps Research and Assessment (DORA) has identified four key metrics to help organizations understand where their DevOps stands and how it can reach an elite level of performance. In this upcoming webinar, Rollbar will teach you one way to become an elite performer: focusing on Continuous Code Improvement.
Companies that use the Continuous Code Improvement approach have a compact feedback loop that tells them when there’s a code issue that needs to be fixed, fixes it, then goes back to writing and running code. It’s an approach to maintaining and updating software applications that allows for faster deployments, fewer errors, and quicker fixes to problems.
This webinar shows how to accelerate code quality as an “Elite or High Performing” DevOps team with Continuous Code Improvement, and explains how this will:
• Increase the speed of your deployments
• Improve the stability of your software
• Build in security from the start
Team Topologies - how and why to design your teams - AllDayDevOps 2017Matthew Skelton
From the AllDayDevOps 2017 live stream https://www.youtube.com/watch?v=XqowSG2Jxqc
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Takeaways:
- The implications of Conway’s Law for software teams
- Cognitive Load for teams
- Effective team topologies
- Team evolution
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...Manuel Pais
Why are so many organizations stuck in the “middle” of DevOps evolution? What’s preventing them from achieving higher levels of performance despite all the automation, tooling, and good practices in place?
Puppet’s State of DevOps Report 2021 provides important research-based clues to answer these questions, supported by the patterns and recommendations in Team Topologies.
In this talk we cover the self-imposed limitations of blindly following some “myths” around DevOps. Almost 80% of organizations are stuck in the “frozen middle” of DevOps evolution because of lack of organizational sensemaking abilities. The margin for growth for these organizations is tremendous, but they need to think beyond technical capabilities to unlock the potential of their teams to deliver with more autonomy and a sense of purpose.
The data shows that Team Topologies provides the necessary organizational and team interaction patterns that help organizations achieve performance metrics such as delivering a new customer change request to live in under one hour, or diagnosing and recovering from a serious issue in production in under an hour.
Fundamentally, we need to supercharge the fundamental principles of DevOps: fast feedback loops, minimal waste, removing bottlenecks, and continuous learning & improvement.
What does it take to get an application into production? Many processes, tools and automation surround that application to deliver it to the customer. As it becomes more common for development teams to autonomously deliver and run their software, the focus of the traditional operational teams shifts towards an as-a-service mindset. But how is such a team positioned within the company? And is Platform Engineering any different from Software Engineering?
In this talk I’ll share my experiences as a platform engineer and explain why I believe that every company should be conscious about why and how to setup this responsibility. I’ll also discuss the biggest challenges surrounding it - and how to tackle them.
Learn from the Experts: Using DORA Metrics to Accelerate Value Stream FlowDevOps.com
When responding to digital disruption, organizations are embracing DevOps practices and value stream thinking, but find it tough to measure their progress.
Organizations need to find a way to make it easy to inspect team and global metrics for incremental adaptation to accelerate the flow of value through every team’s workflow or pipeline. In this webinar, we’ll explore how to automate transparency into the 4 key metrics for throughput and stability as defined by DORA’s Accelerate State of DevOps Reports.
Join Helen Beal, DevOpsologist at Ranger4, and Jeff Keyes from Plutora for this webinar where they will teach you about the key metrics for DevOps success.
Looking through a value stream lens they will show you:
What the key metrics are;
How to make it easy for people to use them;
How they evolve flow over time.
The ability to deliver software is no longer a differentiator. In fact, it is a basic requirement for survival. Companies that embrace cloud native patterns of software delivery will survive; companies that don’t - will not.
In this webinar, we will:
- Look at the common patterns that distinguish cloud native companies and the architectures that they employ.
- Discover that an opinionated platform, one that stretches from the infrastructure all the way to the application framework, rather than ad-hoc automation, is an essential component to an enterprise's cloud native journey.
- Show that the combination of Pivotal Cloud Foundry and Spring is the complete cloud native platform.
Speaker:
Faiz Parkar
DIRECTOR OF PRODUCT MARKETING
As Director of Product Marketing for Pivotal in the Europe, Middle East and Africa region, Faiz Parkar loves working at the intersection of cloud native platforms, big data/analytics and agile application development to help organisations deliver compelling data-driven software experiences for their customers. With more than 25 years experience in the IT industry, Faiz has helped organisations large and small to take advantage of technology transitions from proprietary systems to client/server, from physical infrastructure to virtual, and from virtual infrastructure to cloud. His mission now is to help organisations accelerate their digital transformation journey and reinvent themselves as the digital leaders of the future.
Think that DevOps is just for product? Think again.
In this webinar, ITSM expert John Custy shows you how to apply DevOps principles to your IT org. This event is for anyone involved in the support and development of IT systems and services. The keys to higher-performing services are so simple, they might surprise you.
Watch the full webinar here: http://atlassian.com/help-desk/how-to-run-it-support-devops-way
Brought to you by JIRA Service Desk. Learn more: http://atlassian.com/service-desk
Learn to effectively and efficiently explore, evaluate, and confirm a shared understanding of refined backlog items using Structured conversations with the 7 Product Dimensions so they are ready for implementation.
(Presented at Agile Day New York City September 2018)
The Unicorn Project and The Five Ideals (Updated Dec 2019)Gene Kim
It is impossible to overstate how much I’ve learned since co-authoring The Phoenix Project, DevOps Handbook, and Accelerate. I’m so excited that after years of work, The Unicorn Project will be published later this year.
This book is my attempt to frame what I’ve learned studying technology leaders adopting DevOps principles and patterns in large, complex organizations, often having to fight deeply entrenched orthodoxies. And yet, despite huge obstacles, they create incredibly effective and innovative teams that create beacons of greatness that inspire us all.
In this book, we follow a senior lead developer and architect as she is exiled to the Phoenix Project, to the horror of her friends and colleagues, as punishment for contributing to a payroll outage. She tries to survive in what feels like a heartless and uncaring bureaucracy, forced to work within a system where no one can get anything done without endless committees, paperwork, change requests, and approvals. Decades of technical debt make even small changes difficult or impossible, often causing catastrophic outcomes and fear of punishment.
I get tremendous delight and gratification that this book is not about the bridge crew of the Starship Enterprise -- instead, it is about redshirt engineers, which as it turns out, whose heroic work matters most to the long-term survival of almost every organization.
In my previous books, I’ve focused on principles and practices (e.g., Three Ways, Four Types of Work). However, I’ve always wanted to describe the spectrum of cultural, experiential and value decisions we make that either enable greatness, or create chronic suffering and underperformance. They are currently as follows:
• The First Ideal — Locality and Simplicity
• The Second Ideal — Focus, Flow and Joy
• The Third Ideal — Improvement of Daily Work
• The Fourth Ideal — Psychological Safety
• The Fifth Ideal — Customer Focus
In this talk, I’ll share with you my goals and aspirations for The Unicorn Project, describe in detail the Five Ideals, along with my favorite case studies of both ideal and non-ideal, and why I believe more than ever that DevOps will be one of the most potent economic forces for decades to come.
From project to product mindset and onwards to product platform architecturesJorn Bettin
Is it possible to stay innovative and economically manage many hundreds or even thousands of products or product variants?
Organisations interested in benefiting from a product line and product platform approach must adopt values and organisational principles that encourage the development of deep domain expertise. This includes a deep understanding of the forces that continuously change the environment of the product line. These forces can then be harnessed as part of the architectural foundation for the product line.
The pervasive digitisation of services and the desire to create and operate platforms that can support large digital service ecosystems that include many organisations, have put the spotlight on design principles for product lines, product platforms, and related organisational structures.
These slides relate to a talk at ProductTank Auckland (https://www.meetup.com/ProductTank-Auckland/events/252496542/). The video recording is available at https://twitter.com/pmauckland/status/1021272934416109568.
In this session we’ll leave the need for performance a foregone conclusion and take a whirlwind tour through the complexity of modern Internet architectures. The complexities lead to evil optimization problems and significant challenges troubleshooting production issues to a speedy and successful end.
Starting with the simple facts that you can’t fix what you can’t see and you can’t improve what you can’t measure, we’ll discuss what needs monitoring and why. We’ll talk about unlikely allies in the fight for time and budget to instrument systems, applications and processes for observability.
You’ll leave the session with a better understanding of what it looks like to troubleshoot the storm of a malfunctioning large architecture and some tools and techniques you can use to not be swallowed by the Kraken.
SRE (service reliability engineer) on big DevOps platform running on the clou...DevClub_lv
SRE (service reliability engineer). The talk is to explain the SRE philosophy and the principles of production engineering and operations in clouds.
(Language – English)
Pavlo is ADOP (Accenture DevOps Platform) Service Reliability Team Lead, SRE practitioner. Has more then 18 years of IT experience in Ops and Dev.
Behind every great product is a great team doing work in a way that guarantees results. They are following a roadmap from the starting point to the end product. But a product roadmap can be elusive. This talk addresses why it is important and presents an approach to make one.
As engineers we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. We however spend very little time learning to understand and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
Plenty of people are jumping on the new hype, Observability, lots of them are replacing their “legacy” monitoring stack. Not all of them achieve the goals they set. But observability is not a tool — it is a property of a system. Moving from many small black boxes to a more holistic view of your system.
In this talk we ll talk about how to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems. We look at improving your monitoring by adapting your culture and then maybe your tooling. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior.
Furthermore we ll discuss the need for and the options of not only monitoring our platforms and it's envitable outages, but also their (potential) length and impact. We ll look at tools like at using Service Level Objects for ways to prepare teams to tweak their testing and monitoring setup and runbooks to quickly observe, react to and resolve problems.
Showcase development processes and methods with our content ready Devops PowerPoint Presentation Slide. Focus on rapid application delivery using our visually appealing development and operations PPT visuals. The operating system PowerPoint complete deck comprises self-explanatory and editable PowerPoint templates such as need for DevOps, best practices, criteria for choosing a pilot project, DevOps goals, timeline for DevOps transformation, current state future state, 30-60-90 day plan, roadmap for DevOps, transformation post successful DevOps Implementation, RACI matrix, dashboard to name a few. Users can easily customize all the templates as per their specific project needs. Furthermore, you can also use this IT operations management presentation deck to encourage your team to adopt DevOps culture practices and tools. Demonstrate DevOps goals like Increase automation and standardize the process, reduce cost effort & time to market and so on. Download our system development lifecycle PowerPoint templates to present ways to make improved products faster for greater client satisfaction. Handle deficiencies with our DevOps Powerpoint Presentation Slides. Initiate action to acquire desired assets. https://bit.ly/3y8q8NC
DevOps: A Culture Transformation, More than TechnologyCA Technologies
DevOps is not a new technology or a product. It's an approach or culture of SW development that seeks stability and performance at the same time that it speeds software deliveries to the business. We will discuss this cultural shift where development teams have to accept the feedback of operations teams and the operations team should be ready to accept frequent updates to the SW that it's running.
To learn more about DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
Treating Your Pipeline as a Product - Full Day WorkshopManuel Pais
On completion of the workshop, you should have practical experience of techniques to treat your delivery chain as a first class citizen in your value stream, including testing, monitoring and recovering your delivery system.
Agile Contracts by Drew Jemilo (Agile2015)Drew Jemilo
Agile has moved far beyond commercial software into the world’s largest enterprises and government agencies. We have scaling methods which can help launch vehicles into the atmosphere and beyond, yet traditional contract mindsets have put a drag on escape velocity. But there’s good news! We have agile explorers discovering the next frontier of contract agility. Join us for this Agile2015 session and enter the new era! This era includes the Scaled Agile Framework® (SAFe®)
TRADITIONAL MODELS TO LEAN-AGILE APPROACHES
Fixed requirements, big up-front design, and gated processes have been the norm. The rationale seemed logical in the past. It would not make sense to award a contract or commit to a major development investment without knowing what the system is supposed to do, how much it costs, and when it will be completed. We assumed that complex systems could be fully defined before they were built, that requirements and solutions would not change, and that we could build it right the first time.
Traditional models exist but Lean-Agile contract approaches are gaining momentum in both the commercial and the U.S. Federal space. Find out more!
Team Topologies - how and why to design your teams - AllDayDevOps 2017Matthew Skelton
From the AllDayDevOps 2017 live stream https://www.youtube.com/watch?v=XqowSG2Jxqc
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Takeaways:
- The implications of Conway’s Law for software teams
- Cognitive Load for teams
- Effective team topologies
- Team evolution
Keynote: Frozen DevOps? The not-so-technical Last Mile @ DevOpsDays Portugal,...Manuel Pais
Why are so many organizations stuck in the “middle” of DevOps evolution? What’s preventing them from achieving higher levels of performance despite all the automation, tooling, and good practices in place?
Puppet’s State of DevOps Report 2021 provides important research-based clues to answer these questions, supported by the patterns and recommendations in Team Topologies.
In this talk we cover the self-imposed limitations of blindly following some “myths” around DevOps. Almost 80% of organizations are stuck in the “frozen middle” of DevOps evolution because of lack of organizational sensemaking abilities. The margin for growth for these organizations is tremendous, but they need to think beyond technical capabilities to unlock the potential of their teams to deliver with more autonomy and a sense of purpose.
The data shows that Team Topologies provides the necessary organizational and team interaction patterns that help organizations achieve performance metrics such as delivering a new customer change request to live in under one hour, or diagnosing and recovering from a serious issue in production in under an hour.
Fundamentally, we need to supercharge the fundamental principles of DevOps: fast feedback loops, minimal waste, removing bottlenecks, and continuous learning & improvement.
What does it take to get an application into production? Many processes, tools and automation surround that application to deliver it to the customer. As it becomes more common for development teams to autonomously deliver and run their software, the focus of the traditional operational teams shifts towards an as-a-service mindset. But how is such a team positioned within the company? And is Platform Engineering any different from Software Engineering?
In this talk I’ll share my experiences as a platform engineer and explain why I believe that every company should be conscious about why and how to setup this responsibility. I’ll also discuss the biggest challenges surrounding it - and how to tackle them.
Learn from the Experts: Using DORA Metrics to Accelerate Value Stream FlowDevOps.com
When responding to digital disruption, organizations are embracing DevOps practices and value stream thinking, but find it tough to measure their progress.
Organizations need to find a way to make it easy to inspect team and global metrics for incremental adaptation to accelerate the flow of value through every team’s workflow or pipeline. In this webinar, we’ll explore how to automate transparency into the 4 key metrics for throughput and stability as defined by DORA’s Accelerate State of DevOps Reports.
Join Helen Beal, DevOpsologist at Ranger4, and Jeff Keyes from Plutora for this webinar where they will teach you about the key metrics for DevOps success.
Looking through a value stream lens they will show you:
What the key metrics are;
How to make it easy for people to use them;
How they evolve flow over time.
The ability to deliver software is no longer a differentiator. In fact, it is a basic requirement for survival. Companies that embrace cloud native patterns of software delivery will survive; companies that don’t - will not.
In this webinar, we will:
- Look at the common patterns that distinguish cloud native companies and the architectures that they employ.
- Discover that an opinionated platform, one that stretches from the infrastructure all the way to the application framework, rather than ad-hoc automation, is an essential component to an enterprise's cloud native journey.
- Show that the combination of Pivotal Cloud Foundry and Spring is the complete cloud native platform.
Speaker:
Faiz Parkar
DIRECTOR OF PRODUCT MARKETING
As Director of Product Marketing for Pivotal in the Europe, Middle East and Africa region, Faiz Parkar loves working at the intersection of cloud native platforms, big data/analytics and agile application development to help organisations deliver compelling data-driven software experiences for their customers. With more than 25 years experience in the IT industry, Faiz has helped organisations large and small to take advantage of technology transitions from proprietary systems to client/server, from physical infrastructure to virtual, and from virtual infrastructure to cloud. His mission now is to help organisations accelerate their digital transformation journey and reinvent themselves as the digital leaders of the future.
Think that DevOps is just for product? Think again.
In this webinar, ITSM expert John Custy shows you how to apply DevOps principles to your IT org. This event is for anyone involved in the support and development of IT systems and services. The keys to higher-performing services are so simple, they might surprise you.
Watch the full webinar here: http://atlassian.com/help-desk/how-to-run-it-support-devops-way
Brought to you by JIRA Service Desk. Learn more: http://atlassian.com/service-desk
Learn to effectively and efficiently explore, evaluate, and confirm a shared understanding of refined backlog items using Structured conversations with the 7 Product Dimensions so they are ready for implementation.
(Presented at Agile Day New York City September 2018)
The Unicorn Project and The Five Ideals (Updated Dec 2019)Gene Kim
It is impossible to overstate how much I’ve learned since co-authoring The Phoenix Project, DevOps Handbook, and Accelerate. I’m so excited that after years of work, The Unicorn Project will be published later this year.
This book is my attempt to frame what I’ve learned studying technology leaders adopting DevOps principles and patterns in large, complex organizations, often having to fight deeply entrenched orthodoxies. And yet, despite huge obstacles, they create incredibly effective and innovative teams that create beacons of greatness that inspire us all.
In this book, we follow a senior lead developer and architect as she is exiled to the Phoenix Project, to the horror of her friends and colleagues, as punishment for contributing to a payroll outage. She tries to survive in what feels like a heartless and uncaring bureaucracy, forced to work within a system where no one can get anything done without endless committees, paperwork, change requests, and approvals. Decades of technical debt make even small changes difficult or impossible, often causing catastrophic outcomes and fear of punishment.
I get tremendous delight and gratification that this book is not about the bridge crew of the Starship Enterprise -- instead, it is about redshirt engineers, which as it turns out, whose heroic work matters most to the long-term survival of almost every organization.
In my previous books, I’ve focused on principles and practices (e.g., Three Ways, Four Types of Work). However, I’ve always wanted to describe the spectrum of cultural, experiential and value decisions we make that either enable greatness, or create chronic suffering and underperformance. They are currently as follows:
• The First Ideal — Locality and Simplicity
• The Second Ideal — Focus, Flow and Joy
• The Third Ideal — Improvement of Daily Work
• The Fourth Ideal — Psychological Safety
• The Fifth Ideal — Customer Focus
In this talk, I’ll share with you my goals and aspirations for The Unicorn Project, describe in detail the Five Ideals, along with my favorite case studies of both ideal and non-ideal, and why I believe more than ever that DevOps will be one of the most potent economic forces for decades to come.
From project to product mindset and onwards to product platform architecturesJorn Bettin
Is it possible to stay innovative and economically manage many hundreds or even thousands of products or product variants?
Organisations interested in benefiting from a product line and product platform approach must adopt values and organisational principles that encourage the development of deep domain expertise. This includes a deep understanding of the forces that continuously change the environment of the product line. These forces can then be harnessed as part of the architectural foundation for the product line.
The pervasive digitisation of services and the desire to create and operate platforms that can support large digital service ecosystems that include many organisations, have put the spotlight on design principles for product lines, product platforms, and related organisational structures.
These slides relate to a talk at ProductTank Auckland (https://www.meetup.com/ProductTank-Auckland/events/252496542/). The video recording is available at https://twitter.com/pmauckland/status/1021272934416109568.
In this session we’ll leave the need for performance a foregone conclusion and take a whirlwind tour through the complexity of modern Internet architectures. The complexities lead to evil optimization problems and significant challenges troubleshooting production issues to a speedy and successful end.
Starting with the simple facts that you can’t fix what you can’t see and you can’t improve what you can’t measure, we’ll discuss what needs monitoring and why. We’ll talk about unlikely allies in the fight for time and budget to instrument systems, applications and processes for observability.
You’ll leave the session with a better understanding of what it looks like to troubleshoot the storm of a malfunctioning large architecture and some tools and techniques you can use to not be swallowed by the Kraken.
SRE (service reliability engineer) on big DevOps platform running on the clou...DevClub_lv
SRE (service reliability engineer). The talk is to explain the SRE philosophy and the principles of production engineering and operations in clouds.
(Language – English)
Pavlo is ADOP (Accenture DevOps Platform) Service Reliability Team Lead, SRE practitioner. Has more then 18 years of IT experience in Ops and Dev.
Behind every great product is a great team doing work in a way that guarantees results. They are following a roadmap from the starting point to the end product. But a product roadmap can be elusive. This talk addresses why it is important and presents an approach to make one.
As engineers we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. We however spend very little time learning to understand and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.
Plenty of people are jumping on the new hype, Observability, lots of them are replacing their “legacy” monitoring stack. Not all of them achieve the goals they set. But observability is not a tool — it is a property of a system. Moving from many small black boxes to a more holistic view of your system.
In this talk we ll talk about how to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems. We look at improving your monitoring by adapting your culture and then maybe your tooling. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior.
Furthermore we ll discuss the need for and the options of not only monitoring our platforms and it's envitable outages, but also their (potential) length and impact. We ll look at tools like at using Service Level Objects for ways to prepare teams to tweak their testing and monitoring setup and runbooks to quickly observe, react to and resolve problems.
Showcase development processes and methods with our content ready Devops PowerPoint Presentation Slide. Focus on rapid application delivery using our visually appealing development and operations PPT visuals. The operating system PowerPoint complete deck comprises self-explanatory and editable PowerPoint templates such as need for DevOps, best practices, criteria for choosing a pilot project, DevOps goals, timeline for DevOps transformation, current state future state, 30-60-90 day plan, roadmap for DevOps, transformation post successful DevOps Implementation, RACI matrix, dashboard to name a few. Users can easily customize all the templates as per their specific project needs. Furthermore, you can also use this IT operations management presentation deck to encourage your team to adopt DevOps culture practices and tools. Demonstrate DevOps goals like Increase automation and standardize the process, reduce cost effort & time to market and so on. Download our system development lifecycle PowerPoint templates to present ways to make improved products faster for greater client satisfaction. Handle deficiencies with our DevOps Powerpoint Presentation Slides. Initiate action to acquire desired assets. https://bit.ly/3y8q8NC
DevOps: A Culture Transformation, More than TechnologyCA Technologies
DevOps is not a new technology or a product. It's an approach or culture of SW development that seeks stability and performance at the same time that it speeds software deliveries to the business. We will discuss this cultural shift where development teams have to accept the feedback of operations teams and the operations team should be ready to accept frequent updates to the SW that it's running.
To learn more about DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
Treating Your Pipeline as a Product - Full Day WorkshopManuel Pais
On completion of the workshop, you should have practical experience of techniques to treat your delivery chain as a first class citizen in your value stream, including testing, monitoring and recovering your delivery system.
Agile Contracts by Drew Jemilo (Agile2015)Drew Jemilo
Agile has moved far beyond commercial software into the world’s largest enterprises and government agencies. We have scaling methods which can help launch vehicles into the atmosphere and beyond, yet traditional contract mindsets have put a drag on escape velocity. But there’s good news! We have agile explorers discovering the next frontier of contract agility. Join us for this Agile2015 session and enter the new era! This era includes the Scaled Agile Framework® (SAFe®)
TRADITIONAL MODELS TO LEAN-AGILE APPROACHES
Fixed requirements, big up-front design, and gated processes have been the norm. The rationale seemed logical in the past. It would not make sense to award a contract or commit to a major development investment without knowing what the system is supposed to do, how much it costs, and when it will be completed. We assumed that complex systems could be fully defined before they were built, that requirements and solutions would not change, and that we could build it right the first time.
Traditional models exist but Lean-Agile contract approaches are gaining momentum in both the commercial and the U.S. Federal space. Find out more!
Pictures from OOW (Oracle OpenWorld 2012) in the CA Service Virtualization sponsored Tap & Brew areas - launch and book signing for CA Press "Service Virtualization - Reality is Overrated" with authors John Michelsen and Jason English. For more information on the book and collaboration with the SV community of IT managers, software developers and testers, see http://servicevirtualization.com/book.
CA John Michelsen - Oracle OpenWorld 2012 - "ServiceVirtualization Reality is...ServiceVirtualization.Com
CA CTO, inventor of SV and author John Michelsen's presentation at Oracle OpenWorld #OOW 2012. To truly achieve Agile development, enterprises need a "virtual world" to avoid constraints in software development. Service Virtualization is a new technology and practice of simulating and modeling any service or system dependency needed by teams throughout development, integration, functional and performance testing activities. Other industries from avionics to pharma already understand the power of simulation and virtual "wind tunnels" throughout design and development, and now it's time for software and IT innovation to follow this route to more consistent quality and innovation speed with SV. For more info, visit CA.com or see the community at http://servicevirtualization.com.
10+ Deploys Per Day: Dev and Ops Cooperation at FlickrJohn Allspaw
Communications and cooperation between development and operations isn't optional, it's mandatory. Flickr takes the idea of "release early, release often" to an extreme - on a normal day there are 10 full deployments of the site to our servers. This session discusses why this rate of change works so well, and the culture and technology needed to make it possible.
DOES SFO 2016 - Greg Maxey and Laurent Rochette - DSL at ScaleGene Kim
t last year’s DOES conference, we introduced the new Domain Specific Language (DSL) for Electric Flow and painted a vision for how it could revolutionize application release automation (ARA) for very large enterprise implementations.
We are pleased to share with you our experiences and learnings from such a large scale implementation in a financial services company that we’ve been working on this past year. This is a very large implementation—hundreds of ‘platforms’, each containing hundreds of application components each targeting hundreds of ‘device types’, that is, thousands of components distributed across tens of thousands of end points in data centers across the world.
Because of regulatory and quality concerns, complex multi-environment stage testing and promotion systems with clear separation of duties must be enforced. While Electric Flow provided the core functionality to achieve these goals, there was a considerable amount of customization required to support legacy applications, tools and processes. All of the custom work done by the Electric Cloud professional services teams was done in DSL, that is, source code first. Customizations are maintained in a source control system and applied to the various staging environments through automated script execution managed by Electric Flow. While the Electric Flow UI was not used to author content, it was used to verify implementation and provide a convenient ways for the client to monitor progress of their application delivery. The result was a highly maintainable and scalable implementation that could be customized and adjusted on a moment’s notice. Indeed, the project has been managed in a lean agile manner with three week sprints.
DOES SFO 2016 - Daniel Perez - Doubling Down on ChatOps in the EnterpriseGene Kim
HPE's Research Development & Engineering team has been on a fast-tracked DevOps journey over the past couple of years.
During our DOES 2014 talk we shared our deployment of ElectricFlow as a highly available and centralized self-service solution that has enabled HPE developers to quickly onboard onto ElectricFlow for build/test/deployment pipelines in a repeatable and cost-effective way.
At DOES 2015 we expanded on our investments into a comprehensive monitoring, self-healing, and accelerated deployment strategy across all of our applications to further bridge our Dev and Ops gap with greater visibility into our environments and to accelerate our time-to-market with repeatable and fully automated deploys.
Join us this year as we continue in this journey with our biggest transformation yet: the proliferation of ChatOps within our organization. We will discuss the decisions that lead us to these investments, the key lessons we have learned, and share our various Hubot integrations and capabilities.
DOES SFO 2016 - Greg Padak - Default to OpenGene Kim
Large enterprises have hierarchical organizations to define areas of responsibility and drive better accountability. Those structures often block cross-team interactions and knowledge sharing that slow innovation and agility. We will discuss strategies that use open platforms to drive meaningful development outcomes through collaboration and productivity across the enterprise.
DOES SFO 2016 - Mark Imbriaco - Lessons From the Bleeding EdgeGene Kim
DevOps news is dominated by discussions about tools, and with good reason. It's not unusual for the amount of infrastructure-related code in a system to approach or even exceed the amount of code dedicated to the actual problem the system is solving, even in small systems. As our systems scale in size and complexity, we invest an ever increasing amount of resources into building solutions to help manage our our complex technical systems. And rightly so.
What's often overlooked, however, is the human component of our systems. All too often our approaches to tools, processes, and systems management attempt to remove humans rather than empower them.
I'll make the case that humans are not a source of entropy to be safeguarded against in our systems, but rather a fundamental source of resilience and even efficiency. We'll discuss ways that we can use this point of view to our advantage when constructing our systems to move faster without sacrificing safety. We'll look at things like tools and our interactions with them, team collaboration, and even organizational structure and policies.
We've had plenty of talks about building for web scale, cloud scale, and even planetary scale. Let's spend some time talking about designing for human scale.
DOES SFO 2016 - Marc Priolo - Are we there yet? Gene Kim
2 years ago at DOES14, I presented “Vision Versus Execution: Implementing Continuous Delivery”. I shared how we achieved a big Continuous Delivery win – increasing software test coverage and delivery velocity and efficiency.
Since then, we have been busy scaling DevOps, Continuous Delivery and Lean principles across teams and practices throughout Urban Science. This rollout included both a cultural aspect, as well as an implementation of a centralized, shared, self-service automation solution for our teams – enabling them to “opt-in” to an automated pipeline.
In this talk I will present anecdotes and learnings gathered through our experience over the past two years and discuss the challenges and the value of scaling DevOps across the organization.
Longer days & brighter, warmer evenings are at the top of everyone's list for what they enjoy most about summer. For more information, please visit; http://www.edscomfortsolutions.com.
Why Everyone Needs DevOps Now: My Fourteen Year Journey Studying High Perform...Akamai Technologies
How do great IT organizations simultaneously deliver stellar service levels and fast flow of new features into production? It requires creating a “super-tribe”, where development, test, IT operations and information security genuinely work together to solve business objectives as opposed to throwing each under the bus. In this talk, Gene Kim will describe what successful development organization transformations look like, and how they were achieved from a Dev and Ops perspective. Drawing upon a 14 year study of high performing IT organizations, Gene will share the best known methods, recipes and case studies of how to implement successful DevOps-style transformations. See Gene Kim's Edge Presentation: http://www.akamai.com/html/custconf/edgetv-developers.html#gene-kim
The Akamai Edge Conference is a gathering of the industry revolutionaries who are committed to creating leading edge experiences, realizing the full potential of what is possible in a Faster Forward World. From customer innovation stories, industry panels, technical labs, partner and government forums to Web security and developers' tracks, there’s something for everyone at Edge 2013.
Learn more at http://www.akamai.com/edge
Top Lessons Learned While Researching and Writing The DevOps HandbookDynatrace
Top Lessons Learned While Researching and Writing The DevOps Handbook
In this webinar, Gene Kim shares his top insights discovered while co-authoring The DevOps Handbook with Jez Humble, Patrick Debois, and John Willis, including:
• Informative DevOps transformation case studies around continuous integration and delivery
• Jez Humble’s latest definitions of continuous delivery vs. deployment
• How Conway’s Law and architecture can both hinder and enable success
• Concrete techniques to build a culture of continuous experimentation and learning – including those from Google, Etsy, Nordstrom, and Capital One
DevOps Patterns Distilled: Implementing The Needed Practices In Practical StepsCA Technologies
Learn from Gene Kim, one of the “DevOps Cookbook” authors, how to help accelerate DevOps adoption, increase the success of DevOps initiatives and lower the activation energy required for DevOps transformations to start and finish.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
The Unicorn Project and The Five Ideals (older: see notes for newer version)Gene Kim
Updated version here (Dec 2019): https://www.slideshare.net/realgenekim/the-unicorn-project-and-the-five-ideals-updated-dec-2019
It is impossible to overstate how much I’ve learned since co-authoring The Phoenix Project, DevOps Handbook, and Accelerate. I’m so excited that after years of work, The Unicorn Project will be published later this year.
This book is my attempt to frame what I’ve learned studying technology leaders adopting DevOps principles and patterns in large, complex organizations, often having to fight deeply entrenched orthodoxies. And yet, despite huge obstacles, they create incredibly effective and innovative teams that create beacons of greatness that inspire us all.
In this book, we follow a senior lead developer and architect as she is exiled to the Phoenix Project, to the horror of her friends and colleagues, as punishment for contributing to a payroll outage. She tries to survive in what feels like a heartless and uncaring bureaucracy, forced to work within a system where no one can get anything done without endless committees, paperwork, change requests, and approvals. Decades of technical debt make even small changes difficult or impossible, often causing catastrophic outcomes and fear of punishment.
I get tremendous delight and gratification that this book is not about the bridge crew of the Starship Enterprise -- instead, it is about redshirt engineers, which as it turns out, whose heroic work matters most to the long-term survival of almost every organization.
In my previous books, I’ve focused on principles and practices (e.g., Three Ways, Four Types of Work). However, I’ve always wanted to describe the spectrum of cultural, experiential and value decisions we make that either enable greatness, or create chronic suffering and underperformance. They are currently as follows:
• The First Ideal — Locality and Simplicity
• The Second Ideal — Focus, Flow and Joy
• The Third Ideal — Improvement of Daily Work
• The Fourth Ideal — Psychological Safety
• The Fifth Ideal — Customer Focus
In this talk, I’ll share with you my goals and aspirations for The Unicorn Project, describe in detail the Five Ideals, along with my favorite case studies of both ideal and non-ideal, and why I believe more than ever that DevOps will be one of the most potent economic forces for decades to come.
2019 12 Clojure/conj: Love Letter To Clojure, and A Datomic Experience ReportGene Kim
Talk video: https://www.youtube.com/watch?v=5mbp3SEha38&t=1652s
Blog post: https://itrevolution.com/love-letter-to-clojure-part-1
I will explain how learning the Clojure programming language three years ago changed my life. It led to a series of revelations about all the invisible structures that are required to enable developers to be productive. These concepts show up all over The Unicorn Project, but most prominently in the First Ideal of Locality and Simplicity, and how it can lead to the Second Ideal of Focus, Flow, and Joy.
Without doubt, Clojure was one of the most difficult things I’ve learned professionally, but it has also been one of the most rewarding. It brought the joy of programming back into my life. For the first time in my career, as I’m nearing fifty years old, I’m finally able to write programs that do what I want them to do, and am able to build upon them for years without them collapsing like a house of cards, as has been my normal experience.
The famous French philosopher Claude Lévi-Strauss would say of certain tools, “Is it good to think with?” For reasons that I will try to explain in this post, Clojure embraces a set of design principles and sensibilities that were new to me: functional programming, immutability, an astonishingly strong sense of conservative minimalism (e.g., hardly any breaking changes in ten years!), and much more…
Clojure introduced to me a far better set of tools to think with and to also build with. It’s also led to a set of aha moments that explain why for decades my code would eventually fall apart, becoming more and more difficult to change, as if collapsing under its own weight. Learning Clojure taught me how to prevent myself from constantly self-sabotaging my code in this way.
Speaker Recording Tips For Virtual DevOps Enterprise (And Why We're Pre-Recor...Gene Kim
In this presentation, I describe why we've decided to pre-record our talks for DevOps Enterprise Summit, and some of the top lessons learned for any speaker who needs to record their presentations.
I cover microphones, standing up, elevating your camera, adjusting your lighting, picking a good background, and record!
To learn more about the awesome DevOps Enterprise Summit programming here: https://itrevolution.com/london-virtual-what-to-expect/
Keeping The Auditor Away: DevOps Audit Compliance Case StudiesGene Kim
GenOrganizations and development teams are moving beyond waterfall models to those embracing a continuous delivery/DevOps-style set of processes. The deployment of doing tens, hundreds, or even thousands of deploys per day as 'normal' does not align to the SDLC, separation of duties, and common controls expected by auditors.
In this presentation, we will describe what auditors look for in a compliance audit, how to develop alternate control procedures that fulfill those reporting requirements, how to avoid “red flags” that indicate inadequate controls, and real world case studies and reporting artifacts.
Gene Kim has been studying high performing IT organizations since 1999 and helped develop the SOX scoping guidelines with the Institute of Internal Auditors in 2005. James DeLuccia IV is the leader for the Ernst & Young Americas Certification Services, James oversees all of the audits against common industry standards, and champions several global program implementation roll-outs. Developing and 'translating' the control environment behaviors of clients, such as Google, Amazon, Workday, and others is difficult. This discussion will bridge the needs of auditors with the community of developers by sharing examples, discussing the assurance expectations, and how to communicate to pass an audit.
2012 Velocity London: DevOps Patterns DistilledGene Kim
2012 Velocity London,
Presentation by Patrick Debois (@patrickdebois), Damon Edwards (@damonedwards), Gene Kim (@realgenekim), John Willis (@botchagalupe)
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
18. The Downward Spiral
Operations Sees…
Fragile applications are prone to
failure
Long time required to figure out “which
bit got flipped”
Detective control is a salesperson
Too much time required to restore
service
Too much firefighting and unplanned
work
Planned project work cannot complete
Frustrated customers leave
Market share goes down
Business misses Wall Street
commitments
Business makes even larger promises
to Wall Street
Dev Sees…
More urgent, date-driven projects
put into the queue
Even more fragile code put into
production
More releases have increasingly
“turbulent installs”
Release cycles lengthen to
amortize “cost of deployments”
Failing bigger deployments more
difficult to diagnose
Most senior and constrained IT
ops resources have less time to
fix underlying process problems
Ever increasing backlog of
infrastructure projects that could
fix root cause and reduce costs
Ever increasing amount of
tension between IT Ops and
Development
These aren’t IT Operations problems…
These are business problems!
21. @RealGeneKim
Easy Lines To Get Started
Problem
“What’s the difference between a good day and a bad
day?”
“What keeps you up at night?”
36
22. @RealGeneKim
Easy Lines To Get Started
Significance
“Does anyone really care if that bad thing happens?”
“On a scale of 1-10, how big of a problem is this?”
“So what?”
37
23. @RealGeneKim
Easy Lines To Get Started
Solution
“If you could wave a magic wand, what would you
do?”
“If you were king/queen, what would it look like?”
38
24. @RealGeneKim
Easy Lines To Get Started
Value
“What’s in it for you?”
“In six months, if all this comes true, what does life
look like for you?”
39
25. @RealGeneKim
Stages Of Value Selling
Problem
Significance
Solution
Value
40
When you do this, it should give you confidence that you’re not wasting
anyone’s time.
26. The Downward Spiral
Operations Sees…
Fragile applications are prone to
failure
Long time required to figure out “which
bit got flipped”
Detective control is a salesperson
Too much time required to restore
service
Too much firefighting and unplanned
work
Planned project work cannot complete
Frustrated customers leave
Market share goes down
Business misses Wall Street
commitments
Business makes even larger promises
to Wall Street
Dev Sees…
More urgent, date-driven projects
put into the queue
Even more fragile code put into
production
More releases have increasingly
“turbulent installs”
Release cycles lengthen to
amortize “cost of deployments”
Failing bigger deployments more
difficult to diagnose
Most senior and constrained IT
ops resources have less time to
fix underlying process problems
Ever increasing backlog of
infrastructure projects that could
fix root cause and reduce costs
Ever increasing amount of
tension between IT Ops and
Development
These aren’t IT Operations problems…
These are business problems!
29. The Downward Spiral
Operations Sees…
Fragile applications are prone to
failure
Long time required to figure out “which
bit got flipped”
Detective control is a salesperson
Too much time required to restore
service
Too much firefighting and unplanned
work
Planned project work cannot complete
Frustrated customers leave
Market share goes down
Business misses Wall Street
commitments
Business makes even larger promises
to Wall Street
Dev Sees…
More urgent, date-driven projects
put into the queue
Even more fragile code put into
production
More releases have increasingly
“turbulent installs”
Release cycles lengthen to
amortize “cost of deployments”
Failing bigger deployments more
difficult to diagnose
Most senior and constrained IT
ops resources have less time to
fix underlying process problems
Ever increasing backlog of
infrastructure projects that could
fix root cause and reduce costs
Ever increasing amount of
tension between IT Ops and
Development
These aren’t IT Operations problems…
These are business problems!
31. The Downward Spiral
Operations Sees…
Fragile applications are prone to
failure
Long time required to figure out “which
bit got flipped”
Detective control is a salesperson
Too much time required to restore
service
Too much firefighting and unplanned
work
Planned project work cannot complete
Frustrated customers leave
Market share goes down
Business misses Wall Street
commitments
Business makes even larger promises
to Wall Street
Dev Sees…
More urgent, date-driven projects
put into the queue
Even more fragile code put into
production
More releases have increasingly
“turbulent installs”
Release cycles lengthen to
amortize “cost of deployments”
Failing bigger deployments more
difficult to diagnose
Most senior and constrained IT
ops resources have less time to
fix underlying process problems
Ever increasing backlog of
infrastructure projects that could
fix root cause and reduce costs
Ever increasing amount of
tension between IT Ops and
Development
These aren’t IT Operations problems…
These are business problems!
35. @RealGeneKim
Value To Infosec
Integrate security testing into daily Dev work
Reduce time from “find to fix”
Reduce surface area of risk
Non-functional requirements (Anonymous can
do 6 GB/sec DDoS: how can we survive it?)
Enforce consistency
Build in auditability
Have reliance on IT Ops tools in daily use
Traceability of production artifacts
50
36. The Downward Spiral
Operations Sees…
Fragile applications are prone to
failure
Long time required to figure out “which
bit got flipped”
Detective control is a salesperson
Too much time required to restore
service
Too much firefighting and unplanned
work
Planned project work cannot complete
Frustrated customers leave
Market share goes down
Business misses Wall Street
commitments
Business makes even larger promises
to Wall Street
Dev Sees…
More urgent, date-driven projects
put into the queue
Even more fragile code put into
production
More releases have increasingly
“turbulent installs”
Release cycles lengthen to
amortize “cost of deployments”
Failing bigger deployments more
difficult to diagnose
Most senior and constrained IT
ops resources have less time to
fix underlying process problems
Ever increasing backlog of
infrastructure projects that could
fix root cause and reduce costs
Ever increasing amount of
tension between IT Ops and
Development
These aren’t IT Operations problems…
These are business problems!
41. @RealGeneKim
Our Desired Future Reality
Installs are predictable and require less time/effort than ever
Engineering teams take decisive steps to correct bad installs (and they don’t
happen again)
We are deploying code faster than ever, and can quickly detect and recover
We have operational discipline to enforce a structured resolution process
Less unexpected downtime
Schedule and complete infrastructure improvement projects
Bad installs rarely have a cascading effect
Business unit releases are on schedule (vs delayed)
Customers rarely leave
We’re winning customers
We exceed our 20% growth target
Our business hitting earnings targets
We can tackle even more projects, hire more stars, etc.
56
42. @RealGeneKim
High Performing DevOps Teams
They’re more agile
30x more frequent deployments
8,000x faster cycle time than their peers
They’re more reliable
2x the change success rate
12x faster MTTR
Source: Puppet Labs 2012 State Of DevOps: http://puppetlabs.com/2013-state-of-devops-infographic
43. 58
How organizations achieve high performance
• 89% have infrastructure artifacts in version control
• 82% have automated process to create environments
Source: Puppet Las 2012 DevOps Survey Of Practice
44. 59
Performance by DevOps maturity
Organizations that implemented DevOps practices over 12
months ago were 5x more likely to be high performing than
organizations that weren’t implementing DevOps at all.
Source: Puppet Las 2012 DevOps Survey Of Practice
45. @RealGeneKim
Who Is Doing DevOps?
Google, Amazon, Netflix, Etsy, Twitter, Facebook
, Pinterest …
BNY Mellon, Bank of America, World
Bank, Paychex, Intuit…
The
Gap, Nordstrom, REI, Macy’s, GameStop, …
Portland State University, Seton Hill
University, Kansas State University…
Who else?
60
46. @RealGeneKim
Who Is Doing DevOps?
Google, Amazon, Netflix, Etsy, Twitter, Facebook
, Pinterest …
BNY Mellon, Bank of America, World
Bank, Paychex, Intuit…
The
Gap, Nordstrom, REI, Macy’s, GameStop, …
Portland State University, Seton Hill
University, Kansas State University…
Who else?
61
50. @RealGeneKim
65
“This book will have a profound
effect on IT, just as The Goal did
for manufacturing.” --Jez
Humble, co-author Continuous
Delivery
“This is the IT swamp draining
manual for anyone who is neck
deep in alligators.” --Adrian
Cockroft, Cloud Architect at
Netflix
“This is The Goal for our
decade, and is for any IT
professional who wants their life
back.” --Charles Betz, IT
architect, author “Architecture
and Patterns for IT”
55. @RealGeneKim
If I Could Wave A Magic Wand, Everyone Will…
Be energized about how practitioners can
contribute in this organizational journey
Leave with some concrete steps to get some
great outcomes
Help create the coalition that starts putting
DevOps practices into place
117
56. @RealGeneKim
119
“Some books you give to
friends, for the joy of sharing a
great novel.
“Some books you recommend to
your colleagues and
employees, to create common
ground.
“Some books you share with your
boss, to plant the seeds of a big
idea.
“The Phoenix Project is all three.”
--Jeremiah Shirk, Integration &
Infrastructure Manager at
Kansas State University
57. @RealGeneKim
Our Mission: Positively Impact The Lives Of
One Million IT Workers By 2017
Free 170 page
excerpt:http://itrevolution.com/the-
phoenix-project-excerpt/
http://slideshare.net/realgenekim
DevOps Defensive Audit Toolkit
Enterprise DevOps Case Studies
Early draft of upcoming “DevOps
Cookbook”
(Allspaw, DeBois, Edwards, Humble, Kim
, Orzen)
Email me at genek@realgenekim.me
In fact, I think this destructive pattern is the root cause of one of the biggest problems we face, both as a profession, but has the potential to generate more economic value than anything we’ve seen in 30 years. I’m going to share with you what this destructive pattern is, and maybe it’ll sound familiar to you... It’s a story that can be told in four Acts
Who are they auditing? IT operations.I love IT operatoins. Why? Because when the developers screw up, the only people who can save the day are the IT operations people. Memory leak? No problem, we’ll do hourly reboots until you figure that out.Who here is from IT operations?Bad day:Not as prepared for the audit as they thoughtSpending 30% of their time scrambling, generating presentation for auditorsOr an outage, and the developer is adamant that they didn’t make the change – they’re saying, “it must be the security guys – they’re always causing outages”Or, there’s 50 systems behind the load balancer, and six systems are acting funny – what different, and who made them differentOr every server is like a snowflake, each having their own personalityWe as Tripwire practitioners can help them make sure changes are made visible, authorized, deployed completely and accurately, find differencesCreate and enforce a culture of change management and causality
Source: Flickr: birdsandanchors
Who’s introducing variance? Well, it’s often these guys. Show me a developer who isn’t causing an outage, I’ll show you one who is on vacation.Primary measurement is deploy features quickly – get to market.I’ve worked with two of the five largest Internet companies (Google, Microsoft, Yahoo, AOL, Amazon), and I now believe that the biggest differentiator to great time to market is great operations:Bad day: We do 6 weeks of testing, but deployment still fails. Why? QA environment doesn’t match productionOr there’s a failure in testing, and no one can agree whether it’s a code failure or an environment failureOr changes are made in QA, but no one wrote them down, so they didn’t get replicated downstream in productionBelieve it or not, we as Tripwire practitioners can even help them – make sure environments are available when we need them, that they’re properly configured correctly the first time, document all the changes, replicate them downstream
[ picture of messy data center ] Ten minutes into Bill’s first day on the job, he has to deal with a payroll run failure. Tomorrow is payday, and finance just found out that while all the salaried employees are going to get paid, none of the hourly factory employees will. All their records from the factory timekeeping systems were zeroed out.Was it a SAN failure? A database failure? An application failure? Interface failure? Cabling error?
So who are all these constituencies that we can help, and increase our relevance as Tripwire practitioners and champions?How many people here are in infosec?Goal: protect critical systems and dataSafeguard organizational commitmentsPrevent security breaches, help quickly detect and recover from themBad day: no security standardsNo one is complyingYes, we’re 3 years behind. “Whaddyagonna do about it?”Vs. we (Tripwire owner) can become more relevant and add value by help infosec by leveraging all the configuration guidance out thereMeasure variance between produciton and those known good statesTrust and verify that when management says, we’ve trued up the configurations, they’ve actually done itWhy? Now, more than ever, there are an ever increasing amount of regulatory and contractual requirements to protect systems and data
There are many ways to react to this: like, fear, horror, trying to become invisible… All understandable, given the circumstances…Because infosec can no longer take 4 weeks to turn around a security review for application code, or take 6 weeks to turnaround a firewall change. But, on the other hand, I think it’s will be the best thing to ever happen to infosec in the past 20 years. We’re calling this Rugged DevOps, because it’s a way for infosec to integrate into the DevOps process, and be welcomed. And not be viewed as the shrill hysterical folks who slow the business down.
Tell story of Amazon, Netflix: they care about, availability, securityIt’s not a push, it’s a pull – they’re looking for our help (#1 concern: fear of disintermediation and being marginalized)
There are many ways to react to this: like, fear, horror, trying to become invisible… All understandable, given the circumstances…Because infosec can no longer take 4 weeks to turn around a security review for application code, or take 6 weeks to turnaround a firewall change. But, on the other hand, I think it’s will be the best thing to ever happen to infosec in the past 20 years. We’re calling this Rugged DevOps, because it’s a way for infosec to integrate into the DevOps process, and be welcomed. And not be viewed as the shrill hysterical folks who slow the business down.
How each side Actively impedes the achievement of each other’s goals.
Two things:Arguing with him was like arguing with columbo: he was always five steps ahead of you, and he was so disarming“Before I can trust you, I first need to know you care”“Genuine Curiousity”: He integrated patterns so much into the fiber of his being
How each side Actively impedes the achievement of each other’s goals.
That’sJez Humble of “Continuous Delivery” fame (@jezhumble) in the picture and me sitting together at PuppetConf 2012.
How each side Actively impedes the achievement of each other’s goals.
How each side Actively impedes the achievement of each other’s goals.
How each side Actively impedes the achievement of each other’s goals.
All of that code has moved to our B2 repoExplosive growth in B2 development internally.5x growthWe aren't just saying we are using B2s - we're doing it every single day.
The Goal introduces the Theory of Constraints, has been the most influential book in Gene’s career. Book taught in most MBA programs. What I love about the Goal, is that it’s a Novel. It’s the story about Alex, who is a Plant Manager. He has to fix the Cost and Due date issues in 90 days, otherwise the plant will be shut down. You live the word through Alex’s eyes, where he discovers almost everything he believes about plant management is wrong and pre-destined for failure. You meet his wife and children, and his great epiphany is actually out on a Gene asked me to read an early copy of When IT Fails, a Business Novel: and just like the Goal, it’s a novel and the first 170 pages describe the problems the company and IT team is facing, from multiple perspectives. It’s an engaging story earns us the right to describe what the solution should look like. Gene, why did you and the co-authors model the book so closely on The Goal?The solution to any complex business problem requires different stakeholders, and in order to do that you first need empathy of what the problem looks like from Operation, Development, Security, Service Management and the Business.
The Goal introduces the Theory of Constraints, has been the most influential book in Gene’s career. Book taught in most MBA programs. What I love about the Goal, is that it’s a Novel. It’s the story about Alex, who is a Plant Manager. He has to fix the Cost and Due date issues in 90 days, otherwise the plant will be shut down. You live the word through Alex’s eyes, where he discovers almost everything he believes about plant management is wrong and pre-destined for failure. You meet his wife and children, and his great epiphany is actually out on a Gene asked me to read an early copy of When IT Fails, a Business Novel: and just like the Goal, it’s a novel and the first 170 pages describe the problems the company and IT team is facing, from multiple perspectives. It’s an engaging story earns us the right to describe what the solution should look like. Gene, why did you and the co-authors model the book so closely on The Goal?The solution to any complex business problem requires different stakeholders, and in order to do that you first need empathy of what the problem looks like from Operation, Development, Security, Service Management and the Business.
EranFeigenbaumDirector of Security, Google Enterprise
[ picture of messy data center ] Ten minutes into Bill’s first day on the job, he has to deal with a payroll run failure. Tomorrow is payday, and finance just found out that while all the salaried employees are going to get paid, none of the hourly factory employees will. All their records from the factory timekeeping systems were zeroed out.Was it a SAN failure? A database failure? An application failure? Interface failure? Cabling error?
All of that code has moved to our B2 repoExplosive growth in B2 development internally.5x growthWe aren't just saying we are using B2s - we're doing it every single day.