There in an obsessions to jump to implementation of CI, CD tools when we talk about DevOps. In this talk, I focus on the many aspects that one needs to focus on when going on a DevOps journey
DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue
In this whitepaper, we will deep dive into the concept of continuous integration, continuous delivery and continuous deployment and explain how businesses can benefit from this. We will also elucidate on how to build an effective CI/CD pipeline and some of the best practices for your enterprise DevOps journey.
Understand why we keep missing deadlines; what is the element that keeps making us give incorrect dates and how we can estimate better with mathematical basis!
An introduction to the concepts behind Continuous Delivery as well as an introduction to some of the tools available for implementing continuous delivery practices on a new project. This presentation is geared towards Java developers, but is applicable to all.
Matt Callanan takes the 15 chapters of the famous "Continuous Delivery" book by Jez Humble & Dave Farey and distills it down into 1 hour of convincing arguments, walking through the pieces involved to make it happen including cultural challenges, automated testing, automated deployment & deployment pipelines. Not sure how to get started with DevOps? Finding it hard to convince colleagues & managers that CD is the way forward? Matt has used this presentation to help facilitate enterprise-wide adoption of Continuous Delivery. Slides from a presentation given at DevOps Brisbane March 2014.
From Continuous Integration to Continuous Delivery and DevOpsLuca Minudel
An overview of Continuous Delivery from a business and a technical point of view.
Includes an overview of:
- business value proposition of CD
- prerequisites and tips for CD implementation
- CD implementation was stories and strategies
- CD technical practices
DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue
In this whitepaper, we will deep dive into the concept of continuous integration, continuous delivery and continuous deployment and explain how businesses can benefit from this. We will also elucidate on how to build an effective CI/CD pipeline and some of the best practices for your enterprise DevOps journey.
Understand why we keep missing deadlines; what is the element that keeps making us give incorrect dates and how we can estimate better with mathematical basis!
An introduction to the concepts behind Continuous Delivery as well as an introduction to some of the tools available for implementing continuous delivery practices on a new project. This presentation is geared towards Java developers, but is applicable to all.
Matt Callanan takes the 15 chapters of the famous "Continuous Delivery" book by Jez Humble & Dave Farey and distills it down into 1 hour of convincing arguments, walking through the pieces involved to make it happen including cultural challenges, automated testing, automated deployment & deployment pipelines. Not sure how to get started with DevOps? Finding it hard to convince colleagues & managers that CD is the way forward? Matt has used this presentation to help facilitate enterprise-wide adoption of Continuous Delivery. Slides from a presentation given at DevOps Brisbane March 2014.
From Continuous Integration to Continuous Delivery and DevOpsLuca Minudel
An overview of Continuous Delivery from a business and a technical point of view.
Includes an overview of:
- business value proposition of CD
- prerequisites and tips for CD implementation
- CD implementation was stories and strategies
- CD technical practices
The presentation from my talk on Continuous Integration and Builds at XP Days Indore 2010. The target audience was MCA students, faculty and members of IT industry in and around Indore.
Why your company loves to welcome change but sucks at accommodating itFarooq Ali
The need for sound engineering practices in Agile. A look at a very common Agile anti-pattern (Flaccid Scrum) found in large organizations, and how to fix it.
Devops at SlideShare: Talk at Devopsdays Bangalore 2011Kapil Mohan
Presentation for the talk at Devopsdays Bangalore 2011 (August 26th & 27th)
This is about why we embraced devops at SlideShare and our experiences, achievements and insights in adopting devops.
What is DevOps? | DevOps Introduction | DevOps Tools | DevOps Tutorial For Be...Simplilearn
This presentation on DevOps will help you understand what is DevOps, how DevOps came to being, stages and tools of DevOps, implementation of DevOps, DevOps practices, benefits of DevOps approach and at the end, you will also see a use case of DevOps approach by Etsy. DevOps is a software engineering culture that unifies the development and operations team, under an umbrella of tools to automate every stage. The benefits of DevOps outweigh the potential difficulties. Aligning the two transparency-limited silos ensures that systems are delivered faster, and also reduces risks in production changes through nonfunctional and automated testing, as well as shorter developmental iterations. The DevOps approach automates the service management for the support of operational objectives and improves understanding of the layers in the production environment stack. In turn, this helps prevent and resolve production issues. Now, lets deep dive into these slides and understand what actually DevOps is.
Below topics are explained in this DevOps presentation:
1. How DevOps came to being
2. What is DevOps?
3. Stages and tools of DevOps
4. Implementation of DevOps
5. DevOps practices
6. Use case: DevOps approach by Etsy
7. Benefits of DevOps approach
Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become en expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today.
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach.
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit to the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at https://www.simplilearn.com/
Recently I was asked to explain what dev-ops is at a large enterprise software vendor undergoing transformation.
In these slides, I present the concepts, tools and mindset that drive DevOPS.
(Talk given at Continuous Lifecycle London 2016)
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not funding the build/test/deployment capability properly
- No effective logging or application metrics
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
Integrating hardware development processes (using the Waterfall method / V-model) and Agile software development. This presentation explains the basics of the V-model and how it has evolved into an iterative model, but also tells you about managing hardware and software lifecycle processes in a single release. Then, a live demonstration shows you how to integrate these lifecycles (xLM) in practice.
Shift left as first transformation step into Quality AssuranceZbyszek Mockun
Do you work in a company which has established effective testing process, which ensure high quality and support Agile methodologies? Can your testing process be used as a model for other companies? Fortunately, we were in that place a few years ago and had to ask ourselves a question about the next step. The answer was: Let’s be Quality Assurance Engineers rather than Testers. But what should we do? How can we do this transformation?
At the same time, I got feedback from my colleague – Head of Java practice: “Your testers found defects in areas / scenarios which weren’t included in development scope / my devs didn’t know that should cover those edge cases. What can we do with that?”
I had to agree with him. There is no sense to test scenarios which weren’t implemented. This was the starting point of our transformation. We decided to implement Shift left model as it looks like the most promising one. But when we implemented it not everything worked as smooth as we wished. New challenges appeared, but more in my presentation.
Continuous Integration and Continuous Deployment in Enterprise scenarioDavide Benvegnù
The presentation about Continuous Integration and Continuous Deployment during the Microsoft DevOps Breakfast.
General info about CI and CD.
Demo with Visual Studio Team Services (apply also too TFS)
DevOps is a software development method which is all about working together between Developers and IT Professionals. This presentation gives you an introduction to DevOps.
Best Practices for a Repeatable Shift-Left CommitmentApplause
Applause testing experts discuss the challenges of shifting left and innovative new ways to enable teams to eliminate the impact of manually validating new functionality immediately after a new feature is coded.
The presentation from my talk on Continuous Integration and Builds at XP Days Indore 2010. The target audience was MCA students, faculty and members of IT industry in and around Indore.
Why your company loves to welcome change but sucks at accommodating itFarooq Ali
The need for sound engineering practices in Agile. A look at a very common Agile anti-pattern (Flaccid Scrum) found in large organizations, and how to fix it.
Devops at SlideShare: Talk at Devopsdays Bangalore 2011Kapil Mohan
Presentation for the talk at Devopsdays Bangalore 2011 (August 26th & 27th)
This is about why we embraced devops at SlideShare and our experiences, achievements and insights in adopting devops.
What is DevOps? | DevOps Introduction | DevOps Tools | DevOps Tutorial For Be...Simplilearn
This presentation on DevOps will help you understand what is DevOps, how DevOps came to being, stages and tools of DevOps, implementation of DevOps, DevOps practices, benefits of DevOps approach and at the end, you will also see a use case of DevOps approach by Etsy. DevOps is a software engineering culture that unifies the development and operations team, under an umbrella of tools to automate every stage. The benefits of DevOps outweigh the potential difficulties. Aligning the two transparency-limited silos ensures that systems are delivered faster, and also reduces risks in production changes through nonfunctional and automated testing, as well as shorter developmental iterations. The DevOps approach automates the service management for the support of operational objectives and improves understanding of the layers in the production environment stack. In turn, this helps prevent and resolve production issues. Now, lets deep dive into these slides and understand what actually DevOps is.
Below topics are explained in this DevOps presentation:
1. How DevOps came to being
2. What is DevOps?
3. Stages and tools of DevOps
4. Implementation of DevOps
5. DevOps practices
6. Use case: DevOps approach by Etsy
7. Benefits of DevOps approach
Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become en expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today.
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach.
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit to the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at https://www.simplilearn.com/
Recently I was asked to explain what dev-ops is at a large enterprise software vendor undergoing transformation.
In these slides, I present the concepts, tools and mindset that drive DevOPS.
(Talk given at Continuous Lifecycle London 2016)
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not funding the build/test/deployment capability properly
- No effective logging or application metrics
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
Integrating hardware development processes (using the Waterfall method / V-model) and Agile software development. This presentation explains the basics of the V-model and how it has evolved into an iterative model, but also tells you about managing hardware and software lifecycle processes in a single release. Then, a live demonstration shows you how to integrate these lifecycles (xLM) in practice.
Shift left as first transformation step into Quality AssuranceZbyszek Mockun
Do you work in a company which has established effective testing process, which ensure high quality and support Agile methodologies? Can your testing process be used as a model for other companies? Fortunately, we were in that place a few years ago and had to ask ourselves a question about the next step. The answer was: Let’s be Quality Assurance Engineers rather than Testers. But what should we do? How can we do this transformation?
At the same time, I got feedback from my colleague – Head of Java practice: “Your testers found defects in areas / scenarios which weren’t included in development scope / my devs didn’t know that should cover those edge cases. What can we do with that?”
I had to agree with him. There is no sense to test scenarios which weren’t implemented. This was the starting point of our transformation. We decided to implement Shift left model as it looks like the most promising one. But when we implemented it not everything worked as smooth as we wished. New challenges appeared, but more in my presentation.
Continuous Integration and Continuous Deployment in Enterprise scenarioDavide Benvegnù
The presentation about Continuous Integration and Continuous Deployment during the Microsoft DevOps Breakfast.
General info about CI and CD.
Demo with Visual Studio Team Services (apply also too TFS)
DevOps is a software development method which is all about working together between Developers and IT Professionals. This presentation gives you an introduction to DevOps.
Best Practices for a Repeatable Shift-Left CommitmentApplause
Applause testing experts discuss the challenges of shifting left and innovative new ways to enable teams to eliminate the impact of manually validating new functionality immediately after a new feature is coded.
Agile Transformation: People, Process and Tools to Make Your Transformation S...QASymphony
Many companies are currently going through Agile Transformation or thinking about making the transition to agile. While moving to agile can create great opportunity for organizations, the journey to get there can be highly challenging. If you don’t have the right people, process and tools in place, the true benefits of agile may not be recognized. In this webinar, Andrew Stickland, Head of Client Services, for Clearvision and Kevin Dunne, VP of Business Development and Strategy for QASymphony will discuss the best practices for making the agile transformation. In this webinar, we will try to answer the following questions:
- Who are the people I need in place?
- What are the core processes that I need to change?
- What tools do I need?
View the On-Demand webinar here: http://pi.qasymphony.com/agile-transformation-best-practices-webinar-lp060?utm_source=slideshare&utm_medium=slideshare&utm_campaign=Agile%20Transformation%20Webinar
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
sitHH16 - The Implications of Becoming AgileMarkus Theilen
Slides from my talk about the not so obvious changes that occur when change from waterfall to agile software development with Scrum. A review on the past three years in an agile transition.
Scaling Frame Works are great guideline for Scaling Agile but teams and companies who are working Scrum and/or Kanban for sometime now can scale Agile Implementation following certain disciplines and structural approached and . This talk is to discuss one such implementation.
Lean Kanban India 2017 | Case study - Hybrid Agile Implementation Model to En...LeanKanbanIndia
Session Title: Case study - Hybrid Agile Implementation Model to Enable Enterprise Agility in 9 months (with focus on Kanban and Flow Management)
Session Overview: In this session we will present a detailed case study of implementing agile @ scale in a unique way to enable business agility in a large software product group of ~1500 people that develops large integrated enterprise product. Our model has great amount of focus on Kanban and Flow management – from teams to program to portfolio. The unique hybrid implementation model was developed to handle challenges as: dependencies across various product groups while some working in agile and some not; coaching limitation that do not allow to coach all the groups at once; legacy product (~ 15 years) with veteran managers (culture and support); distributed development (5 locations in India) and last, high business pressure to respond fast to changes. In 9 months with team of 5 agile coaches we achieved most of our business goals (feature cycle time reduced by 50%, time to market by 60%, throughput by 30% and dramatic improvement in quality). In our session we will describe our hybrid approach in implementing agile in scale for fast results.
How to Build in Quality from Day 1 using Lean QA and Agile TestingAtlassian
If you're struggling to implement QA methods that fit with agile's core principles, you're not alone. Join Giancarlo and Maurizio as they explain how their teams found a sweet spot at the intersection of agile and QA engineering. They'll share common pitfalls and how to avoid them. Plus, get tips and tricks on how to capture requirements and link JIRA to test repositories for complete traceability.
In the world of agile, there is theory and then there is practice. We like to talk about self-organizing teams, asynchronous execution, BDD, TDD, and emergent architecture. We also talk about cross-functional teams: how analysts, testers, architects, technical writers, and UX designers belong on the same team, right next to programmers. It all sounds nice in theory, but how does this work in reality? What do these people actually do? How do they interact? What does it look like? Is there really a pragmatic way to make this work?
In this simulation, a cross-functional team will actually build a piece of software. Every specialist will have a hand in the process. Every specialist will also act as a generalist. Everyone will add value. And as a team, we’ll get something DONE.
This is your opportunity to see agile development in practice, and to bridge the gap between what agilists say and what teams do. And it’s not as new or as difficult as you think – affinity between testers, BA’s, coders, and other team members has really been at the root of effective development practices all along. Let’s just finally acknowledge that it works, demonstrate its capabilities, and encourage it going forward.
This IS agile development.
Session Title : Intelligent DevOps enabling Enterprise Agility through power of Automation and Cognitive Intelligence
Session Overview : Digital transformation has mandated convergence of Business and IT to bring organization agility in true sense. Business has been focusing to optimize business processes. IT adopted DevOps to accelerate Collaboration and Automation to drive Speed to Market (Development priorities) and Availability/ Stability/ Performance etc. (IT Operations priorities).
Automation has broader perspective, which includes DevOps ( just-in-time software release) and Robotic Process Automation aka RPA ( just-in-time business process automation) to create best-in-class business outcomes for their enterprises.
Time has come to take next steps towards Continuous journey (Continuous Integration, Continues Testing, Continuous Deployment, Continuous Operations etc.) of DevOps to become Intelligent i.e. Intelligent Integration, Intelligent Testing, Intelligent Deployment and Intelligent Operations.
AgileDC15 I'm Using Chef So I'm DevOps Right?Rob Brown
Introduce DevOps to the uninitiated
Demystify the terminology and techno-centric jargon
Provide an assessment model that you can take back to your organization to help establish a baseline of behaviors and practices, and guidance on moving towards more of a DevOps culture
This slidedeck how Program Management as teams and organizations Agile thinking. It helps understand both qualitative and quantitative aspects of Program Management.
Flow - the secret sauce for business agilitySudipta Lahiri
We discuss how Flow is essential to improving an organization's ability to improve its Agility. We discuss two dimensions of flow - flow of work and people experiencing flow. We discuss some of the impediments for both these dimensions and how one could work through them.
Digital transformation for the next decadeSudipta Lahiri
In this talk, I cover the Digital Transformation trends that we will see in the next decade in the context of the changes that we can expect to see in the environment around us. We then talk about how do organizations need to prepare to be able to take advantage of these trends.
Estimation - Delivering Business Agility without EstimationSudipta Lahiri
In this presentation, we explain how Estimation used to be done, its futility, what insights do we learn from the Lean-Agile BoK and how Agility can be delivered without Estimation. Business Leaders still need an understanding of effort, cost and timeline... and all these can be delivered without wasting time on Estimation.
Getting requirements right for business agilitySudipta Lahiri
In this slidedeck, we help explain how our messaging to the Leadership team, that is largely experienced in conventional ways of software development, must change to help them understand how Lean-Agile thinking drive Business Agility. This specific presentation is focussed on how the messaging around Requirements needs to change!
There is a lot of discussion around changing the team mindset! Its become boring... question is - how do you go about doing it. In this presentation that I did at ANI's Online Conference for Team Mindset, I highlight some of things that we did at Digite to help individuals (and teams) make that shift. I am sure different organizations have tried many other things but if you try these, I am confident it would take you a small step forward.
Upstream: Shifting-left towards organization agilitySudipta Lahiri
In this talk, I explain how focusing on Upstream helps the team's move forwards it's objective of Organization Agility. I start by explaining Upstream (vs Downstream), some of it characterestics, the criteria of a good Upstream execution. I finish the talk with prioritisation techniques that can be used in the Upstream process.
Flow Debt is a concept for Kanban systems to understand why CT histograms do not get better despite taking a lot of the obvious steps. Hope you find this useful.
In this Keynote given at Agile Gurugram 2018, I discuss the importance of VSM to Lean/Agile transformation. I explain common areas of confusion and highlight best practices around application of VSM to Knowledge Services.
I gave this presentation at Agile Noida 2016. Toyota Kata, as articulated by Mike Rother, is an approach to establish a culture of Continuous Improvement. In this talk, I have tried to identify a few simple practices that Lean/Agile teams can adopt to help establish a Continuous Improvement culture.
I recently gave a KeyNote presentation at Agile Noida 2014. This is the presentation that I used there and talks about Personal Kanban and its effectiveness.
This is a training that I conducted on Agile Testing. There is a lot of confusion around how Testing Professionals are impacted when they move from Traditional development models to Agile development models. This training attempted to clear some of the confusion around that.
Training - Introducing Agile, Lean and KanbanSudipta Lahiri
This is a presentation that I did for a team to introduce them to Agile, Lean and Kanban, It covers these these 3 areas, how they overlap and then gets into greater details about the Kanban Method.
I recently spoke at Symbiosis University on how WCM (World Class Manufacturing) is being applied to the software industry.
World Class Manufacturing [WCM] is the collective term for the most effective methodologies and techniques to realize the objectives of: A) Products of consistent high quality B) Delivery on Time of the desired quantity and C) Product at the lowest cost. The commonly knows WCM methodologies and techniques are TPM, Kaizen, TQM, Six Sigma, JIT, and Lean Manufacturing.
This presentation shares how the software industry and been adopting many practices from the above techniques over the last decade.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
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.
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.
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.
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
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
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.
Unsubscribed: Combat Subscription Fatigue With a Membership Mentality by Head...
Dev ops is more than CI+CD tools
1. DEVOPS >
CI + CD (TOOLS)
S U D I P TA L A H I R I
D I G I T É
AG I L E G U R U G R A M 2 0 1 7
2. @sudiptal
QUICK INTRODUCTION…
• Sudipta Lahiri (Sudi)
• 27+ years in the industry
• Agile/Lean practitioner (85%) + Agile/Lean Student (15%)
– Head of Products @ Digité
– ex-Head of Engineering and Professional Services @ Digité
– Development of SwiftKanban and SwiftALM products
• Organize the LimitedWIP Societies in India
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
3. WHY DEVOPS?
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
4. @sudiptal
SETTING THE CONTEXT…
• From the manifesto: Early continuous delivery of valuable
software!
• What would be a single KPI if you want to focus on this
objective?
– Lead time (LT): From the time when the customer gave you some
idea of what he/she wanted, how long did it take him/her to get it?
• Keeping focus on LT helps all teams come together to server
common objective: customer!
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
5. @sudiptal
HOW DO WE BRING LEAD TIME DOWN?
Ideation to Specification
(including the front end)
Specification
to Dev
Complete
Dev
Complete to
Production
Deployment
Agile
methods
focus here.
DevOps extends the spectrum
Can we make this a non-
issue by putting adequate
processes and infrastructure
in place?
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
7. @sudiptal
NET RESULT: TRIPLE CONSTRAINT
BUSTED! • Agile Methods/DevOps
establish the opposite
– We can deliver the highest
quality in the least time with
the least effort (minimize
waste)
– Slam dunk in green field
development initiatives
– Takes times with legacy
systems
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
8. @sudiptal
WHAT MAKES HIGH PERFORMANCE IT
ORGANIZATIONS?
Continuous
Delivery
Lean
Management
Practices
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
9. @sudiptal
CONTINUOUS DELIVERY:
MAKES WORK BETTER AND MAKE IT “FEEL” BETTER
Test Deployment
and
Automation
Continuous
Integration
(All) Production
artefacts in
Version Control
Continuou
s
Delivery
IT
Performanc
e
Lower
Deploymen
t Plan
Lower
Change Fail
Rates
Organizatio
n
Performanc
e
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
10. @sudiptal
LEAN MANAGEMENT PRACTICES:
MAKES WORK BETTER AND MAKE IT “FEEL” BETTER
WIP Limits:
Drive
Improvement
Visualisations to
monitor work
Monitoring to
make business
decisions
Lean
Managemen
t
IT
Performanc
e
Decreased
Burnout
Improved
Organizatio
n Culture
Organizatio
n
Performanc
e
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
11. WHY IS IT
DIFFICULT?
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
13. @sudiptal
FROM THE “CULT” CLASSIC:
3 TAKEAWAYS • DevOps is applied kanban. To run
DevOps well, you must understand
kanban.
• DevOps is not a collection of
tools
• If your people are 100% utilized,
you are introducing waste
http://daveondevops.com/2016/03/17/takeawaysfromphoenixproje
14. SO, WHAT’S
BEYOND CI+CD
(TOOLS)?
What are the CSFs?
DRIVEN BY FOCUS ON LEAD TIME!
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
15. CONTINUOUS
DELIVERY
YO U R W O R K P R O D U C T I S A LWAY S R E A D Y
F O R D E L I V E R Y
E X C LU S I O N S : L E A N M A N AG E M E N T
P R AC T I C E S , C U LT U R E
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
16. @sudiptal
“ALWAYS DEPLOYABLE” MEANS…
• Ability to get changes (features, configuration changes, bug
fixes, experiments) into Production, safely, quickly and sustain
it
– Make Releases boring; no one stays awake at night!
– No need to use the latest tools; bring people together to get this
done
– Not just functionally ready – it should be ready with all NFR
requirements (performance, security)
• Eliminate integration, testing and hardening
– A good 5-10% of the overall Lead Time@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
17. HOW DO WE GET
THERE?
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
18. 1. QUALITY
IMPROVING QUALITY IS
EVERYONE’S RESPONSIBILITY
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
19. @sudiptal
THE QUALITY BIBLE:
DEMING’S 14 POINTS ON QUALITY MANAGEMENT
• Create constancy of purpose for improving products and services.
• Adopt the new philosophy.
• Cease dependence on inspection to achieve quality; eliminate
inspection; BUILD QUALITY INTO THE PRODUCT IN THE FIRST
PLACE
• End the practice of awarding business on price alone; instead, minimize
total cost by working with a single supplier, on a long term relationship
of loyalty and trust!
• Improve constantly and forever every process for planning, production
and service.
• Institute training on the job.
• Adopt and institute leadership.
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
20. @sudiptal
THE BIBLE:
DEMING’S 14 POINTS ON QUALITY MANAGEMENT
• Drive out fear.
• Break down barriers between staff areas.
• Eliminate slogans, exhortations and targets for the workforce.
• Eliminate numerical quotas for the workforce and numerical goals for
management; eliminate MBO
• Remove barriers that rob people of pride of workmanship, and eliminate
the annual rating or merit system. The responsibility of supervisors must
be changed from sheer numbers to quality.
• Institute a vigorous program of education and self-improvement for
everyone.
• Put everybody in the company to work accomplishing the
transformation. Transformation is everyone’s job!
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
21. @sudiptal
WHAT DOES IT MEAN TO US?
• There is no Agility/DevOps with crappy software
• There is no Agility/DevOps with manual test regression of
days/weeks/months
• There is no Agility/DevOps with Dev and Ops in their own cocoons,
with handoffs from one team to another
• Developers should be writing tests; if you don’t have this, you are
not ready for DevOps
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
22. @sudiptal
WHAT TO DO?
• Treat Tests as first class citizens of
your project
– Use tools to build and manage
them… just like you do with your
source code
• Follow Agile Testing body of
knowledge
– If needed, get rid of the separate
Testing team; Dev understands that
there is no insurance to cover them
for their crappy code!
– Inverted Testing Pyramid is a non-
starter!
• Revitalize the tester
– Tester is a role; not a person
• Definitely, not a failed developer
– Advocates for the user; makes
quality transparent
– Preferably, not doing manual testing
• Focussed on exploratory testing +
maintaining automated acceptance
test cases
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
23. @sudiptal
AGILE TESTING QUADRANTS
Diagram invented by Brian Marick
Unless you do TDD,
test automation
post deployment is
expensive and hard
Cannot automate
this stuff! You need
people…
Should be doing this
from the beginning.
These things are
testing the architecture.
You need to know if
you have this right
24. @sudiptal
TEST DATA MANAGEMENT
• Suffers from low focus on (compared to Test Automation)
• Need adequate test data + ability to create test data on demand
• Choose low volume test data combinations that cover large
volume scenarios
– Avoid loading/unloading of DB dumps
– Don’t use production data dumps (except for Staging and Performance)
– Start from a clean DB and programmatically create data using the
application APIs => Works nicely with an automation led strategy
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
26. @sudiptal
ACCEPTANCE TESTING
• Writing “good” acceptance test
cases is hard
• Its “good” IF you have the
confidence in the quality of the
software when Acceptance Test
Cases pass
• If you get failure, introduce an
automation script at the right
level
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
27. @sudiptal
ACCEPTANCE TEST SUITES
• Very hard to maintain
• Decay over time..
– Just like code! Refactor relentlessly
• Ownership is always the issue
– Not owned by the tester but by
the team!
• Treat test code as Production
• Flaky tests are no good!
– You lose the trust in your existing
Test Suite
– Move them to a different test suite
– Quarantine them till they are
refactored and consistent
• External Systems
– Move to a separate suite
– Parameterize the connections
– Run them before the full
acceptance suite
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
28. @sudiptal
BROWSER BASED TESTING IS UNRELIABLE
• If you hear “it failed in CI… but it ran manually”, you know
there is a difference between test mechanics and interaction
pattern
• If you have AJAX based testing where tests need to wait for a
response from the server, then you will run into issues
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
29. @sudiptal
PERSONA BASED USER-JOURNEYS
• Persona based user-journeys
– Extract them from existing Acceptance Test Cases
– Move to server side testing (away from browser based UI testing)
– Journey should only cover the most likely path
• Extract negative/edge scenarios to a separate suite to run after the journey
scenarios are done
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
32. @sudiptal
CONWAYS LAW
• Organizations which design systems are constrained to
produce designs which are copies of the communication
structures of these organizations
• If you don’t want your product to look like your organization,
change your organization or change you product
Rebecca Parsons
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
34. @sudiptal
AMAZON’S DIRECTIVE TO ITS TEAMS…
• All teams will henceforth expose their data and functionality through service
interfaces.
• Teams must communicate with each other through these interfaces.
• There will be no other form of interprocess communication allowed: no direct
linking, no direct reads of another team's data store, no shared-memory
model, no back-doors whatsoever. The only communication allowed is via
service interface calls over the network.
• It doesn't matter what technology they use. HTTP, Corba, Pubsub, custom
protocols -- doesn't matter. Bezos doesn't care.
• All service interfaces, without exception, must be designed from the ground up
to be externalizable. That is to say, the team must plan and design to be able
to expose the interface to developers in the outside world. No exceptions.
• Anyone who doesn't do this will be fired.
https://plus.google.com/+RipRowan/posts/eVeouesvaV
35. @sudiptal
YOU BUILD IT, YOU RUN IT!
“… Giving developers operational responsibilities has greatly
enhanced the quality of the services, both from a customer and a
technology point of view. The traditional model is that you take your
software to the wall that separates development and operations,
and throw it over and then forget about it. Not at Amazon. You
build it, you run it. This brings developers into contact with the day-
to-day operation of their software. It also brings them into day-to-
day contact with the customer. This customer feedback loop is
essential for improving the quality of the service.”
Werner Vogels, CTO, Amazon
June 2006
http://queue.acm.org/detail.cfm?id=114206
36. @sudiptal
ARCHITECTING FOR
REMOTE APPLICATIONS
• Circuit Breakers: handle remote calls
• Wrap the function call in a circuit breaker
object
– Once the failures reach a threshold, it trips
– Further calls return with an error, without calling the
function
• Monitor and alert when it trips; have the
breaker itself detect when its ready again https://martinfowler.com/bliki/CircuitBreaker.html
37. @sudiptal
ARCHITECTING FOR
LEGACY APPLICATIONS
• Strangler Applications
• Start by building new
functionality in new modules,
using SOA
– Don’t rewrite existing code except
to simplify or removing bugs
– If you need to extend, write
wrappers
https://www.martinfowler.com/bliki/StranglerApplication.htm
38. @sudiptal
STRANGLER APPLICATION
• Benefits:
– Reduced risk.
– Give value steadily
– Frequent releases allow you
to monitor its progress more
carefully
– You can avoid a lot of the
unnecessary features that cut
over rewrites often generate
• For new applications:
– All new applications today
will be legacy tomorrow!
– When designing a new
application, design it in such
a way as to make it easier for
it to be strangled in the
future
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
39. @sudiptal
ARCHITECTED FOR RECOVERY
• Even the High performing organizations report failures up to 15%
– However, they can recover in <1hr
• Applications have to be designed for recovery
– Strategies could vary for the application layer to the DB layer
• If the build is broken, rollback first! You don’t need to stay up all
night or late evening to fix it.
– Take time to fix it. Fixes made in a hurry create more problems/technical
debt!
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
40. @sudiptal
OPTIMISE FOR MTRS
• Think Lead Time!
– How quickly can I detect?
– How quickly can I find the
cause?
– How quickly can I fix the
problem?
– How quickly can I rollout the
fix?
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
41. 3. CONTINUOUS
INTEGRATION
I N T E G R A T E E A R L Y A N D O F T E N
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
43. @sudiptal
ESSENTIALS FOR CI
• Maintain a Single Source
Repository.
• Automate the Build
• Make Your Build Self-Testing
• Everyone Commits To the
Mainline Every Day
• Every Commit Should Build
the Mainline on an
Integration Machine
• Fix Broken Builds Immediately
• Keep the Build Fast
• Test in a Clone of the
Production Environment
• Make it Easy for Anyone to
Get the Latest Executable
• Everyone can see what's
happening
• Automate Deployment
https://martinfowler.com/articles/continuousIntegration.html#EveryoneCommitsToTheMainlineE
44. @sudiptal
FEATURE BRANCHES + CI
FEATURE BRANCH CONTINUOUS INTEGRATION
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
45. @sudiptal
AWAY FROM (LONG LIVE) FEATURE
BRANCHES
• Most teams got driven to
Feature Based Development
– Until these explode… and they
age!
• Longer you are building in your
own branch, greater the risk of
all sorts of incompatibilities
• Move to:
– Short branches (less than a day)
– Less than 3 active branches
– Merge to trunk/master on a daily
basis
• Emphasis on main line
development
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
46. @sudiptal
SAY NO TO “LONG LIVE” BRANCHES
• Rarely needed; its value
diminishes dramatically
over time
• Avoid “environment(itis)”
Age of Branch
RealPotentialTestingValue
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
48. @sudiptal
CATEGORIES OF TOGGLES
• Release Toggles: allow incomplete and untested code paths to be
shipped to production as latent code, which might never be turned on!
• Experiment Toggles: used to perform A/B testing
• Ops Toggles: control operational aspects of the application, for e.g.,
turning down a load intensive processing when there is high transaction
load
• Permissioning Toggles: change features that certain users receive, for
e.g., for a set of internal users (“Champagne Brunch”)
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
49. @sudiptal
CATEGORIES OF TOGGLES
• Static toggles OR Short
longevity Toggles would
need a simple on/off
configuration
• Dynamic or High Longevity
Toggles need sophisticated
“Toggle Routers”
https://martinfowler.com/articles/feature-toggles.htm
50. @sudiptal
TOGGLE ROUTING
• Prefer static routes that are
baked into the source code
via configuration
– All the benefit of infra as a code
– Simpler testing
• Dynamic Toggle Routing
patterns
– Hard coded toggle
configuration
– Parameterised toggle
configuration (command line or
env variables)
– Toggle Configuration file
– Toggle via App DB
– Overriding configuration
• Per request overrides
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
51. @sudiptal
FEATURE TOGGLES ADD TESTING
COMPLEXITY
• Both options need to be
tested for each Toggle!
• (Might) explode with multiple
toggles options!
– Use Toggle Configuration files
– Add meta-data to track
audit/governance information
for that toggle
– In general, there's no need to
test all combinations of
features.
• For release toggles, test 2
combinations
– All toggles on that are
expected to be on in the next
release
– All toggles on
• Build an ability to generate
the listing of all the “active”
toggles on the runtime
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
52. @sudiptal
TOGGLE COME AT A COST!
• View the Feature Toggles as inventory
– There is a carrying cost; keep this inventory as low as possible.
• Team must be proactive in removing feature toggles; retire then
when pending feature are bedded to Production
– Add a toggle removal task onto backlog whenever it is introduced
– Put "expiration dates" on toggles.
• Creating "time bombs" that will fail a test (or even refuse to start an application!) if
a toggle is still around after its expiration date
– Apply a Lean approach by placing a limit on the number of toggles
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
53. 4. DEPLOYMENT
PIPELINE
D E P L O Y M E N T I S T H E F I N A L S T A G E O F
C I
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
55. LOW RISK RELEASE
PATTERNS
Y O U H A V E T O A R C H I T E C T F O R T H E S E !
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
56. @sudiptal
DEPLOYING DB CHANGES
• If you want to
• Then
– Make the DB change in the 1st release by adding the incremental fields
– The UI does a conditional read; if new field is blank, read from the old field
– The UI always writes to both fields.
– Now, introduce the new feature... if it fails, you are ready to rollback
immediately,
– Much later, delete the old field (called the "contract" phase).
Address Address1 Address2
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
57. @sudiptal
CI FOR DB
• Data is persistent
• Often, large datasets;
rollback is not an option
– Some changes are
irreversible
• Make DDL/DML scripts part
of version control
– In test environment, build DB
from scratch
– Then, run acceptance test
cases
• Scripts are ordered; they
run in a sequence
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
58. @sudiptal
DEPLOY ON PRODUCTION
• Apply the same scripts on
Production
• Incremental scripts to be pulled
from version control
• For each script, build the
rollback script (as far as
possible)
• Check dbdeploy.com
• Maintain a metadata table that
indicates what scripts have been
run on it
• Logs success/failure
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
59. @sudiptal
BLUE-GREEN DEPLOYMENTS
• Deployments often become a batch
operation waiting for the next “good” time
• Solution: Blue Green deployments
• Minimizes cutover from one version to
next; Fast rollback if needed
• Use the “other” as staging environment
• Multiple approaches to handle “live”
transactions on the earlier system
https://martinfowler.com/bliki/BlueGreenDeployment.htm
• For Database Changes:
– Separate from the application rollout
– Use the earlier pattern
60. @sudiptal
RELEASE != DEPLOYMENT
• Deployment might release to all environments at the same
time.
• Release process controls who sees what
– In FB, this person is called “Gatekeeper”
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
63. @sudiptal
DEFINE THE ENVIRONMENT
• What it is?
• What to use it for?
• How long to retain that environment?
• All environments are an “approximation” of the Production
– Hence, it is only good for a purpose – not good for any other
purpose
– That defines the “What to use it for?”
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
64. @sudiptal
INFRASTRUCTURE
• All environment and supporting
services
– Networking, Storage, Mail, DNS…
• Desired state in version control
• Self corrects to the desired state
(Autonomic)
• State should be known via
continuous monitoring
• Protect from “Configuration
Drift”
– Adhoc changes to the system that go
unrecorded
– Test yourself like a “Fire Drill”
• Solution:
– Use Software that automatically syncs
with a “baseline”
– Limited to the extent that you have
artefacts under version control
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
65. @sudiptal
THE TALE OF 2 COMPANIES…
http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.h
66. @sudiptal
“…it takes about 80 hours to bootstrap a startup. This generally
means installing and configuring an automated infrastructure
management system (puppet), version control system
(subversion), continuous build and test (frequently cruisecontrol.rb),
software deployment (capistrano), monitoring (currently
evaluating Hyperic, Zenoss, and Groundwork). Once this is done the
“install time” is reduced to nearly zero and requires no specialized
knowledge.”
Jesse Robbins
(ex) Master of Disaster, Amazon
Founder of Chef
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
67. @sudiptal
THE NEXTFLIX SIMIAN ARMY
https://insights.sei.cmu.edu/devops/2015/04/devops-case-study-netflix-and-the-chaos-monk
68. @sudiptal
AMAZON GAME DAYS
• Inject failures into critical
systems
• Discover flaws and critical
dependencies
• Accept that reliable software
platform is built on top of
components that are
unreliable
• Need to keep testing services
against failure all year around
• Fail systems that will need to
bring people together who
otherwise don’t interact with
each other
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
69. @sudiptal
RESILIENCE ENGINEERING:
A FUNDAMENTAL CULTURAL SHIFT
• From a steadfast belief that
systems should never fail—and
if they do, focusing on who's to
blame—to actually forcing
systems to fail
• Rather than expending
resources on building systems
that don't fail, the emphasis is
to how to deal with systems
swiftly and expertly once they
do fail—because fail they will.
• Much of the value comes from
changing the collective mindset
of the engineers who design
and build
– It's not easy to watch their systems
fail and its consequences
– Overtime, they gain confidence in
the systems and practices
• It invokes a more just culture in
which people can be held
accountable without being
blamed, or punished, for failure.
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
70. SOME OTHER
THOUGHTS…
… T H A T I C O U L D N ’ T F I T A N Y W H E R E E L S E !
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
71. @sudiptal
PRACTICES
• Developers should be able to run acceptance tests on their
environments
• Virtualize all environments
• If anything fails, stop the line!
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
72. @sudiptal
PITFALLS
• Configuration(itis)!
– Once you start automating your
configurations, you will see an
explosion in the same
– For every small incremental
functional OR NFT, you will get a
request for a new configuration…
and then, these will stay
– Set some STANDARDS and
governance around this (similar to
temporary branching)!
• What should be a standard env
for Test, Staging, including test
data
• Ops people are generally
automation savvy
– Don’t get too obsessed with
frameworks, trying to make it too
generic
– Don’t build a huge framework with
tons of scripts and tools! Don’t have
hundreds of metadata config points
that becomes a nightmare to manage
• Don’t create Configuration
Management “Sherpas” whose only
job is to manage and track
configuration
– Avoid your Brent!@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
73. @sudiptal
PITFALLS
• Change in a “stealth” mode:
– Just start by saying that you are
automating what you do today; one
organization called “Rapid Release”
– Don’t take the message “we will change
everything”
– Fast delivery in a safe way keeping all the
gray suits/ITIL happy!
– Focus on better work-life balance for
everyone
• If you are starting your DevOps
initiative with tools, you are almost
certain to fail
• Event and Alert monitoring:
– With an explosion of tools and
environments, it will be a nightmare to
analyse and track all that is happening
– Get all feeds into one activity stream like
Slack
– Build parsers to filter out what you really
want to see
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
74. IN CLOSING…
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
75. @sudiptal
• Think lean: shorten Lead Time by focussing on the full value
stream
• Don’t look at Agile and DevOps as two different initiatives!
– If you do that, Agility is “Dead on Arrival”
– Go beyond your CI/CD tools
• Initiate small changes – take a Toyota Kata approach
– Start small; avoid the “cliché” terms – no reorg!
– The way they think, interact, architect, code, test
– Think SERVICES (SOA/Microservices)
– Simulate and test for failure/security/performance
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com
76. @sudiptal
THANK YOU….
• Reach me at:
– @sudiptal
– slahiri@digite.com
– sudiptalahiri.wordpress.c
om
@ Agile Network India , All Rights Reserved. www.agilenetworkindia.com