Talk given by Michael DeHaan and Greg DeKoenigsberg at All Things Open in October 2014, in which we discussed how we applied open source best practices to grow a large and active community of users and developers.
How to build the wrong thing faster and learn from it keynote by David Hussma...ProductCamp Twin Cities
Discussion: Can ‘agile software development’ be refactored to ‘agile product development’? Some brave pioneers already doing this are re-learning that building good product is more opaque than simply getting work done. The land of product development is filled with holes, ambiguity and landmines of wrongness. Ideas that you are stone certain about often fizzle or change when you watch someone interact with your product. Being overly certain or focusing on ‘just getting work done’ to sustain velocity are mistakes that make matters worse.
Join me in an exploration of how to embrace wrongness, learn from it, and make it a vital part of our success. Our journey will explore the messy, sloppy and non-linear aspects of product development. Along the way, we’ll investigate how software construction is important, but courageously failing and learning in product is even more essential. We’ll look at how some teams are producing more real product value with less code. We will also peer into the world of program level development, where collections of teams produce better product by employing what might be called ‘test driven product.’
Who knows, toward the end of the journey, we might even rally to refactor the agile manifesto to read ‘Learning in Product over Simply Getting Things Done.’
DevOps requires agility. The document discusses how DevOps involves operations and development engineers working together throughout the entire service lifecycle. It provides the example of Etsy, which deployed code to production an average of 32-50 times per day. Continuous integration is presented as a way to integrate changes frequently in order to detect issues early. The key aspects of continuous integration discussed are having a CI server that rebuilds and runs tests on every commit, as well as activities like unit testing, code analysis, reporting and visualization.
DevOps is a cultural and professional movement that aims to build a culture of increased work flow, fast feedback loops, and continuous improvement. The top 10 DevOps values are: 1) Culture of empowerment, shared responsibility, cross-functional teams, shared success, and learning; 2) Communication and collaboration across teams; 3) Trust between teams; 4) Decreasing silos between departments; 5) Fast feedback loops at all stages; 6) Systems thinking to improve the entire system; 7) Applying Lean principles to eliminate waste and optimize processes; 8) Automating repetitive tasks; 9) Measuring everything as often as possible; and 10) Promoting continuous improvement through learning and knowledge sharing.
The document describes a DevOps game called the Marshmallow Challenge where teams compete to build the tallest freestanding structure using spaghetti that can support a marshmallow on top. The game aims to teach DevOps principles like collaboration, continuous learning, and applying feedback. It discusses how different groups like kindergarten students versus business students or engineers perform. The rules and process for playing the game are provided along with learnings around integrating development, operations, testing and more.
In this presentation I discuss how poor implementations of root cause analysis undermine an organization’s attempts to enable a learning culture. Audience members will: 1. understand the intent of root cause analysis; 2. be able to recognize its limitations; 3. fix their implementations.
How To Do Kick-Ass Software DevelopmentSven Peters
With Kick-Ass Software Development you actually get stuff done. Feedback cycles are short, code quality is awesome and customers get the features they lust after. Less mangers managing, less testers testing and less IT-operators operating. The developers take the power back, making them much happier. Sound like paradise? It is! This session will show you how we do Kick-Ass Software Development at Atlassian.
I talk about how we: use pull requests for better code quality; collaborate fast to develop ideas; avoid meetings to get more stuff done; tighten our feedback loops to fail faster; shorten our release cycles; and work together happily on different continents. It's a great way to develop software and we think it can work in your company, too.
Watch the video if this talk: http://vimeo.com/70102926
Talk given by Michael DeHaan and Greg DeKoenigsberg at All Things Open in October 2014, in which we discussed how we applied open source best practices to grow a large and active community of users and developers.
How to build the wrong thing faster and learn from it keynote by David Hussma...ProductCamp Twin Cities
Discussion: Can ‘agile software development’ be refactored to ‘agile product development’? Some brave pioneers already doing this are re-learning that building good product is more opaque than simply getting work done. The land of product development is filled with holes, ambiguity and landmines of wrongness. Ideas that you are stone certain about often fizzle or change when you watch someone interact with your product. Being overly certain or focusing on ‘just getting work done’ to sustain velocity are mistakes that make matters worse.
Join me in an exploration of how to embrace wrongness, learn from it, and make it a vital part of our success. Our journey will explore the messy, sloppy and non-linear aspects of product development. Along the way, we’ll investigate how software construction is important, but courageously failing and learning in product is even more essential. We’ll look at how some teams are producing more real product value with less code. We will also peer into the world of program level development, where collections of teams produce better product by employing what might be called ‘test driven product.’
Who knows, toward the end of the journey, we might even rally to refactor the agile manifesto to read ‘Learning in Product over Simply Getting Things Done.’
DevOps requires agility. The document discusses how DevOps involves operations and development engineers working together throughout the entire service lifecycle. It provides the example of Etsy, which deployed code to production an average of 32-50 times per day. Continuous integration is presented as a way to integrate changes frequently in order to detect issues early. The key aspects of continuous integration discussed are having a CI server that rebuilds and runs tests on every commit, as well as activities like unit testing, code analysis, reporting and visualization.
DevOps is a cultural and professional movement that aims to build a culture of increased work flow, fast feedback loops, and continuous improvement. The top 10 DevOps values are: 1) Culture of empowerment, shared responsibility, cross-functional teams, shared success, and learning; 2) Communication and collaboration across teams; 3) Trust between teams; 4) Decreasing silos between departments; 5) Fast feedback loops at all stages; 6) Systems thinking to improve the entire system; 7) Applying Lean principles to eliminate waste and optimize processes; 8) Automating repetitive tasks; 9) Measuring everything as often as possible; and 10) Promoting continuous improvement through learning and knowledge sharing.
The document describes a DevOps game called the Marshmallow Challenge where teams compete to build the tallest freestanding structure using spaghetti that can support a marshmallow on top. The game aims to teach DevOps principles like collaboration, continuous learning, and applying feedback. It discusses how different groups like kindergarten students versus business students or engineers perform. The rules and process for playing the game are provided along with learnings around integrating development, operations, testing and more.
In this presentation I discuss how poor implementations of root cause analysis undermine an organization’s attempts to enable a learning culture. Audience members will: 1. understand the intent of root cause analysis; 2. be able to recognize its limitations; 3. fix their implementations.
How To Do Kick-Ass Software DevelopmentSven Peters
With Kick-Ass Software Development you actually get stuff done. Feedback cycles are short, code quality is awesome and customers get the features they lust after. Less mangers managing, less testers testing and less IT-operators operating. The developers take the power back, making them much happier. Sound like paradise? It is! This session will show you how we do Kick-Ass Software Development at Atlassian.
I talk about how we: use pull requests for better code quality; collaborate fast to develop ideas; avoid meetings to get more stuff done; tighten our feedback loops to fail faster; shorten our release cycles; and work together happily on different continents. It's a great way to develop software and we think it can work in your company, too.
Watch the video if this talk: http://vimeo.com/70102926
The Journey of devops and continuous delivery in a Large Financial InstitutionKris Buytaert
The Journey of devops and continuous deliverey in a Large Financial Institution,
as presented by @markheistek and myselve at Velocity Conf 2013, Longon
The document discusses developing sustainable web projects with PHP. It emphasizes using light weight processes like automating tasks, communicating effectively with stakeholders, and focusing on delivering value through short iterative cycles. The document recommends using tools like Behat for testing, Trello for task management, and continuous integration to regularly deploy updates. It stresses having no assumptions about client needs and designing based on user stories to develop projects in a sustainable way.
How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Av...DevOpsDays Tel Aviv
The document discusses how to continuously innovate with software given the rapid pace of new technologies being introduced and the large research and development budgets of corporations. It emphasizes the need to build solutions that address business needs rather than adopting every new tool, and to develop an adaptive culture within teams that can respond to changing technologies and industry trends. Examples are provided of how open source technologies like Docker have evolved and best practices for evaluating and using new software.
Kris Buytaert discusses the Devops movement and how bringing developers and operations teams together earlier improves systems. He advocates for automation throughout the development and deployment process, from version control and testing to configuration management, monitoring, and upgrades. Adopting a Devops culture and practices like continuous integration, delivery, and deployment can help teams deploy better systems faster at lower risk.
Chris Heilmann gave a talk about breaking out of endless callback loops in JavaScript development. He discussed the history and evolution of JavaScript, including its growing capabilities and uses. However, he emphasized that progressive enhancement and capability testing are still important principles on the client side to avoid broken experiences. While tools like transpilation and polyfills can help bring future features to current browsers, overreliance on them has downsides. The best approach is to embrace JavaScript's use in different environments and balance innovation with backward compatibility.
The document discusses the importance of continuous updating of software libraries and dependencies to ensure applications have the latest bug fixes and security updates. It notes that with agile development, the software development lifecycle has accelerated, but dependencies are still often overlooked. Left unmanaged, outdated dependencies can introduce security vulnerabilities and breakages over time. The document advocates using a tool like VersionEye to automatically detect outdated libraries, track used licenses, and ensure continuous integration of updates through automated migration paths. This prevents issues and saves developers time and money from manual updating processes.
Successful agile in distributed team Scrum Gathering Shanghai 2015hrbendi
Distributed team is always a big headache to software development. In this presentation we will discuss what are the key elements of a distributed team in terms of success, and share a case study.
Introduction to Test Driven DevelopmentDaniel Wildt
This document discusses various agile methodologies including Lean, Scrum, eXtreme Programming (XP), and test-driven development (TDD). It provides overviews of Lean principles and practices, XP practices like writing user stories and tests first, and tools for testing like Selenium IDE and JUnit. Links are included for further reading on topics like Lean software development, what is XP, writing user stories, TDD, and behavior driven development. The document aims to provide information on agile strategies, tactics, and processes for software development.
Startup Engineering culture - "What matters & what does not"Mohan Krishnan
The document discusses key aspects of engineering culture at startup companies. It emphasizes that culture, such as how teams work together and communicate, is more important than superficial practices like free food or tools. Specifically, it recommends hiring for cultural fit, prioritizing teams over individuals, over-communicating transparently, providing honest feedback, embracing change through quick iterations, and learning from failures.
The agile manifesto says directly that "We are uncovering better ways of developing software by doing it and helping others do it." If this continual improvement is true, what new topics are currently being discussed and talked about at agile conferences? What are teams across the world struggling and experimenting with? What topics are the most heated? In this session, I'll give an overview of some of the new and hot agile topics.
This document discusses passion for software and Atlassian. It highlights that passion is needed to start with a vision, work with great people, have freedom and respect in the workplace. It also discusses using a wiki to share knowledge fast, getting feedback through public issue trackers, and the importance of passionate developers and teams for innovation. The document promotes breaking work into small pieces, failing fast, and allowing time for innovation through independent work periods.
This document discusses important developer disciplines for software development. It begins by introducing the author, Chris Howe-Jones, and his background. It then discusses the complex, multi-disciplinary nature of software development teams and environments. The rest of the document outlines various important developer disciplines like test-driven development, version control, continuous integration, refactoring, design principles and more. It emphasizes the importance of testing in many forms. Overall, the document provides an overview of technical and process disciplines that are important for developers to know.
This document summarizes a 1st DevOps meetup in Riga. It introduces Uldis Karlovs-Karlovskis as the DevOps Evangelist and discusses what DevOps is, including that it is a culture where development and operations work together. It also notes that DevOps involves tools like Jenkins, Git, Ansible, AWS, Chef and Jira. Finally, it discusses why organizations adopt DevOps and emphasizes continual learning about DevOps through resources like books, reports and online sources.
The document discusses lean software development principles for achieving continuous delivery, including eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole process. It provides examples of how following these principles can reduce wait times, unnecessary processes, and bugs by making decisions quickly with the whole team and delivering changes more rapidly based on feedback. The overall message is that lean principles can help teams optimize their processes for continuous delivery.
A culture of Automation - Joe Smith - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv
The document discusses strategies for running production services, including careful planning, extensive documentation, and good communication. It emphasizes establishing runbooks that document operational tasks and procedures. Over time, as teams grow and work expands, runbooks should be automated through scripts and tools to reduce manual effort and potential errors. Automating runbooks involves initially writing scripts for small tasks and evolving them through testing, bug fixing, and incorporating additional workflow steps. Fully automated runbooks improve reliability and allow work to be completed through execution of instructions rather than human judgement.
modern approaches share a focus on producing exceptional outcomes and growing an outstanding culture. Today, it makes far more sense to bypass antiquated agility in favor of modern approaches.
Modern agile methods are defined by four guiding principles:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
my understanding of fundamentals of DevOps and how it relates conceptually to Agile, Scrum, Kanban, etc.
SlideShare does not allow uploading a new version of existing presentation. Hence I have to upload the new verson.
Goto https://www.slideshare.net/nitinbhide/devops-understanding-core-concepts for latest version.
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 ).
Are you a:
- University student or fresh graduate wishing to pursue a career in DevOps and want to prepare for it?
- Software Engineer (developer, tester, etc.) who is curious about DevOps?
- Software Engineer (developer, tester, etc.) wishing to switch from his/her current role to a DevOps related role?
This session is just for you!
Check out the video on YouTube at https://www.youtube.com/watch?v=yYWEOdORH40
The Journey of devops and continuous delivery in a Large Financial InstitutionKris Buytaert
The Journey of devops and continuous deliverey in a Large Financial Institution,
as presented by @markheistek and myselve at Velocity Conf 2013, Longon
The document discusses developing sustainable web projects with PHP. It emphasizes using light weight processes like automating tasks, communicating effectively with stakeholders, and focusing on delivering value through short iterative cycles. The document recommends using tools like Behat for testing, Trello for task management, and continuous integration to regularly deploy updates. It stresses having no assumptions about client needs and designing based on user stories to develop projects in a sustainable way.
How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Av...DevOpsDays Tel Aviv
The document discusses how to continuously innovate with software given the rapid pace of new technologies being introduced and the large research and development budgets of corporations. It emphasizes the need to build solutions that address business needs rather than adopting every new tool, and to develop an adaptive culture within teams that can respond to changing technologies and industry trends. Examples are provided of how open source technologies like Docker have evolved and best practices for evaluating and using new software.
Kris Buytaert discusses the Devops movement and how bringing developers and operations teams together earlier improves systems. He advocates for automation throughout the development and deployment process, from version control and testing to configuration management, monitoring, and upgrades. Adopting a Devops culture and practices like continuous integration, delivery, and deployment can help teams deploy better systems faster at lower risk.
Chris Heilmann gave a talk about breaking out of endless callback loops in JavaScript development. He discussed the history and evolution of JavaScript, including its growing capabilities and uses. However, he emphasized that progressive enhancement and capability testing are still important principles on the client side to avoid broken experiences. While tools like transpilation and polyfills can help bring future features to current browsers, overreliance on them has downsides. The best approach is to embrace JavaScript's use in different environments and balance innovation with backward compatibility.
The document discusses the importance of continuous updating of software libraries and dependencies to ensure applications have the latest bug fixes and security updates. It notes that with agile development, the software development lifecycle has accelerated, but dependencies are still often overlooked. Left unmanaged, outdated dependencies can introduce security vulnerabilities and breakages over time. The document advocates using a tool like VersionEye to automatically detect outdated libraries, track used licenses, and ensure continuous integration of updates through automated migration paths. This prevents issues and saves developers time and money from manual updating processes.
Successful agile in distributed team Scrum Gathering Shanghai 2015hrbendi
Distributed team is always a big headache to software development. In this presentation we will discuss what are the key elements of a distributed team in terms of success, and share a case study.
Introduction to Test Driven DevelopmentDaniel Wildt
This document discusses various agile methodologies including Lean, Scrum, eXtreme Programming (XP), and test-driven development (TDD). It provides overviews of Lean principles and practices, XP practices like writing user stories and tests first, and tools for testing like Selenium IDE and JUnit. Links are included for further reading on topics like Lean software development, what is XP, writing user stories, TDD, and behavior driven development. The document aims to provide information on agile strategies, tactics, and processes for software development.
Startup Engineering culture - "What matters & what does not"Mohan Krishnan
The document discusses key aspects of engineering culture at startup companies. It emphasizes that culture, such as how teams work together and communicate, is more important than superficial practices like free food or tools. Specifically, it recommends hiring for cultural fit, prioritizing teams over individuals, over-communicating transparently, providing honest feedback, embracing change through quick iterations, and learning from failures.
The agile manifesto says directly that "We are uncovering better ways of developing software by doing it and helping others do it." If this continual improvement is true, what new topics are currently being discussed and talked about at agile conferences? What are teams across the world struggling and experimenting with? What topics are the most heated? In this session, I'll give an overview of some of the new and hot agile topics.
This document discusses passion for software and Atlassian. It highlights that passion is needed to start with a vision, work with great people, have freedom and respect in the workplace. It also discusses using a wiki to share knowledge fast, getting feedback through public issue trackers, and the importance of passionate developers and teams for innovation. The document promotes breaking work into small pieces, failing fast, and allowing time for innovation through independent work periods.
This document discusses important developer disciplines for software development. It begins by introducing the author, Chris Howe-Jones, and his background. It then discusses the complex, multi-disciplinary nature of software development teams and environments. The rest of the document outlines various important developer disciplines like test-driven development, version control, continuous integration, refactoring, design principles and more. It emphasizes the importance of testing in many forms. Overall, the document provides an overview of technical and process disciplines that are important for developers to know.
This document summarizes a 1st DevOps meetup in Riga. It introduces Uldis Karlovs-Karlovskis as the DevOps Evangelist and discusses what DevOps is, including that it is a culture where development and operations work together. It also notes that DevOps involves tools like Jenkins, Git, Ansible, AWS, Chef and Jira. Finally, it discusses why organizations adopt DevOps and emphasizes continual learning about DevOps through resources like books, reports and online sources.
The document discusses lean software development principles for achieving continuous delivery, including eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole process. It provides examples of how following these principles can reduce wait times, unnecessary processes, and bugs by making decisions quickly with the whole team and delivering changes more rapidly based on feedback. The overall message is that lean principles can help teams optimize their processes for continuous delivery.
A culture of Automation - Joe Smith - DevOpsDays Tel Aviv 2017DevOpsDays Tel Aviv
The document discusses strategies for running production services, including careful planning, extensive documentation, and good communication. It emphasizes establishing runbooks that document operational tasks and procedures. Over time, as teams grow and work expands, runbooks should be automated through scripts and tools to reduce manual effort and potential errors. Automating runbooks involves initially writing scripts for small tasks and evolving them through testing, bug fixing, and incorporating additional workflow steps. Fully automated runbooks improve reliability and allow work to be completed through execution of instructions rather than human judgement.
modern approaches share a focus on producing exceptional outcomes and growing an outstanding culture. Today, it makes far more sense to bypass antiquated agility in favor of modern approaches.
Modern agile methods are defined by four guiding principles:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
my understanding of fundamentals of DevOps and how it relates conceptually to Agile, Scrum, Kanban, etc.
SlideShare does not allow uploading a new version of existing presentation. Hence I have to upload the new verson.
Goto https://www.slideshare.net/nitinbhide/devops-understanding-core-concepts for latest version.
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 ).
Are you a:
- University student or fresh graduate wishing to pursue a career in DevOps and want to prepare for it?
- Software Engineer (developer, tester, etc.) who is curious about DevOps?
- Software Engineer (developer, tester, etc.) wishing to switch from his/her current role to a DevOps related role?
This session is just for you!
Check out the video on YouTube at https://www.youtube.com/watch?v=yYWEOdORH40
The document discusses common cultural impediments ("elephants") that can prevent effective collaboration between development (Dev) and operations (Ops) teams when adopting a DevOps approach. It identifies eight such elephants: 1) Dev and Ops teams don't communicate; 2) teams are separated rather than integrated; 3) senior leadership priorities aren't aligned; 4) DevOps is seen as replacing Ops rather than collaboration; 5) DevOps is equated only with tools; 6) teams resist change; 7) teams hide behind regulations; and 8) teams try to change too many things at once. For each elephant, it provides ideas for how to address the issue, with a focus on improving communication, collaboration, knowledge sharing and adopting a
Mark Mzyk
Engineering Manager with Chef
Find more by Mark Mzyk: https://speakerdeck.com/mmzyk
All Things Open
October 26-27, 2016
Raleigh, North Carolina
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.
A high level introduction to DevOps. Explains what it is, how popular DevOps has become, why DevOps is popular, how DevOps differs from traditional approaches and some next steps to implementation.
The document discusses DevOps concepts and best practices. It begins with defining what DevOps is not, such as not being a role or only about tools. The main part then defines DevOps as a culture of collaboration between development and operations to accelerate the software development lifecycle. It lists things the author wishes they knew about DevOps such as it being about automation, collaboration, and continuous processes. Best practices discussed include shifting testing left, embracing automation and infrastructure as code.
This document provides an overview of getting started with DevOps. It includes an agenda covering topics like DevOps frameworks, practices, and tooling. The DevOps framework section outlines the people, process, and technology aspects, including mindset, practices like pipelines and automation, and DevOps toolchains. It also discusses how to build a DevOps team and adoption plan. The overall document serves as an introduction to DevOps concepts, best practices, and provides guidance on implementing DevOps.
The document outlines 10 ways to fail at DevOps by misunderstanding its core principles. DevOps is not about adding specialized teams or roles, enforcing tools or processes, or attaining certifications. Rather, DevOps is about culture change through collaboration between teams, embracing failure to improve, and giving developers freedom and responsibility.
The document provides 5 lessons from implementing DevOps practices in large, complex enterprise environments. The lessons are: 1) DevOps initiatives require balancing top-down directives with bottom-up cultural changes; 2) cross-cutting concerns like security, compliance, and audit need to be addressed; 3) standardization is important but too much can stifle innovation; 4) DevOps needs to involve related groups beyond just development and operations like QA and security; and 5) organizations need to determine whether the focus is internal automation or outward-facing cultural and organizational changes.
This document provides an introduction to DevOps. It begins with background on the presenter and then outlines the topics to be covered: What is DevOps?, Why DevOps?, and How to DevOps?. Under What is DevOps?, it explains that DevOps emphasizes communication and collaboration between development and operations teams. It also discusses definitions of DevOps and what DevOps is not. The Why DevOps? section notes that DevOps can increase speed, reduce risks, and help companies adapt to changes. How to DevOps? involves cultural shifts, focusing on people, processes, tools, and adopting concepts like automation, lean, measurement and sharing.
Devops & Agility - Build the Culture, Get the Tools, Win the Day - Dundee Tec...David Walker
DevOps involves development and operations engineers collaborating throughout the entire service lifecycle from design to deployment and support. It builds upon agile principles by applying them throughout the entire workflow. Implementing DevOps requires cultural changes across the entire organization where teams work together towards shared goals. Automation, lean principles, continuous monitoring and improvements are key aspects of DevOps.
Andrew Phillips gave a presentation on DevOps at SaltConf15. He began with a primer on DevOps, noting it is a methodology that emphasizes frequent tooling like configuration management and infrastructure as code. He explained that operations has become a software-defined endeavor, and DevOps applies development methodologies and practices to operations. This often results in organizations having two development teams - one for development and one for operations. However, creating end-to-end development teams that span the full software lifecycle is also an option, though it presents challenges. The key is for each organization to figure out which approach works best for them.
This document discusses DevOps from the perspective of Erno Aapa, a DevOps consultant. It outlines some common misunderstandings about DevOps, such as thinking it is a role or team. The document then discusses the history of approaches like Agile, Scrum, and Continuous Integration that influenced DevOps. It explains how DevOps gives companies the capability to experiment and deploy changes rapidly and safely. The benefits of DevOps include faster deployments, improved collaboration between Dev and Ops teams, and the ability to get feedback from customers to continuously improve.
DevOps is mainstream - at least the tools, the automation and the metrics. But what happened to DevOps Culture? Does it still matter? If yes - how do we achieve it?
Agile Gurgaon 2016 | Thinking Beyond :: Marry Agile and DevOps for Phenomenal...AgileNetwork
This document discusses marrying Agile and DevOps approaches to get phenomenal results. It begins with an introduction of the author and their experience. It then poses common questions around when to adopt Agile vs DevOps and how they relate. The document outlines differences between traditional and Agile/DevOps mindsets and practices. It provides examples of lessons learned and challenges overcome during one organization's transformation journey. Finally, it discusses steps to get started with a DevOps approach and lists examples of effective DevOps practices.
A talk about DevOps that I gave at a SysARmy meetup while visiting MuleSoft's Buenos Aires DevOps team. I've been thinking a lot recently about what DevOps is, what it means to be a DevOps Engineer (or in my case a DevOps Engineering Manager). Putting this together was really helpful to clarify some ideas I've been kicking around.
DevOps culture: Computer scientists are only human ... ;)Jörg Hastreiter
Eye-catching top 10 signs, that you have to change something and DevOps is a possible answer. Typical points of resistance illustrate, that DevOps is a human challenge!
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
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.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
3. The outcome of applying Lean principles to
the IT value stream – Gene Kim
DevOps Definitions – A Dime a Dozen
Software dev method that stresses
communication, collaboration, integration,
automation, and measurement of cooperation
- Wikipedia
An umbrella concept that refers to anything that
smoothes out the interaction between dev and
ops – Damon Edwards
6. How DevOps is Killing the Developer? - Jeff Knupp
Is DevOps Killing the Developer?
- Paul Krill
Is DevOps Killing Some Types of Jobs?
- Eric Minick
Since When DevOps Became a Serial Killer?
Is DevOps killing the <insert position
of the day here>? - Jonathan Thorpe
DevOps isn’t killing developers – But…
- Jim Bird
10. But I Can‘t Live Like This…
Attend Some Meetups
And Conferences
Use a Checklist
http://devopschecklist.com
Track KPIs/ Metrics
11. Context Matters (at least during transition)
Compiled vs. non-Compiled?
Enterprise vs. Startup?
Legacy vs. Fresh?
5 teams vs. 500 teams?
Grassroots vs. top-down?
Public cloud vs. Private cloud?
12. Many Practices (Forms) are Common!
Multi-disciplinary & Self-disciplined Teams
Trust-based Culture
Self-serve Tools
Automation
Configuration Management
Proactive Testing & Monitoring
16. It’s About Continuous Improvement!
Continuous improvement is better than delayed perfection!
- Mark Twain
It’s not about being the best,
it’s about better than you were yesterday
- Wise Man
17. Useful Stuff
Chef Style DevOps Kungfu
Adam Jacob
https://www.youtube.com/watch?v=_DEToXsgrPc&list=PL11cZfNdwNyO9CpTWH2qjYfzysEtpfOCd
Surprise! Broad Agreement on the Definition of DevOps
Erick Minick
http://devops.com/2015/05/13/surprise-broad-agreement-on-the-definition-of-devops/