Monitorama 2017
•
1 like•273 views
The document discusses how ChatOps can be used as an agent of change by connecting people, tools, processes, and automation. It notes that implementing DevOps in a Microsoft environment can cause friction due to dependencies, lack of context, different time zones, and organizational structure. Finally, it lists over 30 common tools used in enterprise environments.
Report
Share
Report
Share
Download to read offline
Recommended
ChatOps as Change Agent
The document discusses concepts related to DevOps including ChatOps, change agents, onboarding, and friction. It provides definitions for these terms and lists examples of how ChatOps can help with onboarding by reducing friction from issues like permissions, dependencies, training, context, timezones, organization structure, transparency, and guardrails. A quote indicates that Guido P. was very excited about the idea of ChatOps.
DevOpsing in a Microsoft World - An experience report from Columbia Sportswear
The document discusses challenges in implementing DevOps practices within a Microsoft-centric organization and outlines strategies to address those challenges. It describes typical challenges such as reliance on vendors, siloed teams, and resistance to change. It emphasizes that enduring DevOps transformations require a commitment to becoming a learning organization. Interviews are presented where individuals discuss their journey implementing DevOps and lessons learned around constant change, lack of prioritization, and the importance of expanding skills.
Social Project Management 2.0
The mission of Social Project Management 2.0 is helping project teams to improve the team work by using enterprise social media platforms.
"Framing Feelix" - MYOB's UX Framework
Delivered by:
Kate Goodwin from HeathWallace - Senior UX Consultant
Gerry Scullion from MYOB - Senior UX Designer
Spoke at:
UX Australia 2014 Sydney
Web:
http://www.heathwallace.com/
http://myob.com.au/
Continuous Integration: a bittersweet love story
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
UX @BBC: Leading complex projects across platforms and teams
Leo Marti leads complex UX projects across platforms and teams at the BBC, which involves working with 200 designers. He discusses six principles for leading such complex projects: having fun, influencing effectively through storytelling and collaboration, designing decision making processes, helping teams work efficiently, using design strategically, and collaborating across disciplines from the beginning. The document provides tips and examples for each principle, such as setting up a design system and using agile, continuous research methods.
Agil8 Agile Story Writing - Impact Mapping - David Hicks - 30 Oct 2014
David Hicks, founder and CEO of agil8, introduced the concept of Impact Mapping to support effective Product Backlog creation at agil8's recent informal Agile evening Community Event on 30th October 2014.
#noprojects: Live happily ever after without projects
This document discusses the concept of #noprojects, which advocates switching from a project mindset to a product mindset when developing software. It presents #noprojects as a deliberate act of continuous product management. The document outlines #noprojects in 4 stages: 1) experiments over projects, 2) stable teams over temporary endeavors, 3) products over software, and 4) outcomes over execution. It also provides 10 principles for guiding a #noprojects approach, such as funding capacity not scope, bringing work to stable teams, and ensuring roadmaps are driven by needs not features. The overall message is that organizations should stop viewing software development as projects and instead focus on continuous product management and development.
Recommended
ChatOps as Change Agent
The document discusses concepts related to DevOps including ChatOps, change agents, onboarding, and friction. It provides definitions for these terms and lists examples of how ChatOps can help with onboarding by reducing friction from issues like permissions, dependencies, training, context, timezones, organization structure, transparency, and guardrails. A quote indicates that Guido P. was very excited about the idea of ChatOps.
DevOpsing in a Microsoft World - An experience report from Columbia Sportswear
The document discusses challenges in implementing DevOps practices within a Microsoft-centric organization and outlines strategies to address those challenges. It describes typical challenges such as reliance on vendors, siloed teams, and resistance to change. It emphasizes that enduring DevOps transformations require a commitment to becoming a learning organization. Interviews are presented where individuals discuss their journey implementing DevOps and lessons learned around constant change, lack of prioritization, and the importance of expanding skills.
Social Project Management 2.0
The mission of Social Project Management 2.0 is helping project teams to improve the team work by using enterprise social media platforms.
"Framing Feelix" - MYOB's UX Framework
Delivered by:
Kate Goodwin from HeathWallace - Senior UX Consultant
Gerry Scullion from MYOB - Senior UX Designer
Spoke at:
UX Australia 2014 Sydney
Web:
http://www.heathwallace.com/
http://myob.com.au/
Continuous Integration: a bittersweet love story
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
UX @BBC: Leading complex projects across platforms and teams
Leo Marti leads complex UX projects across platforms and teams at the BBC, which involves working with 200 designers. He discusses six principles for leading such complex projects: having fun, influencing effectively through storytelling and collaboration, designing decision making processes, helping teams work efficiently, using design strategically, and collaborating across disciplines from the beginning. The document provides tips and examples for each principle, such as setting up a design system and using agile, continuous research methods.
Agil8 Agile Story Writing - Impact Mapping - David Hicks - 30 Oct 2014
David Hicks, founder and CEO of agil8, introduced the concept of Impact Mapping to support effective Product Backlog creation at agil8's recent informal Agile evening Community Event on 30th October 2014.
#noprojects: Live happily ever after without projects
This document discusses the concept of #noprojects, which advocates switching from a project mindset to a product mindset when developing software. It presents #noprojects as a deliberate act of continuous product management. The document outlines #noprojects in 4 stages: 1) experiments over projects, 2) stable teams over temporary endeavors, 3) products over software, and 4) outcomes over execution. It also provides 10 principles for guiding a #noprojects approach, such as funding capacity not scope, bringing work to stable teams, and ensuring roadmaps are driven by needs not features. The overall message is that organizations should stop viewing software development as projects and instead focus on continuous product management and development.
Ppt of waterfall vs agile (2)
Waterfall vs Agile The basic trait of civilization is order and protocol. The chaos and non-structured attempts to build something has never resulted in a fruitful outcome in any spectrum. Software Development isn’t an exception either.
Agile Mobile Design: Why we don’t do mobile usability tests (and neither shou...
Agile Mobile Design: Why we don’t do mobile usability tests (and neither shou...DesignCaffeine, Inc.
Mobile usability tests are not recommended for agile mobile design projects. Instead of kickoff meetings, design workshops should be held where stakeholders provide feedback using post-it notes to guide rapid iterative testing and exploration. This allows designers to quickly test and refine designs without the time and costs of traditional usability testing.No Tool is an Island: Building DevOps into your business
IT toolstacks keep growing, with specialized tools that improve the efficiency of the business analysts, developers, testers, and service desk reps involved in the software delivery value stream. The problem is: NOTHING IS FLOWING! Tasktop was no exception. We struggled with the lack of visibility, communication bottlenecks, inefficiencies and waste created by a disconnected toolchain. In this webinar, we’ll describe the problems we faced and how we’ve solved them with relative ease through automation across our value stream.
#Noprojects @Agile Venture Prato 2018
La quasi totalità degli sviluppi software è basata su un approccio per progetto. Un progetto, per definizione, è qualcosa di effimero. Ha un inizio, e soprattutto una fine, qualcosa di temporaneo. Il software non è temporaneo. Un software sopravvive fino a quando esiste almeno una persona che lo utilizza. A volte sopravvive anche più a lungo.
Perché continuiamo ad usare qualcosa di effimero per gestire qualcosa che effimero non è? Quali alternative abbiamo? Possiamo fare veramente a meno dei progetti?
Keep Calm and Innovate Sustainably: 10 Tips for Sustainable Design
Nowadays, sustainable production and consumption remain an exception. Consumers demand more sustainable products, yet they often lack information. The problem for product designers and managers: shifting to sustainable innovation is not always easy. This presentation will drive you through 10 tips to get started with more sustainable design.
Parts of this presentation were inspired by the SPIN/Leapfrog Project, a joint initiative from TU Delft, the Vietnam Cleaner Production Center (VNCPC), UNEP and Dassault Systèmes.
Learn more about the Leapfrog Project at: http://perspectives.3ds.com/tag/leapfrog-project/
From idea to mvp
From Idea to Minimum Viable Product - The Journey to a product involves understanding the process of experimenting with prototypes and building a more formal process of Lean Startup experimentation and validation.
The Project Management Comeback
Project Managers often face an identity crisis when companies transition to agile: either become a scrum master, move to another role entirely, or another company! This discussion will demonstrate how project management can not only co-exist with your agile process, but thrive. Plus, you'll learn how Gilt blends agile principles with traditional project management techniques to bring their strategic initiatives to life.
Project planning 101 for publicsectorpm v2
An introduction to project planning. These are the slides that I use for the half day project planning course that I run.
DevOps is Scaling Agile too
A customer of us asked to give a presentation on DevOps and Agile. Having a mixed audience, Agile experienced Developers, testers but people from the Business and Ops to, I decided to link Agile and DevOps in a logical story. In this presentation I explain the step from SCRUM to DevOps. Starting with why we want to do SCRUM, the challenges I see we are struggling with in daily live, and make the step to Scaling Agile (e.g. Less, DaD, SAFe). Scaling Agile scales its defects too. So we should fix your problems before scaling them. What will happen if you enter the world of Continues Integration and Deployment. Isn't that Scaling Agile too? What does this mean for the defects in you dev - process?
Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...
From a talk at Tech.Rocks 2020
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the book Team Topologies by Matthew Skelton and Manuel Pais including first-hand experience helping companies around the world with the design of their technology teams.
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
We're all Designers: Encouraging Collaboration in Design Without Forming a Co...
Product design and development often involves many people of different roles who enter and leave at different parts of a project. However, this can cause communication problems and responses that sound like "you're the designer", "that'll take too much time", or "that's not my job" when people attempt to collaborate.
In this talk, Catt discussed methods used to cross silos in order to speed up the design and development process while also building camaraderie, agency, and transparency. She also discussed ways to encourage teams that may be reluctant to change and ways to get upper management on board with a more collaborative design process.
Limiting WIP: Doing Less to Do More
This session will review the concept of WIP and explore in-depth the reasons for limiting WIP: enhancing focus, reducing cycle time, optimizing flow and making bottlenecks visible. We will give strategies for starting out with WIP limits and suggestions for what to do when a limit is reached. Finally, we'll put theory to practice by running a short, virtual simulation that all attendees can participate in.
Beyond the spotify model - Team Topologies - Agile Yorkshire 2019-03-20 - Mat...
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway's Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
Bio: Matthew Skelton is the Founder and Head of Consulting at Conflux. He has been building, deploying, and operating commercial software systems since 1998. As Head of Consulting at Conflux, he specialises in Continuous Delivery, operability and organisation dynamics for software in manufacturing, ecommerce, and online services, including cloud, IoT, and embedded software.
Recognised by TechBeacon in 2018 as one of the top 100 people to follow in DevOps, Matthew curates the well-known DevOps team topologies patterns at devopstopologies.com and is co-author of the books Continuous Delivery with Windows and .NET (O’Reilly, 2016), Team Guide to Software Operability (Skelton Thatcher Publications, 2016), and Team Topologies (IT Revolution Press, 2019).
Matthew founded Conflux in 2017 to offer training and consulting to organisations building and running software systems.
Twitter: @matthewpskelton
LinkedIn: matthewskelton
Slideshare: matthewskelton
From a talk at Agile Yorkshire on 20 March 2019 http://www.agileyorkshire.org/event-announcements/wed20thmarch-andybutcherautonomyandchoreography-usingconwayslawtotacklethecompanyscalingproblem
'10 Great but now Overlooked Tools' by Graham Thomas
The idea for this presentation came directly from EuroSTAR 2011. Sitting on the bus back to the conference centre after attending the Gala Dinner, a discussion started, about industry luminaries who turn up at conferences and give presentations which roughly say "Don't do all the stuff that I told you to do 5 years ago! Do this stuff now." But, but, but . . . .
As we got talking I realised how many simple effective tools I no longer used, because they have either become overlooked, forgotten and thus fallen into disuse, or because modern methods claim not to need them and they are redundant. I wondered if any of them were worth looking at again - starting with my trusty flowcharting template; I realised it is a great tool which I have overlooked for far too long!
Here is my list of 10 great but now overlooked tools:
• Flowcharts
• Prototypes
• Project Plans
• Mind Maps
• Tools we already have at our disposal like ....
• Aptitude Tests
• Hexadecimal Calculators
• Desk Checking
• Data Dictionaries and Workbenches
This is my list of really useful tools that I think are overlooked. In the webinar I will outline each tool, why I think it was great, and what we are missing out by not using it.
And it naturally follows that if there are some tools we have overlooked then there are also some tools that we should get rid of! I will identify some.
Hopefully this webinar will give you a different perspective on tools to use for testing, some tools that may be improved upon or plain discarded, and help you think about the tools you currently use and maybe to view them in a different light.
Enacting Scrum - What it takes to maximize the chances for a successful adopt...
This document provides an overview of Scrum and Agile frameworks presented at the ITCAMPRO #ITCAMP16 conference. It defines Scrum roles, events, artifacts and principles. Key aspects of Scrum include short sprint cycles, daily stand-ups, product backlogs and increments. Agile principles emphasize valuing individuals, working software, collaboration and responding to change. The document also discusses factors for successfully enacting Scrum, such as willingness to change, collaborate and succeed.
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...South Tyrol Free Software Conference
This document discusses improving the developer experience for open source projects by focusing on documentation, outdated documentation being a common problem, and defining processes for code style, linting, contributions and releases. It recommends using containers to reduce prerequisites and mimic production environments. Defining processes is described as important for others to understand what to do. Laravel is presented as a case study of a project that has well-defined processes.Citizen Developer Tools are not just for Citizen Developers (session at Share...
So, the citizen developers have all the cool tools, and those that actually code for a living are left with legacy stuff? Not so fast! The same tools that Microsoft is targeting for citizen developers make development easier, faster and cheaper for everyone!
This session combines tools such as Flow, Azure Cognitive Services and Azure Functions with some actual simple development work to provide highly customized, Machine Learning powered analysis workflow for the newly baked Modern Team Sites in SharePoint Online. This demo-heavy session will look at real business scenarios, and how we can solve them using citizen developer tools and some code (Because we’re developers after all, right?)
After this session, you'll know how to create rich and customized business automation processes that use the latest tools offered to us by Microsoft.
Beyond the Spotify model - Team Topologies - Keynote at JAX DevOps 2019-05-16...
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
From a keynote talk at Jax DevOps 2019, London.
Explainable Machine Learning for Ranking Factors
It’s now common knowledge that machine learning can be used to predict your ranking factors, your traffic, or perfectly classify images, but it's impossible to point to the factors that most influence a prediction or a classification in each specific case.
However, new methods and techniques make algorithms more understandable to humans, even when dealing with very complex models. This is a huge benefit for machine learning use cases in SEO.
Teams Nation 2024 - #Copilot & Teams or Just Premium.pptx
This the presentation MVP Knut Relbe-Moe and I hold yesterday (21.02.24) at TeamsNation 2024.
In this session we spoke about M365 Copilot or Teams Premium. What do you need or do you sometime need both? Well this you learn from here.
Limiting WIP - Music City Tech 2021
Limiting work in progress improves product quality, achieves faster delivery, and helps the flow of work on a team.
Beyond Ad-hoc Automation - Leveraging Structured Platforms (Agile Day Twin Ci...
This document discusses leveraging structured platforms for automation beyond ad-hoc methods. It mentions containerizing builds, continuous integration, continuous delivery practices using Concourse CI, canary deployments, creating visibility into operations, architecting for failure, and distributing decision making. It also emphasizes that durable communication is important and should be inclusive, transparent, and reliable.
More Related Content
What's hot
Ppt of waterfall vs agile (2)
Waterfall vs Agile The basic trait of civilization is order and protocol. The chaos and non-structured attempts to build something has never resulted in a fruitful outcome in any spectrum. Software Development isn’t an exception either.
Agile Mobile Design: Why we don’t do mobile usability tests (and neither shou...
Agile Mobile Design: Why we don’t do mobile usability tests (and neither shou...DesignCaffeine, Inc.
Mobile usability tests are not recommended for agile mobile design projects. Instead of kickoff meetings, design workshops should be held where stakeholders provide feedback using post-it notes to guide rapid iterative testing and exploration. This allows designers to quickly test and refine designs without the time and costs of traditional usability testing.No Tool is an Island: Building DevOps into your business
IT toolstacks keep growing, with specialized tools that improve the efficiency of the business analysts, developers, testers, and service desk reps involved in the software delivery value stream. The problem is: NOTHING IS FLOWING! Tasktop was no exception. We struggled with the lack of visibility, communication bottlenecks, inefficiencies and waste created by a disconnected toolchain. In this webinar, we’ll describe the problems we faced and how we’ve solved them with relative ease through automation across our value stream.
#Noprojects @Agile Venture Prato 2018
La quasi totalità degli sviluppi software è basata su un approccio per progetto. Un progetto, per definizione, è qualcosa di effimero. Ha un inizio, e soprattutto una fine, qualcosa di temporaneo. Il software non è temporaneo. Un software sopravvive fino a quando esiste almeno una persona che lo utilizza. A volte sopravvive anche più a lungo.
Perché continuiamo ad usare qualcosa di effimero per gestire qualcosa che effimero non è? Quali alternative abbiamo? Possiamo fare veramente a meno dei progetti?
Keep Calm and Innovate Sustainably: 10 Tips for Sustainable Design
Nowadays, sustainable production and consumption remain an exception. Consumers demand more sustainable products, yet they often lack information. The problem for product designers and managers: shifting to sustainable innovation is not always easy. This presentation will drive you through 10 tips to get started with more sustainable design.
Parts of this presentation were inspired by the SPIN/Leapfrog Project, a joint initiative from TU Delft, the Vietnam Cleaner Production Center (VNCPC), UNEP and Dassault Systèmes.
Learn more about the Leapfrog Project at: http://perspectives.3ds.com/tag/leapfrog-project/
From idea to mvp
From Idea to Minimum Viable Product - The Journey to a product involves understanding the process of experimenting with prototypes and building a more formal process of Lean Startup experimentation and validation.
The Project Management Comeback
Project Managers often face an identity crisis when companies transition to agile: either become a scrum master, move to another role entirely, or another company! This discussion will demonstrate how project management can not only co-exist with your agile process, but thrive. Plus, you'll learn how Gilt blends agile principles with traditional project management techniques to bring their strategic initiatives to life.
Project planning 101 for publicsectorpm v2
An introduction to project planning. These are the slides that I use for the half day project planning course that I run.
DevOps is Scaling Agile too
A customer of us asked to give a presentation on DevOps and Agile. Having a mixed audience, Agile experienced Developers, testers but people from the Business and Ops to, I decided to link Agile and DevOps in a logical story. In this presentation I explain the step from SCRUM to DevOps. Starting with why we want to do SCRUM, the challenges I see we are struggling with in daily live, and make the step to Scaling Agile (e.g. Less, DaD, SAFe). Scaling Agile scales its defects too. So we should fix your problems before scaling them. What will happen if you enter the world of Continues Integration and Deployment. Isn't that Scaling Agile too? What does this mean for the defects in you dev - process?
What's hot (9)
Agile Mobile Design: Why we don’t do mobile usability tests (and neither shou...
Agile Mobile Design: Why we don’t do mobile usability tests (and neither shou...
No Tool is an Island: Building DevOps into your business
No Tool is an Island: Building DevOps into your business
Keep Calm and Innovate Sustainably: 10 Tips for Sustainable Design
Keep Calm and Innovate Sustainably: 10 Tips for Sustainable Design
Similar to Monitorama 2017
Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...
From a talk at Tech.Rocks 2020
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the book Team Topologies by Matthew Skelton and Manuel Pais including first-hand experience helping companies around the world with the design of their technology teams.
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
We're all Designers: Encouraging Collaboration in Design Without Forming a Co...
Product design and development often involves many people of different roles who enter and leave at different parts of a project. However, this can cause communication problems and responses that sound like "you're the designer", "that'll take too much time", or "that's not my job" when people attempt to collaborate.
In this talk, Catt discussed methods used to cross silos in order to speed up the design and development process while also building camaraderie, agency, and transparency. She also discussed ways to encourage teams that may be reluctant to change and ways to get upper management on board with a more collaborative design process.
Limiting WIP: Doing Less to Do More
This session will review the concept of WIP and explore in-depth the reasons for limiting WIP: enhancing focus, reducing cycle time, optimizing flow and making bottlenecks visible. We will give strategies for starting out with WIP limits and suggestions for what to do when a limit is reached. Finally, we'll put theory to practice by running a short, virtual simulation that all attendees can participate in.
Beyond the spotify model - Team Topologies - Agile Yorkshire 2019-03-20 - Mat...
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway's Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
Bio: Matthew Skelton is the Founder and Head of Consulting at Conflux. He has been building, deploying, and operating commercial software systems since 1998. As Head of Consulting at Conflux, he specialises in Continuous Delivery, operability and organisation dynamics for software in manufacturing, ecommerce, and online services, including cloud, IoT, and embedded software.
Recognised by TechBeacon in 2018 as one of the top 100 people to follow in DevOps, Matthew curates the well-known DevOps team topologies patterns at devopstopologies.com and is co-author of the books Continuous Delivery with Windows and .NET (O’Reilly, 2016), Team Guide to Software Operability (Skelton Thatcher Publications, 2016), and Team Topologies (IT Revolution Press, 2019).
Matthew founded Conflux in 2017 to offer training and consulting to organisations building and running software systems.
Twitter: @matthewpskelton
LinkedIn: matthewskelton
Slideshare: matthewskelton
From a talk at Agile Yorkshire on 20 March 2019 http://www.agileyorkshire.org/event-announcements/wed20thmarch-andybutcherautonomyandchoreography-usingconwayslawtotacklethecompanyscalingproblem
'10 Great but now Overlooked Tools' by Graham Thomas
The idea for this presentation came directly from EuroSTAR 2011. Sitting on the bus back to the conference centre after attending the Gala Dinner, a discussion started, about industry luminaries who turn up at conferences and give presentations which roughly say "Don't do all the stuff that I told you to do 5 years ago! Do this stuff now." But, but, but . . . .
As we got talking I realised how many simple effective tools I no longer used, because they have either become overlooked, forgotten and thus fallen into disuse, or because modern methods claim not to need them and they are redundant. I wondered if any of them were worth looking at again - starting with my trusty flowcharting template; I realised it is a great tool which I have overlooked for far too long!
Here is my list of 10 great but now overlooked tools:
• Flowcharts
• Prototypes
• Project Plans
• Mind Maps
• Tools we already have at our disposal like ....
• Aptitude Tests
• Hexadecimal Calculators
• Desk Checking
• Data Dictionaries and Workbenches
This is my list of really useful tools that I think are overlooked. In the webinar I will outline each tool, why I think it was great, and what we are missing out by not using it.
And it naturally follows that if there are some tools we have overlooked then there are also some tools that we should get rid of! I will identify some.
Hopefully this webinar will give you a different perspective on tools to use for testing, some tools that may be improved upon or plain discarded, and help you think about the tools you currently use and maybe to view them in a different light.
Enacting Scrum - What it takes to maximize the chances for a successful adopt...
This document provides an overview of Scrum and Agile frameworks presented at the ITCAMPRO #ITCAMP16 conference. It defines Scrum roles, events, artifacts and principles. Key aspects of Scrum include short sprint cycles, daily stand-ups, product backlogs and increments. Agile principles emphasize valuing individuals, working software, collaboration and responding to change. The document also discusses factors for successfully enacting Scrum, such as willingness to change, collaborate and succeed.
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...South Tyrol Free Software Conference
This document discusses improving the developer experience for open source projects by focusing on documentation, outdated documentation being a common problem, and defining processes for code style, linting, contributions and releases. It recommends using containers to reduce prerequisites and mimic production environments. Defining processes is described as important for others to understand what to do. Laravel is presented as a case study of a project that has well-defined processes.Citizen Developer Tools are not just for Citizen Developers (session at Share...
So, the citizen developers have all the cool tools, and those that actually code for a living are left with legacy stuff? Not so fast! The same tools that Microsoft is targeting for citizen developers make development easier, faster and cheaper for everyone!
This session combines tools such as Flow, Azure Cognitive Services and Azure Functions with some actual simple development work to provide highly customized, Machine Learning powered analysis workflow for the newly baked Modern Team Sites in SharePoint Online. This demo-heavy session will look at real business scenarios, and how we can solve them using citizen developer tools and some code (Because we’re developers after all, right?)
After this session, you'll know how to create rich and customized business automation processes that use the latest tools offered to us by Microsoft.
Beyond the Spotify model - Team Topologies - Keynote at JAX DevOps 2019-05-16...
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.
Key takeaways:
1. Why using the “Spotify Model” of team design is not enough
2. The four fundamental team topologies needed for modern software delivery
3. The three team interaction modes that enable fast flow and rapid learning
4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies
From a keynote talk at Jax DevOps 2019, London.
Explainable Machine Learning for Ranking Factors
It’s now common knowledge that machine learning can be used to predict your ranking factors, your traffic, or perfectly classify images, but it's impossible to point to the factors that most influence a prediction or a classification in each specific case.
However, new methods and techniques make algorithms more understandable to humans, even when dealing with very complex models. This is a huge benefit for machine learning use cases in SEO.
Teams Nation 2024 - #Copilot & Teams or Just Premium.pptx
This the presentation MVP Knut Relbe-Moe and I hold yesterday (21.02.24) at TeamsNation 2024.
In this session we spoke about M365 Copilot or Teams Premium. What do you need or do you sometime need both? Well this you learn from here.
Limiting WIP - Music City Tech 2021
Limiting work in progress improves product quality, achieves faster delivery, and helps the flow of work on a team.
Beyond Ad-hoc Automation - Leveraging Structured Platforms (Agile Day Twin Ci...
This document discusses leveraging structured platforms for automation beyond ad-hoc methods. It mentions containerizing builds, continuous integration, continuous delivery practices using Concourse CI, canary deployments, creating visibility into operations, architecting for failure, and distributing decision making. It also emphasizes that durable communication is important and should be inclusive, transparent, and reliable.
Limiting WIP @ SM Summit_5.17.22
The document discusses limiting work in progress (WIP) to improve productivity. Some key points:
1. Limiting WIP to 1-3 items leads to faster delivery, better quality, and less stress by avoiding multitasking. It also makes bottlenecks more visible.
2. Studies show multitasking is inefficient and can reduce productivity by 40% due to switching costs. Limiting WIP reduces context switching.
3. With too much WIP, teams spend most time waiting rather than working. Limiting WIP improves flow and enables faster response to changes.
Distributed: of systems and teams (RICON 2015 version)
This document discusses distributed teams and systems. It notes that Bridget Kromhout lives in Minneapolis but works for Pivotal in San Francisco. It provides tips for effective communication and coordination for distributed teams, including using tools like Slack, providing context, being available, and over-communicating to prevent misunderstandings. It emphasizes that people are more important than tools and choosing tools the whole team will use.
Distributed: of systems and teams (SPS)
This document discusses distributed teams and systems. It begins with an overview of distributed systems concepts like availability, consistency, and partition tolerance. It then focuses on distributed teams, noting some challenges like lower bandwidth communication but also advantages in work-life balance and potential as a competitive advantage. Some recommendations for distributed teams include over-communicating, being explicit, examining assumptions, and distributing decision-making. The document provides references for further information.
Beyond the Spotify model - Team Topologies - Leeds DevOps - 2019-09-16 - Matt...
This talk covers the basics of organization design using Team Topologies, exploring a selection of key team types and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.
From a talk given at Leeds DevOps meetup group: http://www.leedsdevops.org.uk/post/2019-09-08-monday-16th-september-2019-at-the-odi-node-in-leeds/
Beyond the Spotify model - Team Topologies - OSWA Oslo - 2020-01-22 - Matthew...
A talk given at Oslo Software Architecture meetup
https://www.meetup.com/Oslo-Software-Architecture/events/267904102/
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.
Experimentación ágil de machine learning con DVC
Conforme aumenta el uso de modelos de machine learning en las empresas, y se requiere continuamente estarlos enriqueciendo y generando experimentos para estimar el impacto de los cambios, requerimos de herramientas que nos apoyen para facilitar, automatizar y gestionar estas tareas.
Presentado por: Ramón Valles
Keynote Dev Days vilnius 2018: how openness changes your behaviour
This document discusses how openness and dashboards can change organizational culture and behavior. It describes how the author modernized an IT team through implementing monitoring dashboards that provided transparency into operations. This improved communication between teams and ended the "shouting" between IT and developers. Dashboards improved executives' understanding of workloads and helped prioritize cloud migrations. Overall, dashboards fostered understanding, trust and empowerment by sharing operational insights across organizations.
Similar to Monitorama 2017 (20)
Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...
Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...
We're all Designers: Encouraging Collaboration in Design Without Forming a Co...
We're all Designers: Encouraging Collaboration in Design Without Forming a Co...
Beyond the spotify model - Team Topologies - Agile Yorkshire 2019-03-20 - Mat...
Beyond the spotify model - Team Topologies - Agile Yorkshire 2019-03-20 - Mat...
'10 Great but now Overlooked Tools' by Graham Thomas
'10 Great but now Overlooked Tools' by Graham Thomas
Enacting Scrum - What it takes to maximize the chances for a successful adopt...
Enacting Scrum - What it takes to maximize the chances for a successful adopt...
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...
Citizen Developer Tools are not just for Citizen Developers (session at Share...
Citizen Developer Tools are not just for Citizen Developers (session at Share...
Beyond the Spotify model - Team Topologies - Keynote at JAX DevOps 2019-05-16...
Beyond the Spotify model - Team Topologies - Keynote at JAX DevOps 2019-05-16...
Teams Nation 2024 - #Copilot & Teams or Just Premium.pptx
Teams Nation 2024 - #Copilot & Teams or Just Premium.pptx
Beyond Ad-hoc Automation - Leveraging Structured Platforms (Agile Day Twin Ci...
Beyond Ad-hoc Automation - Leveraging Structured Platforms (Agile Day Twin Ci...
Distributed: of systems and teams (RICON 2015 version)
Distributed: of systems and teams (RICON 2015 version)
Beyond the Spotify model - Team Topologies - Leeds DevOps - 2019-09-16 - Matt...
Beyond the Spotify model - Team Topologies - Leeds DevOps - 2019-09-16 - Matt...
Beyond the Spotify model - Team Topologies - OSWA Oslo - 2020-01-22 - Matthew...
Beyond the Spotify model - Team Topologies - OSWA Oslo - 2020-01-22 - Matthew...
Keynote Dev Days vilnius 2018: how openness changes your behaviour
Keynote Dev Days vilnius 2018: how openness changes your behaviour
Recently uploaded
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdf
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Trusted Execution Environment for Decentralized Process Mining
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Operating System Used by Users in day-to-day life.pptx
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
Recently uploaded (20)
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdf
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdf
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Trusted Execution Environment for Decentralized Process Mining
Trusted Execution Environment for Decentralized Process Mining
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Operating System Used by Users in day-to-day life.pptx
Operating System Used by Users in day-to-day life.pptx
Monitorama 2017
- 1. @scottnasello | @Monitorama ChatOps as Change Agent? 1
- 2. @scottnasello | @Monitorama2 “DevOps in a Microsoft shop is like a 5 hour road trip to an amusement park on the hottest day of the year”
- 3. @scottnasello | @Monitorama3 ChatOps: A collaboration workflow that connects people, tools, process, and automation
- 4. @scottnasello | @Monitorama NOBODY PUTS IN THE CORNER
- 5. @scottnasello | @Monitorama5 Welcome aboard!
- 6. @scottnasello | @Monitorama6 … New hire day 1 … Autobuild Coffee Scripts … CI pipeline
- 7. @scottnasello | @Monitorama Friction (n): conflict or animosity caused by a clash of wills, temperaments, or opinions.
- 8. @scottnasello | @Monitorama Friction (n): conflict or animosity caused by a clash of wills, temperaments, or opinions.
- 9. @scottnasello | @Monitorama9 friction … dependencies … context … time zone … org structure
- 10. @scottnasello | @Monitorama10 1 2 3 4 5 Active Directory, Artifactory, Azure, CHEF, Cisco, Citrix, Commvault, EMC, GitLab, Grafana, InfluxDB, Isilon, Jenkins, Lansweeper, O365, NetScaler, Packer, Palo Alto, Pester, PoshOrigin, SAP, SCCM, Sensu, SharePoint, Symantec, Teradata, Terraform, TFS, VMware, VPN, Windows