This document provides a guide to initiating and supporting a DevOps transformation through a 3-step process: 1) Build the "Why?" by understanding the business reasons for change, 2) Build organizational alignment by getting stakeholders on the same page through techniques like value stream mapping, and 3) Implement continuous improvement by developing a common DevOps vision focused on system flow and feedback. The value lies in improving productivity, quality and collaboration between development and operations teams through a cultural shift toward shared goals and automated processes.
Without Self-Service Operations, the Cloud is Just Expensive Hosting 2.0 - (a...dev2ops
Damon Edwards (DTO Solutions) presentation at Cloud Expo 2014 Santa Clara.
We are all here because we are sold on the transformative promise of The Cloud. But what good is all of this ephemeral, on-demand infrastructure if your usage doesn't actually improve the agility and speed of your business? How must Operations adapt in order to avoid stifling your Cloud initiative?
Agile Principles are more Software Development focused. There is need for Organizations to look for Software Development Agility nothing but DevOps. In order to achieve Organization operational efficiency the complete Organization needs to be DevOps complaint.
Take away for orgnizations on What is that they need to do?
At present, DevOps has got several buzz words associated with it. Standards in terminology by bringing in concepts such that everybody speaks same language.
DevOpsDays Austin: Helping Horses Become Unicorns, Chef's Operations Maturity...Matt Ray
Helping customers evaluate their ability to deploy and operate systems while managing incidents is key to our Consulting practice. We have developed an operations maturity model that provides a roadmap for understanding and improving mean time to production while setting realistic expectations. This session will explain the challenges and thresholds for becoming a more effective organization.
Without Self-Service Operations, the Cloud is Just Expensive Hosting 2.0 - (a...dev2ops
Damon Edwards (DTO Solutions) presentation at Cloud Expo 2014 Santa Clara.
We are all here because we are sold on the transformative promise of The Cloud. But what good is all of this ephemeral, on-demand infrastructure if your usage doesn't actually improve the agility and speed of your business? How must Operations adapt in order to avoid stifling your Cloud initiative?
Agile Principles are more Software Development focused. There is need for Organizations to look for Software Development Agility nothing but DevOps. In order to achieve Organization operational efficiency the complete Organization needs to be DevOps complaint.
Take away for orgnizations on What is that they need to do?
At present, DevOps has got several buzz words associated with it. Standards in terminology by bringing in concepts such that everybody speaks same language.
DevOpsDays Austin: Helping Horses Become Unicorns, Chef's Operations Maturity...Matt Ray
Helping customers evaluate their ability to deploy and operate systems while managing incidents is key to our Consulting practice. We have developed an operations maturity model that provides a roadmap for understanding and improving mean time to production while setting realistic expectations. This session will explain the challenges and thresholds for becoming a more effective organization.
TJ Randall, VP of Customer Success at XebiaLabs, gives his presentation on how to express the cost of your application delivery at the DevOps Leadership Summit in Boston MA.
1 year has passed since my Devops laboratory talk in Devopsdays Melbourne and we haven't stopped experimenting. After all the buzz and great conversations at Devops days I decided to extend the talk with a few more experiments on top of the previous presentation. This talk was first presented in Last.conf Melbourne on June 2016. The objective is no matter were your company is in terms of adopting a Devops culture/mindset there is always opportunities to try something new.
The experiments covered include:
E0. At the beginning, there was devs and ops
E1. Placements
E2. The tooling team (code name Gandalf)
E3. Secondments
E4. Ops as an attribute of Business areas
E5. The era of Guilds
E6. The raise of the Delivery Engineering teams
E7. Sec + DevOps
E8. Leverage vs Autonomy
E9. Finance + DevOps
E10. ????
The pursuit for the perfect synchrony between software development and IT operations is still ongoing, and striking the balance won’t happen any time soon. Understand and address these 5 common DevOps challenges to achieve a higher- functioning and collaborative organization.
DEVNET-2015 DevOps In Depth - Damon Edwards on DevOps Kaizen: Building an Ent...Cisco DevNet
Damon Edwards will be discussiong DevOps Kaizen: Building an Enterprise’s Capability to Change -- There are plenty of aspirational DevOps stories about organizations achieving blistering speed and dazzling nimbleness. But when you look at your own organization everything feels complicated, contentious, and stuck. How do you get started? How do you overcome the silos, the legacy, the entrenched behaviors? This talk is about starting and sustaining a DevOps transformation in large and complex of organizations using a methodical -- and totally reasonable -- Kaizen (Continuous Improvement) approach. This talk isn't about mythical silver bullets. It's about real examples of enterprises that learned to fix themselves by taking a fresh look at proven techniques
Navvia is always looking for ways to improve how we do things and we’ve come to see DevOps as our compass on the road to continual improvement. However, DevOps means different things to different people.
To our company, it has become the rallying cry for organizational change. It is the standard that leads us on a path towards better alignment across teams, enhanced agility, higher quality and the elimination of waste.
What you will learn:
- Why Navvia embarked on DevOps
- An overview of DevOps including common misconceptions
- A case study entitled “a tale of two apps”
- How Navvia is implementing DevOps
- What we’ve learned so far
It’s an exciting journey with the destination being improved customer experience, higher rates of innovation and a faster path to business value.
Agile 2014- Metrics driven development and devopsKarthik Gaekwad
There are many facets of devops, and we will spend our time in this presentation focusing on collecting and using metrics (business, application, system, etc.) and building a metrics driven culture in organizations.
We will define how we have seen devops progress in our organizations and how we’ve realized that different teams in our organizations can find common ground when teams (who have different roles) can work well together when they use metrics as the common language.
Karthik will talk about how we are using the principles from the Lean Startup to define our development cycles, sprints and using metrics to quantify how successful the products we are trying to come out with in R&D. Initially we started practicing devops on the dev and ops side of the house but realized this was still a black box to the business side of the house, so we pivoted to what our business actually understood, and that was metrics; today, we focus more on metrics (business and system level), and can fail or succeed fast to achieve our business goals faster than before.
Ernest will go into detail on how a large, mature SaaS organization uses metrics in conjunction with distributed agile development and DevOps to guide their development at scale. How much a product is used, how much each feature is used, and how much value each user gets out of it are key drivers for a business strategy - and it’s all information that’s emitted by a system. He'll show how large companies have invested time in collecting and using these metrics to guide their decisions and influence their culture.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
This session is an overview on what DevOps is (to me) and how it impacts traditional organizations the most. DevOps is way more than just continuous delivery! From an Agile (synergetic) mindset, DevOps takes a step beyond and focusses on automation, collaboration and learning. Apart from that I also look forward to what oppurtunities lie ahead when implementing DevOps.
On March 2nd I presented this DevOps Unraveled session for abt 40 IT-managers at business university Nyenrode. This was part of the Masterclass Agile management
(Dutch website http://www.executiveeducation.nl/open-programmas/programmadetails/masterclass-agile-management/sectie/introductie.html ).
The Role of Automation in the Journey to Continuous DeliveryXebiaLabs
Presenters Robert Reeves, CTO and Cofounder of Datical, and Tim Buntel, VP of Products at XebiaLabs, give an expert presentation on the role of automation in Continuous Delivery. Find the entire webinar here: https://xebialabs.com/community/webinars/
First DRAFT of a DevOps presentation and posters covering the essentials for a DevOps mindset. Help improve the content by forking and contributing a pull request to https://github.com/wpschaub/DevOps-mindset-essentials/blob/master/README.md.
5 Keys to Building a Successful DevOps Culture featuring Mandi WallsSerena Software
DevOps is not just about tools and processes, it’s about people and their interactions. It requires a cultural shift that impacts every level in the organization and requires everyone to contribute.
Advance ALM and DevOps Practices with Continuous ImprovementTechWell
Do you want to improve your application lifecycle and incorporate DevOps practices quickly with limited resources? If so, you’re experiencing a common scenario – not enough budget and unrealistic time constraints. Your big multi-year application lifecycle management (ALM) project seems less achievable than ever, and you are left wondering how to move forward. Jason St-Cyr shares how to establish a continuous improvement approach using “build, measure, learn” techniques and a DevOps maturity model to kickstart your DevOps/ALM project. Jason reviews some of the tools—Visual Studio Online, Atlassian OnDemand, and TeamCity—available to support iterative DevOps changes. Find out how to tackle smaller achievable chunks of process improvement, even when time does not seem to be on your side. Learn how to plan for incremental organizational change and examine metrics for monitoring improvements, reporting on success, and supporting your business case for further investment. Join Jason to see why you don’t have to put your organization’s DevOps initiatives on hold.
More and more teams are turning to DevOps as a way of working together to improve the efficiency and quality of software delivery and start adding more value to the business. But without having someone on the team with experience of putting it into practice, it's sometimes difficult to know how to get started.
Redgate Software invited Steve Thair, CTO at the DevOpsGuys, to deliver a one-hour training session on 'How to get started with DevOps'. Steve gave practical tips on how you can start implementing DevOps in your own organization.
The recording can be found here - https://youtu.be/ZioF58drwcA
For more information about services from the DevOpsGuys visit www.devopsguys.com
To find out about extending DevOps practices to the database visit www.red-gate.com/solutions
Continuous Delivery in a Legacy Shop—One Step at a TimeTechWell
Not every continuous delivery (CD) initiative starts with someone saying “Drop everything. We’re going to do DevOps.” Sometimes, you have to grow your process incrementally. And sometimes you don’t set out to grow at all—you are just fixing problems with your process, trying to make things better. Gene Gotimer discusses techniques and the chain of tools he has used to bring a DevOps mindset and CD practices into a legacy environment. Gene discusses how his team started fixing problems and making process improvements in development. From there, they tackled one problem after another, each time making the release a little better and a little less risky. They incrementally brought their practices through other environments until the project was confidently delivering working and tested releases every two weeks. Gene shares their journey and the tools they used to build quality into the product, the releases, and the release process.
Continuous Integration Is for Everyone—Especially DevOpsTechWell
Continuous delivery and deployment are taking center stage in the DevOps conversations. Neither continuous delivery nor deployment are easy to jump into, and both make a lot of assumptions about the applications being released. Continuous integration (CI), however, is for everyone who wants higher development velocity and better quality. CI can be implemented in development shops from brand new to large enterprise teams. When implemented, CI helps the organization take a giant leap into modern development. With the ever-growing expectation for DevOps teams to produce faster, high-quality software releases, continuous testing—a key CI driver—must occur at all stages of the software delivery chain. Chris Riley covers the important tenets of CI metrics, key CI components, testing, infrastructure, and end-to-end testing. Learn how CI can fit into all development shops, and take back strategies for tackling the challenges of a new system including change control, management, and sustainability.
TJ Randall, VP of Customer Success at XebiaLabs, gives his presentation on how to express the cost of your application delivery at the DevOps Leadership Summit in Boston MA.
1 year has passed since my Devops laboratory talk in Devopsdays Melbourne and we haven't stopped experimenting. After all the buzz and great conversations at Devops days I decided to extend the talk with a few more experiments on top of the previous presentation. This talk was first presented in Last.conf Melbourne on June 2016. The objective is no matter were your company is in terms of adopting a Devops culture/mindset there is always opportunities to try something new.
The experiments covered include:
E0. At the beginning, there was devs and ops
E1. Placements
E2. The tooling team (code name Gandalf)
E3. Secondments
E4. Ops as an attribute of Business areas
E5. The era of Guilds
E6. The raise of the Delivery Engineering teams
E7. Sec + DevOps
E8. Leverage vs Autonomy
E9. Finance + DevOps
E10. ????
The pursuit for the perfect synchrony between software development and IT operations is still ongoing, and striking the balance won’t happen any time soon. Understand and address these 5 common DevOps challenges to achieve a higher- functioning and collaborative organization.
DEVNET-2015 DevOps In Depth - Damon Edwards on DevOps Kaizen: Building an Ent...Cisco DevNet
Damon Edwards will be discussiong DevOps Kaizen: Building an Enterprise’s Capability to Change -- There are plenty of aspirational DevOps stories about organizations achieving blistering speed and dazzling nimbleness. But when you look at your own organization everything feels complicated, contentious, and stuck. How do you get started? How do you overcome the silos, the legacy, the entrenched behaviors? This talk is about starting and sustaining a DevOps transformation in large and complex of organizations using a methodical -- and totally reasonable -- Kaizen (Continuous Improvement) approach. This talk isn't about mythical silver bullets. It's about real examples of enterprises that learned to fix themselves by taking a fresh look at proven techniques
Navvia is always looking for ways to improve how we do things and we’ve come to see DevOps as our compass on the road to continual improvement. However, DevOps means different things to different people.
To our company, it has become the rallying cry for organizational change. It is the standard that leads us on a path towards better alignment across teams, enhanced agility, higher quality and the elimination of waste.
What you will learn:
- Why Navvia embarked on DevOps
- An overview of DevOps including common misconceptions
- A case study entitled “a tale of two apps”
- How Navvia is implementing DevOps
- What we’ve learned so far
It’s an exciting journey with the destination being improved customer experience, higher rates of innovation and a faster path to business value.
Agile 2014- Metrics driven development and devopsKarthik Gaekwad
There are many facets of devops, and we will spend our time in this presentation focusing on collecting and using metrics (business, application, system, etc.) and building a metrics driven culture in organizations.
We will define how we have seen devops progress in our organizations and how we’ve realized that different teams in our organizations can find common ground when teams (who have different roles) can work well together when they use metrics as the common language.
Karthik will talk about how we are using the principles from the Lean Startup to define our development cycles, sprints and using metrics to quantify how successful the products we are trying to come out with in R&D. Initially we started practicing devops on the dev and ops side of the house but realized this was still a black box to the business side of the house, so we pivoted to what our business actually understood, and that was metrics; today, we focus more on metrics (business and system level), and can fail or succeed fast to achieve our business goals faster than before.
Ernest will go into detail on how a large, mature SaaS organization uses metrics in conjunction with distributed agile development and DevOps to guide their development at scale. How much a product is used, how much each feature is used, and how much value each user gets out of it are key drivers for a business strategy - and it’s all information that’s emitted by a system. He'll show how large companies have invested time in collecting and using these metrics to guide their decisions and influence their culture.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
This session is an overview on what DevOps is (to me) and how it impacts traditional organizations the most. DevOps is way more than just continuous delivery! From an Agile (synergetic) mindset, DevOps takes a step beyond and focusses on automation, collaboration and learning. Apart from that I also look forward to what oppurtunities lie ahead when implementing DevOps.
On March 2nd I presented this DevOps Unraveled session for abt 40 IT-managers at business university Nyenrode. This was part of the Masterclass Agile management
(Dutch website http://www.executiveeducation.nl/open-programmas/programmadetails/masterclass-agile-management/sectie/introductie.html ).
The Role of Automation in the Journey to Continuous DeliveryXebiaLabs
Presenters Robert Reeves, CTO and Cofounder of Datical, and Tim Buntel, VP of Products at XebiaLabs, give an expert presentation on the role of automation in Continuous Delivery. Find the entire webinar here: https://xebialabs.com/community/webinars/
First DRAFT of a DevOps presentation and posters covering the essentials for a DevOps mindset. Help improve the content by forking and contributing a pull request to https://github.com/wpschaub/DevOps-mindset-essentials/blob/master/README.md.
5 Keys to Building a Successful DevOps Culture featuring Mandi WallsSerena Software
DevOps is not just about tools and processes, it’s about people and their interactions. It requires a cultural shift that impacts every level in the organization and requires everyone to contribute.
Advance ALM and DevOps Practices with Continuous ImprovementTechWell
Do you want to improve your application lifecycle and incorporate DevOps practices quickly with limited resources? If so, you’re experiencing a common scenario – not enough budget and unrealistic time constraints. Your big multi-year application lifecycle management (ALM) project seems less achievable than ever, and you are left wondering how to move forward. Jason St-Cyr shares how to establish a continuous improvement approach using “build, measure, learn” techniques and a DevOps maturity model to kickstart your DevOps/ALM project. Jason reviews some of the tools—Visual Studio Online, Atlassian OnDemand, and TeamCity—available to support iterative DevOps changes. Find out how to tackle smaller achievable chunks of process improvement, even when time does not seem to be on your side. Learn how to plan for incremental organizational change and examine metrics for monitoring improvements, reporting on success, and supporting your business case for further investment. Join Jason to see why you don’t have to put your organization’s DevOps initiatives on hold.
More and more teams are turning to DevOps as a way of working together to improve the efficiency and quality of software delivery and start adding more value to the business. But without having someone on the team with experience of putting it into practice, it's sometimes difficult to know how to get started.
Redgate Software invited Steve Thair, CTO at the DevOpsGuys, to deliver a one-hour training session on 'How to get started with DevOps'. Steve gave practical tips on how you can start implementing DevOps in your own organization.
The recording can be found here - https://youtu.be/ZioF58drwcA
For more information about services from the DevOpsGuys visit www.devopsguys.com
To find out about extending DevOps practices to the database visit www.red-gate.com/solutions
Continuous Delivery in a Legacy Shop—One Step at a TimeTechWell
Not every continuous delivery (CD) initiative starts with someone saying “Drop everything. We’re going to do DevOps.” Sometimes, you have to grow your process incrementally. And sometimes you don’t set out to grow at all—you are just fixing problems with your process, trying to make things better. Gene Gotimer discusses techniques and the chain of tools he has used to bring a DevOps mindset and CD practices into a legacy environment. Gene discusses how his team started fixing problems and making process improvements in development. From there, they tackled one problem after another, each time making the release a little better and a little less risky. They incrementally brought their practices through other environments until the project was confidently delivering working and tested releases every two weeks. Gene shares their journey and the tools they used to build quality into the product, the releases, and the release process.
Continuous Integration Is for Everyone—Especially DevOpsTechWell
Continuous delivery and deployment are taking center stage in the DevOps conversations. Neither continuous delivery nor deployment are easy to jump into, and both make a lot of assumptions about the applications being released. Continuous integration (CI), however, is for everyone who wants higher development velocity and better quality. CI can be implemented in development shops from brand new to large enterprise teams. When implemented, CI helps the organization take a giant leap into modern development. With the ever-growing expectation for DevOps teams to produce faster, high-quality software releases, continuous testing—a key CI driver—must occur at all stages of the software delivery chain. Chris Riley covers the important tenets of CI metrics, key CI components, testing, infrastructure, and end-to-end testing. Learn how CI can fit into all development shops, and take back strategies for tackling the challenges of a new system including change control, management, and sustainability.
Lean software engineering emphasizes continuous delivery of high quality applications. Ken Pugh explains the principles and practices that form the basis of lean software development―concentrating on developing a continuous flow by eliminating delays and loopbacks; delivering quickly by developing in small batches; emphasizing high quality which decreases delays due to defect repair; making policies, process and progress transparent; optimizing the whole rather than individual steps; and becoming more efficient by decreasing waste. Ken describes lean’s emphasis on cycle time, rather than resource utilization, and demonstrates the value stream map which helps you visualize the development cycle flow to identify bottlenecks. He explores the differences between push and pull flow, describes how lean thinking shows up in agile processes including Scrum and Extreme Programming, and discusses how lean can be applied to the entire workflow—not just the development portion. Ken concludes with a discussion of how you can begin your lean transformation.
Focus on Flow: Lean Principles in ActionMike Clement
Lean concepts have become more and more popular in software development. Coming from the manufacturing world, understanding these concepts and how they can apply to your software development efforts can help you get to deliver faster and more reliably. Join Mike as he makes the case for integrating lean software development principles into your software development methodology.
From Chaos to Confidence: DevOps at LeanKitJon Terry
As a company, LeanKit have believed in Lean, Kanban, Agile, DevOps since our founding. We've alway talked about how important these ideas are - in the community and inside our company.
But that doesn't mean that doing those things in practice has been easy. We're a very fast growing startup in a very competitive market space. We've tripled in size in less than a year and nearly came apart at the seams at times.
In fact, in the fall of 2015, our technology team were having a very hard team. We were out of synch with our sales & marketing partners and facing a lot of internal conflict.
But we came together as a team and worked hard to implement a well coordinated system of values, team structure, cadences, and standard practices. We're now in a much better place as a team and generating much better results for our company.
There are no one-size-fits-all answers for companies. I can't promise that if you copy LeanKit you'll succeed. But we do think we have some interesting lessons learned to share and that you just might be able to pick up some ideas that you can take back to your company.
Bio:
Jon Terry is co-Chief Executive Officer of LeanKit. Before LeanKit, Jon held a number of senior IT positions with hospital-giant HCA and its logistics subsidiary, HealthTrust Purchasing Group. He was among those responsible for launching HCA’s adoption of Lean/Agile methods.
Jon earned his Global Executive MBA from Georgetown University and ESADE Business School in Barcelona, Spain, and his Masters Certificate in Project Management from George Washington University. He is a Project Management Professional, a Certified Scrum Master, a Kanban Coaching Professional, is certified in the Lean Construction Institute’s Last Planner Method, and trained in the SAFe Lean Systems Engineering method.
Bimodal IT: Shortcut to Innovation or Path to Dysfunction?dev2ops
Damon Edwards (DTO Solutions) presentation at Pink16 in Las Vegas on February 16, 2016.
Key takeaway: "Bimodal IT describes the problem, not the solution"
DevOps & Security from an Enterprise Toolsmith's Perspectivedev2ops
Slides from presentation by Alex Honor and Damon Edwards at DevOps Connect at RSA 2015 in San Francisco on April 20, 2015.
Abstract:
IT organizations are feeling the squeeze from seemingly conflicting business mandates. At one moment the message is “Go Go Go. DevOps, Lean Startup, Continuous Delivery… move faster and give more people access”. The next moment the message is “Be more secure. Compliance above all. Keep us out of the press!”. Damon Edwards and Alex Honor work with many enterprises who are facing these challenges. This talk is an in the trenches view of how these companies are responding and learning to go faster and be more secure.
Rundeck + Nexus (from Nexus Live on June 5, 2014)dev2ops
The SimplifyOps team was on Nexus Live talking about how people use Rundeck and the integration between Rundeck and Nexus.
Link to the webcast:
https://www.youtube.com/watch?v=eHaEEBEMRA8
You Can't Change Culture, But You Can Change Behavior (DevOpsDays Rome 2012)dev2ops
Presentation by Damon Edwards at DevOpsDays Rome 2012.
Topics:
• What do we mean by "Culture"?
• DevOps Vision defined
1. See the system
2. Focus on flow
3. Recognize feedback loops
4. Look for continuous improvement opportunities
• Examples of techniques that high performing companies use
Lloyd Taylor’s talk at SVDevOps Meetup on Dec 8, 2010. Diagnosing and transforming the culture of your organization.
Video:
http://vimeo.com/17661043
Lloyd Taylor:
http://www.linkedin.com/in/lloydtaylor
SVDevOps:
http://www.meetup.com/SVDevOps/
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/
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
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.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
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.
9. “How do I explain it”
“My managers don’t get it”
“Dev group won’t talk to me”
“Ops group won’t talk to me”
“QA says I’m dangerous”
“I don’t know where to start”
BUT....
“People say they are too busy
getting real work done”
“My boss told me to buy DevOps
by next quarter or else”
“I still don’t know where to start”
“I still don’t know where to start”
“Is anybody listening to me?”
“THEY all just don’t get it”
39. Ultimate goal: Develop a Common DevOps Vision
1. See the system
expanded from
2. Focus on flow
40. Ultimate goal: Develop a Common DevOps Vision
1. See the system
expanded from
2. Focus on flow
3. Recognize feedback loops
41. Ultimate goal: Develop a Common DevOps Vision
1. See the system
expanded from
2. Focus on flow
3. Recognize feedback loops
4. Look for continuous improvement opportunities
47. Overt actions
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
48. Overt actions
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
b. timeline analysis
49. Overt actions
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
b. timeline analysis
c. waste analysis
50. Value Stream Mapping
Core business service delivery process
Current state value stream map
Steering
Committee
Erica Switzer
Full
Projects /
Expedites
L/T
Process time
H/C
Head count
S/R
Business Analyst
Lead time
P/T
Scrap rate
Erica Switzer
D
Estimates
and
requirements
Defects
EP
Partially done
TS
Task switching
W
Erica Switzer
Motion
PD
Project Manager
Extra processes
M
Waiting
Business
Change
request
Daily Scrum
meeting
Mx3
Dx3 Develop
Request QA
build
Technical
Specification
web assets
L/T 6 weeks
P/T 4 weeks
H/C 12
S/R 5%
Bob McNulty
EP
Cut project branch
L/T 15 minutes
P/T 5 minutes
H/C 1
S/R 0%
Chris Holmes
Delta
features and
fixes
L/T 8 weeks
P/T 4 weeks
H/C 5
S/R 25%
Joe Harbaugh
Dx2
QA
Business Systems
Support
Wx2
Wx2
PDx4
Development
Build and deploy
Development
Integration testing
L/T 2 days
P/T 4 hours
H/C 1
S/R 10%
Joe Harbaugh
L/T 1 day
P/T 1 day
H/C 5
S/R 95%
Joe Harbaugh
D
Release Engineering
Stan Walters
Deployment
Document
Jira issues
TSx5
Set of
service
branches
Deployment
Meeting
RT tickets
Web Assets,
flows and
wireframes
Development
Program Management
Development
Daily Scrum
meeting
Jira issues
Creative
Change
Control Forms
Technical Operations
Change
Control
RT tickets
Release
Build and deploy
L/T 8 hours
P/T 7 hours
H/C 1
S/R 2%
Fernando Gomez
Acceptance testing
L/T
P/T
H/C
S/R
Development
Environments
Documented
test plans
and cases
W
D
D
5 days
5 hours
2
10%
Raj Lee
D
PDx3
EP
Feature testing
L/T
P/T
H/C
S/R
Tested
packages
Mx8
PD
Dx2
Deploy to
Production
Staging testing
L/T 6 days
P/T 90 minutes
H/C 3
S/R 66%
Frances Middleton
4 weeks
2.5 weeks
4
20%
Raj Lee
Deploy to Staging
L/T 1 week
P/T 3.5 days
H/C 4
S/R 66%
Frances Middleton
Mx2
EP
L/T 9 hours
P/T 8 hours
H/C 6
S/R 66%
Allen Cannata
Merge project
branch
L/T 30 minutes
P/T 30 minutes
H/C 1
S/R 33%
Fernando Gomez
PDx2
Build test plan
L/T
P/T
H/C
S/R
QA
Environments
Build test cases
5 days
4 days
1
10%
Raj Lee
L/T
P/T
H/C
S/R
Staging
Environment
2 weeks
8 days
2
20%
Raj Lee
Production
Environment
Performance
testing
Deploy to
Performance
L/T 6 days
P/T 90 minutes
H/C 3
S/R 66%
Frances Middleton
L/T 1 week
P/T 3 days
H/C 1
S/R 66%
Allen Cannata
Performance
Environment
4 weeks
4 weeks
2 weeks
4 hours
4 weeks
1 day
1.5 days
7 hours
5 hours
1 hours
2.5 weeks
4.5 days
90 minutes
1.5 weeks
3.5 days
5.75 days
Process Time
= 62 days
8 hours
1.5 days
1 hour
Lead Time =
113 days
51. Value Stream Mapping
Core business service delivery process
Current state value stream map
Steering
Committee
Erica Switzer
Full
Projects /
Expedites
L/T
Process time
H/C
Head count
S/R
Business Analyst
Lead time
P/T
Scrap rate
Erica Switzer
D
Estimates
and
requirements
Defects
EP
Partially done
TS
Task switching
W
Erica Switzer
Motion
PD
Project Manager
Extra processes
M
Waiting
Business
Change
request
Daily Scrum
meeting
Mx3
Dx3 Develop
Request QA
build
Technical
Specification
web assets
L/T 6 weeks
P/T 4 weeks
H/C 12
S/R 5%
Bob McNulty
EP
Cut project branch
L/T 15 minutes
P/T 5 minutes
H/C 1
S/R 0%
Chris Holmes
Delta
features and
fixes
L/T 8 weeks
P/T 4 weeks
H/C 5
S/R 25%
Joe Harbaugh
Dx2
QA
Business Systems
Support
Wx2
Wx2
PDx4
Development
Build and deploy
Development
Integration testing
L/T 2 days
P/T 4 hours
H/C 1
S/R 10%
Joe Harbaugh
L/T 1 day
P/T 1 day
H/C 5
S/R 95%
Joe Harbaugh
D
Release Engineering
Stan Walters
Deployment
Document
Jira issues
TSx5
Set of
service
branches
Deployment
Meeting
RT tickets
Web Assets,
flows and
wireframes
Development
Program Management
Development
Daily Scrum
meeting
Jira issues
Creative
Change
Control Forms
Technical Operations
Change
Control
RT tickets
Release
Build and deploy
L/T 8 hours
P/T 7 hours
H/C 1
S/R 2%
Fernando Gomez
Acceptance testing
L/T
P/T
H/C
S/R
Development
Environments
Documented
test plans
and cases
W
D
D
5 days
5 hours
2
10%
Raj Lee
D
PDx3
EP
Feature testing
L/T
P/T
H/C
S/R
Tested
packages
Mx8
PD
Dx2
Deploy to
Production
Staging testing
L/T 6 days
P/T 90 minutes
H/C 3
S/R 66%
Frances Middleton
4 weeks
2.5 weeks
4
20%
Raj Lee
Deploy to Staging
L/T 1 week
P/T 3.5 days
H/C 4
S/R 66%
Frances Middleton
Mx2
EP
L/T 9 hours
P/T 8 hours
H/C 6
S/R 66%
Allen Cannata
Merge project
branch
L/T 30 minutes
P/T 30 minutes
H/C 1
S/R 33%
Fernando Gomez
PDx2
Build test plan
L/T
P/T
H/C
S/R
QA
Environments
Build test cases
5 days
4 days
1
10%
Raj Lee
L/T
P/T
H/C
S/R
Staging
Environment
2 weeks
8 days
2
20%
Raj Lee
Production
Environment
Performance
testing
Deploy to
Performance
L/T 6 days
P/T 90 minutes
H/C 3
S/R 66%
Frances Middleton
L/T 1 week
P/T 3 days
H/C 1
S/R 66%
Allen Cannata
Performance
Environment
4 weeks
4 weeks
2 weeks
4 hours
4 weeks
1 day
1.5 days
7 hours
5 hours
1 hours
2.5 weeks
4.5 days
90 minutes
1.5 weeks
3.5 days
5.75 days
Process Time
= 62 days
8 hours
1.5 days
1 hour
Lead Time =
113 days
52. Value Stream Mapping
M
Service pack
review
email
W
Release Program
Management
derived
reqs.
Estimates
M
PRD
M
EP
Partially done
TS
Task switching
W
Waiting
Technical Support
Product Management
EP(2)
Documentum
TS(2)
M(3)
W(2)
ERR
PRD
M(3)
checklist
Remedy
Ticket
L/T = 60d
P/T = 1d
H/C = 1
S/R = >5%
Victoria Doe
D
M
EP(3)
README
QA Test
L/T = 105d
P/T = 11d
H/C = 42
S/R =
Sam Young
L/T = 24d
P/T = 4d
H/C = 3
S/R = 50%
Jen Garza
MOP
MOP
Patch
Calendar
EP
W
Change Control
EP
Rollout
Schedule
L/T = 42d
P/T =
H/C =
S/R =
Peter Lee
ERR
PD(3)
Selective
Promotion
L/T = 90d
P/T = 15d
H/C = 5
S/R =
Steve Young
New Targets
W
Server
Provisioning
Engineering
Release
M
QA Forum
Ticket
M(3)
BRD
L/T = 60d
P/T = 16d
H/C = 3
S/R = 3%
Reggie / Carlos
MOP, SOP
EP
PD
Cloud Services
Release
ERR
D
QA forum
Tasks
Motion
PD
Lockdown
control
Extra processes
M
PRD
QA
Environment
QA Forum
Ticket
Defects
EP
W
Cloud Services
Release
Memos
L/T = 45d
P/T = 21d
H/C = 140
S/R =
Bob Smith
Scrap rate
Customer
Engineering
Design
Specs
L/T = 45d
P/T = 18d
H/C = 23
S/R =
Bob Smith
Preliminary
Development
Head count
S/R
L/T = 105d
P/T = 46d
H/C = 15
S/R = 100%
John Robert
EP
Engineering
Planning
Process
Process time
H/C
Product Program
Planning
PD
M(2)
Lead time
D
Release
Schedule
L/T =
P/T =
H/C =
S/R =
Erica Smith
PRD
L/T
P/T
L/T = 28d
P/T = 7d
H/C = 1
S/R =
Stephen / Xi
crit bugs
M(2)
Current state value stream map
Customer
communication
L/T = 56d
P/T = 7d
H/C = 6
S/R = 100%
Suresh Wu
Server
Acceptance
L/T = 14d
P/T = 1d
H/C = 4.5
S/R = 15%
Lynn A. etc
Remedy
Ticket
BTS
README
Full
Development
L/T = 75d
P/T = 43d
H/C = 130
S/R =
Bob Smith
M
W(2)
Deploy Release
EP
M(2)
Commits
Build
L/T = 1d
P/T = 0.3d
H/C = 2
S/R = 33%
John Doe
Shared Drive
Test
PD(3)
Release
Promotion
L/T = 60d
P/T = 0.2d
H/C = 1
S/R = >5%
Victoria Doe
Shared
Drive Prod
Packages
XML
Single
Image
Server
L/T = 90d
P/T = 8d
H/C = 8
S/R = 2%
Lewis S./Peter Y.
M
W(2)
EP
PD
D(3)
TS
Production
BRD
53. Value Stream Mapping
M
Service pack
review
email
W
Release Program
Management
derived
reqs.
Estimates
M
PRD
M
EP
Partially done
TS
Task switching
W
Waiting
Technical Support
Product Management
EP(2)
Documentum
TS(2)
M(3)
W(2)
ERR
PRD
M(3)
checklist
Remedy
Ticket
L/T = 60d
P/T = 1d
H/C = 1
S/R = >5%
Victoria Doe
D
M
EP(3)
README
QA Test
L/T = 105d
P/T = 11d
H/C = 42
S/R =
Sam Young
L/T = 24d
P/T = 4d
H/C = 3
S/R = 50%
Jen Garza
MOP
MOP
Patch
Calendar
EP
W
Change Control
EP
Rollout
Schedule
L/T = 42d
P/T =
H/C =
S/R =
Peter Lee
ERR
PD(3)
Selective
Promotion
L/T = 90d
P/T = 15d
H/C = 5
S/R =
Steve Young
New Targets
W
Server
Provisioning
Engineering
Release
M
QA Forum
Ticket
M(3)
BRD
L/T = 60d
P/T = 16d
H/C = 3
S/R = 3%
Reggie / Carlos
MOP, SOP
EP
PD
Cloud Services
Release
ERR
D
QA forum
Tasks
Motion
PD
Lockdown
control
Extra processes
M
PRD
QA
Environment
QA Forum
Ticket
Defects
EP
W
Cloud Services
Release
Memos
L/T = 45d
P/T = 21d
H/C = 140
S/R =
Bob Smith
Scrap rate
Customer
Engineering
Design
Specs
L/T = 45d
P/T = 18d
H/C = 23
S/R =
Bob Smith
Preliminary
Development
Head count
S/R
L/T = 105d
P/T = 46d
H/C = 15
S/R = 100%
John Robert
EP
Engineering
Planning
Process
Process time
H/C
Product Program
Planning
PD
M(2)
Lead time
D
Release
Schedule
L/T =
P/T =
H/C =
S/R =
Erica Smith
PRD
L/T
P/T
L/T = 28d
P/T = 7d
H/C = 1
S/R =
Stephen / Xi
crit bugs
M(2)
Current state value stream map
Customer
communication
L/T = 56d
P/T = 7d
H/C = 6
S/R = 100%
Suresh Wu
Server
Acceptance
L/T = 14d
P/T = 1d
H/C = 4.5
S/R = 15%
Lynn A. etc
Remedy
Ticket
BTS
README
Full
Development
L/T = 75d
P/T = 43d
H/C = 130
S/R =
Bob Smith
M
W(2)
Deploy Release
EP
M(2)
Commits
Build
L/T = 1d
P/T = 0.3d
H/C = 2
S/R = 33%
John Doe
Shared Drive
Test
PD(3)
Release
Promotion
L/T = 60d
P/T = 0.2d
H/C = 1
S/R = >5%
Victoria Doe
Shared
Drive Prod
Packages
XML
Single
Image
Server
L/T = 90d
P/T = 8d
H/C = 8
S/R = 2%
Lewis S./Peter Y.
M
W(2)
EP
PD
D(3)
TS
Production
BRD
54. Timeline Analysis
Core business service delivery process
Current state value stream map
Steering
Committee
Erica Switzer
Full
Projects /
Expedites
L/T
Process time
H/C
Head count
S/R
Business Analyst
Lead time
P/T
Scrap rate
Erica Switzer
D
Estimates
and
requirements
Defects
EP
Partially done
TS
Task switching
W
Erica Switzer
Motion
PD
Project Manager
Extra processes
M
Waiting
Business
Change
request
Daily Scrum
meeting
Mx3
Dx3 Develop
Request QA
build
Technical
Specification
web assets
L/T 6 weeks
P/T 4 weeks
H/C 12
S/R 5%
Bob McNulty
EP
Cut project branch
L/T 15 minutes
P/T 5 minutes
H/C 1
S/R 0%
Chris Holmes
Delta
features and
fixes
L/T 8 weeks
P/T 4 weeks
H/C 5
S/R 25%
Joe Harbaugh
Dx2
QA
Business Systems
Support
Wx2
Wx2
PDx4
Development
Build and deploy
Development
Integration testing
L/T 2 days
P/T 4 hours
H/C 1
S/R 10%
Joe Harbaugh
L/T 1 day
P/T 1 day
H/C 5
S/R 95%
Joe Harbaugh
D
Release Engineering
Stan Walters
Deployment
Document
Jira issues
TSx5
Set of
service
branches
Deployment
Meeting
RT tickets
Web Assets,
flows and
wireframes
Development
Program Management
Development
Daily Scrum
meeting
Jira issues
Creative
Change
Control Forms
Technical Operations
Change
Control
RT tickets
Release
Build and deploy
L/T 8 hours
P/T 7 hours
H/C 1
S/R 2%
Fernando Gomez
Acceptance testing
L/T
P/T
H/C
S/R
Development
Environments
Documented
test plans
and cases
W
D
D
5 days
5 hours
2
10%
Raj Lee
D
PDx3
EP
Feature testing
L/T
P/T
H/C
S/R
Tested
packages
Mx8
PD
Dx2
Deploy to
Production
Staging testing
L/T 6 days
P/T 90 minutes
H/C 3
S/R 66%
Frances Middleton
4 weeks
2.5 weeks
4
20%
Raj Lee
Deploy to Staging
L/T 1 week
P/T 3.5 days
H/C 4
S/R 66%
Frances Middleton
Mx2
EP
L/T 9 hours
P/T 8 hours
H/C 6
S/R 66%
Allen Cannata
Merge project
branch
L/T 30 minutes
P/T 30 minutes
H/C 1
S/R 33%
Fernando Gomez
PDx2
Build test plan
L/T
P/T
H/C
S/R
QA
Environments
Build test cases
5 days
4 days
1
10%
Raj Lee
L/T
P/T
H/C
S/R
Staging
Environment
2 weeks
8 days
2
20%
Raj Lee
Production
Environment
Performance
testing
Deploy to
Performance
L/T 6 days
P/T 90 minutes
H/C 3
S/R 66%
Frances Middleton
L/T 1 week
P/T 3 days
H/C 1
S/R 66%
Allen Cannata
Performance
Environment
4 weeks
4 weeks
2 weeks
4 hours
4 weeks
1 day
1.5 days
7 hours
5 hours
1 hours
2.5 weeks
4.5 days
90 minutes
1.5 weeks
3.5 days
5.75 days
Process Time
= 62 days
8 hours
1.5 days
1 hour
Lead Time =
113 days
55. Waste Analysis
Core business service delivery process
Current state value stream map
Steering
Committee
Erica Switzer
Full
Projects /
Expedites
L/T
Process time
H/C
Head count
S/R
Business Analyst
Lead time
P/T
Scrap rate
Erica Switzer
D
Estimates
and
requirements
Defects
EP
Partially done
TS
Task switching
W
Erica Switzer
Motion
PD
Project Manager
Extra processes
M
Waiting
Business
Change
request
Daily Scrum
meeting
Mx3
Dx3 Develop
Request QA
build
Technical
Specification
web assets
L/T 6 weeks
P/T 4 weeks
H/C 12
S/R 5%
Bob McNulty
EP
Cut project branch
L/T 15 minutes
P/T 5 minutes
H/C 1
S/R 0%
Chris Holmes
Delta
features and
fixes
L/T 8 weeks
P/T 4 weeks
H/C 5
S/R 25%
Joe Harbaugh
Dx2
QA
Business Systems
Support
Wx2
Wx2
PDx4
Development
Build and deploy
Development
Integration testing
L/T 2 days
P/T 4 hours
H/C 1
S/R 10%
Joe Harbaugh
L/T 1 day
P/T 1 day
H/C 5
S/R 95%
Joe Harbaugh
D
Release Engineering
Stan Walters
Deployment
Document
Jira issues
TSx5
Set of
service
branches
Deployment
Meeting
RT tickets
Web Assets,
flows and
wireframes
Development
Program Management
Development
Daily Scrum
meeting
Jira issues
Creative
Change
Control Forms
Technical Operations
Change
Control
RT tickets
Release
Build and deploy
L/T 8 hours
P/T 7 hours
H/C 1
S/R 2%
Fernando Gomez
Acceptance testing
L/T
P/T
H/C
S/R
Development
Environments
Documented
test plans
and cases
W
D
D
5 days
5 hours
2
10%
Raj Lee
D
PDx3
EP
Feature testing
L/T
P/T
H/C
S/R
Tested
packages
Mx8
PD
Dx2
Deploy to
Production
Staging testing
L/T 6 days
P/T 90 minutes
H/C 3
S/R 66%
Frances Middleton
4 weeks
2.5 weeks
4
20%
Raj Lee
Deploy to Staging
L/T 1 week
P/T 3.5 days
H/C 4
S/R 66%
Frances Middleton
Mx2
EP
L/T 9 hours
P/T 8 hours
H/C 6
S/R 66%
Allen Cannata
Merge project
branch
L/T 30 minutes
P/T 30 minutes
H/C 1
S/R 33%
Fernando Gomez
PDx2
Build test plan
L/T
P/T
H/C
S/R
QA
Environments
Build test cases
5 days
4 days
1
10%
Raj Lee
L/T
P/T
H/C
S/R
Staging
Environment
2 weeks
8 days
2
20%
Raj Lee
Production
Environment
Performance
testing
Deploy to
Performance
L/T 6 days
P/T 90 minutes
H/C 3
S/R 66%
Frances Middleton
L/T 1 week
P/T 3 days
H/C 1
S/R 66%
Allen Cannata
Performance
Environment
4 weeks
4 weeks
2 weeks
4 hours
4 weeks
1 day
1.5 days
7 hours
5 hours
1 hours
2.5 weeks
4.5 days
90 minutes
1.5 weeks
3.5 days
5.75 days
Process Time
= 62 days
8 hours
1.5 days
1 hour
Lead Time =
113 days
57. How do you develop an org’s DevOps Vision?
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
b. timeline analysis
c. waste analysis
58. How do you develop an org’s DevOps Vision?
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
b. timeline analysis
c. waste analysis
3. Develop metrics chains
59. Metrics Chains
What matters to the business
Capability that influences
what matters to the business
Activity over which an individual
can cause/influence outcomes
60. How do you develop an org’s DevOps Vision?
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
b. timeline analysis
c. waste analysis
3. Develop metrics chains
61. How do you develop an org’s DevOps Vision?
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
b. timeline analysis
c. waste analysis
3. Develop metrics chains
4. Identify projects / experiments against
baseline
62. How do you develop an org’s DevOps Vision?
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
b. timeline analysis
c. waste analysis
3. Develop metrics chains
4. Identify projects / experiments against
baseline
5. Repeat steps 2 - 4
(continuous improvement program)
63. Doing it without talking about “DevOps Vision”!
1. Teach concepts
2. Getting everyone on the same page
a. value stream mapping
b. timeline analysis
c. waste analysis
3. Develop metrics chains
4. Identify projects / experiments against
baseline
5. Repeat steps 2 - 4
(continuous improvement program)
64. Doing it without talking about “DevOps Vision”!
1. Teach concepts
2. Getting everyone on the same page
1. See the system
a. value stream mapping
b. timeline analysis
c. waste analysis
3. Develop metrics chains
4. Identify projects / experiments against
baseline
5. Repeat steps 2 - 4
(continuous improvement program)
65. Doing it without talking about “DevOps Vision”!
1. Teach concepts
2. Getting everyone on the same page
1. See the system
a. value stream mapping
2. Focus on flow
b. timeline analysis
c. waste analysis
3. Develop metrics chains
4. Identify projects / experiments against
baseline
5. Repeat steps 2 - 4
(continuous improvement program)
66. Doing it without talking about “DevOps Vision”!
1. Teach concepts
2. Getting everyone on the same page
1. See the system
a. value stream mapping
2. Focus on flow
b. timeline analysis
c. waste analysis
3. Recognize feedback loops
3. Develop metrics chains
4. Identify projects / experiments against
baseline
5. Repeat steps 2 - 4
(continuous improvement program)
67. Doing it without talking about “DevOps Vision”!
1. Teach concepts
2. Getting everyone on the same page
1. See the system
a. value stream mapping
2. Focus on flow
b. timeline analysis
c. waste analysis
3. Recognize feedback loops
3. Develop metrics chains
4. Identify projects / experiments against
4. Look for continuous
baseline
improvement opportunities
5. Repeat steps 2 - 4
(continuous improvement program)
68. While theory and high-level concepts are introduced and explained, the focus of this workshop is on
imparting practical “nuts and bolts” knowledge that attendees can use immediately in their day-today work. By Day 2, your team will be practices new techniques to analyze and diagnose your own
DevOps problems. By Day 3, your team will be identifying potential solutions and building an
improvement roadmap.
Important Tool: Workshops
Day 2
Day 3
Morning Sessions:
• Analyzing Your Current State
Morning Sessions:
• Process Improvement and
Automation Toolchain Design
Principles
• Solutions Discussion
Agenda
Day 1
Morning Sessions:
• Welcome and Kickoff
• Raising the Bar: Trends and
High Performance
• Case Study
• Anti-Patterns
Lunch
Lunch
Afternoon Sessions:
• Successful Design Patterns
• Organization and Process
• Technical
• Learning to See: Analyzing
and Diagnosing Problems
Afternoon Sessions:
• Problem Identification
Techniques
• Improvement Metrics
• Technical Deep Dive
Lunch
Afternoon Sessions:
• Solutions Discussion (cont’d)
• Project Listing and Roadmap
Building
Wrap-up
= Principles
= Analysis
= Design