This document summarizes a presentation on how to build high-performing IT teams. It begins by making the case that high-performing teams are both more agile and reliable based on data. It then discusses identifying the desired organizational state with high trust cultures, aligned goals, and other attributes. Next, it covers aligning incentives across business, development, operations, and quality teams to focus on customer value. The document also reviews common team structures and implementing technical practices like infrastructure as code, version control, peer review, and continuous delivery to measure results.
Demystifying DevOps for Ops - Including Findings from the 2015 State of DevOp...Puppet
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code.
It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
DOES15 - Sherry Chang - Intel’s Journey to Large Scale DevOps Transformation Gene Kim
Sherry Chang, Enterprise Architect, Intel
Is it possible to transform large enterprises with 100’s of in-flight projects across myriad technology stacks and entrenched processes, requiring massive workforce re-skilling? In this session, I’ll share approaches we employed to increase the likelihood of success through DevOps adoption by:
-Offering of a common Continuous Delivery Service, similar to industry offerings from Codeship.io, CloudBees, and others
-Establishing a Maturity Model to help teams incrementally adopt DevOps practices
-Coaching teams through Kaizen sessions to eliminate bottlenecks and waste in their value stream
Structuring the right team for DevOps without Re-Organization. I presented this at DevOps Fusion 2015. Tips include rapid feedback loop, value stream analysis, etc.
What does a Maturity Curve for Enterprise Adoption of Agile and DevOps look like? Where would an organization like yours rank on the curve? Are there specific areas of improvement you might want to consider?
In many organizations, agile development processes are driving the pursuit of faster software releases, which has spawned a set of new practices called DevOps. DevOps stresses communications and integration between development and operations, including continuous integration, continuous delivery, and rapid deployments. Because DevOps practices require confidence that changes made to the code base will function as expected. automated testing is an essential ingredient Join Jeff Payne as he discusses the unique challenges associated with integrating automated testing into continuous integration/continuous delivery (CI/CD) environments. Learn the internals of how CI/CD works, appropriate tooling, and test integration points. Find out howpto integrate your existing test automation frameworks into a DevOps environment and leave with roadmap for integrating test automation with continuous integration and delivery.
Demystifying DevOps for Ops - Including Findings from the 2015 State of DevOp...Puppet
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code.
It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
DOES15 - Sherry Chang - Intel’s Journey to Large Scale DevOps Transformation Gene Kim
Sherry Chang, Enterprise Architect, Intel
Is it possible to transform large enterprises with 100’s of in-flight projects across myriad technology stacks and entrenched processes, requiring massive workforce re-skilling? In this session, I’ll share approaches we employed to increase the likelihood of success through DevOps adoption by:
-Offering of a common Continuous Delivery Service, similar to industry offerings from Codeship.io, CloudBees, and others
-Establishing a Maturity Model to help teams incrementally adopt DevOps practices
-Coaching teams through Kaizen sessions to eliminate bottlenecks and waste in their value stream
Structuring the right team for DevOps without Re-Organization. I presented this at DevOps Fusion 2015. Tips include rapid feedback loop, value stream analysis, etc.
What does a Maturity Curve for Enterprise Adoption of Agile and DevOps look like? Where would an organization like yours rank on the curve? Are there specific areas of improvement you might want to consider?
In many organizations, agile development processes are driving the pursuit of faster software releases, which has spawned a set of new practices called DevOps. DevOps stresses communications and integration between development and operations, including continuous integration, continuous delivery, and rapid deployments. Because DevOps practices require confidence that changes made to the code base will function as expected. automated testing is an essential ingredient Join Jeff Payne as he discusses the unique challenges associated with integrating automated testing into continuous integration/continuous delivery (CI/CD) environments. Learn the internals of how CI/CD works, appropriate tooling, and test integration points. Find out howpto integrate your existing test automation frameworks into a DevOps environment and leave with roadmap for integrating test automation with continuous integration and delivery.
The world of IT is shifting rapidly towards DevOps with analysts predicting the majority of companies will adopt DevOps practices in the next few years. In fact, in a recent study on DevOps by International Data Corp. (IDC), they believe that DevOps will be adopted (in either practice or discipline) by 80% of Global 1000 organizations by 2019!
Forming a DevOps team seems like a natural step, but the idea of creating a dedicated DevOps team has ignited anger in the community. Why? What's the concern? Is a DevOps team evil? Completely necessary? A necessary Evil?
Join IBM UrbanCode's Eric Minick to learn the pitfalls of creating bad DevOps teams, and successful approaches of good ones. Along the way, we’ll explore other heresies such as using tools to change culture.
Continuous Delivery presents a compelling vision of builds that are automatically deployed and tested until ready for production.
Most teams aren't there yet. Some never want to go that far. Others want to push the envelope further.
This deck presents a model for scoring yourself on the continuum and examples of how companies can decide what parts of CD to adopt first, later and not at all.
Showcase development processes and methods with our content ready Devops PowerPoint Presentation Slide. Focus on rapid application delivery using our visually appealing development and operations PPT visuals. The operating system PowerPoint complete deck comprises self-explanatory and editable PowerPoint templates such as need for DevOps, best practices, criteria for choosing a pilot project, DevOps goals, timeline for DevOps transformation, current state future state, 30-60-90 day plan, roadmap for DevOps, transformation post successful DevOps Implementation, RACI matrix, dashboard to name a few. Users can easily customize all the templates as per their specific project needs. Furthermore, you can also use this IT operations management presentation deck to encourage your team to adopt DevOps culture practices and tools. Demonstrate DevOps goals like Increase automation and standardize the process, reduce cost effort & time to market and so on. Download our system development lifecycle PowerPoint templates to present ways to make improved products faster for greater client satisfaction. Handle deficiencies with our DevOps Powerpoint Presentation Slides. Initiate action to acquire desired assets. https://bit.ly/3y8q8NC
5 Steps to Building a Mature DevOps Organization with Sherwin-WilliamsDynatrace
The “wall of confusion” is a common theme for many IT organizations. The development team wants change while the operations team wants stability. But how do you break down the wall and move towards a DevOps model?
Sherwin-Williams shares the 5-point maturity model they used to transform themselves into a full-fledged DevOps company, and how you can learn to build DevOps into your company.
You’ll learn:
• How automation can help you build a bigger and better pipeline
• How to create modular environments for local development all the way through production
• Why testing everything, automatically, and at all tiers is critical to moving at the speed of light
• How to remove the hand offs, streamline the process, and challenge everything that doesn’t add value
Building a DevOps Organization and CultureRapidValue
This whitepaper explains adopting the DevOps practice and how teams should be structured and re-structured. It discusses in detail how organizations can achieve increased collaboration within the team through DevOps. It also, describes the different roles and responsibilities of people involved in the DevOps
approach with real-world examples.
Developing a Testing Strategy for DevOps SuccessDevOps.com
To achieve rapid time-to-market, businesses have embraced DevOps, which places a premium on speed and efficiency. But speed is not the only measure of DevOps success. To release better software faster, enterprises must optimize testing strategy and embed a culture of quality within their DevOps processes.
In this webinar, you will learn:
How to transform QA from a bottleneck to a speed enabler
How to integrate quality and increase visibility throughout the SDLC
How to help your VPs and Directors gauge the success of their current quality initiatives
We provide a brief introduction to DevOps, as well as a more practical analysis on how DevOps can be implemented efficiently. We discuss the genealogy of DevOps: how it came about, what it has to do with Agile, why it has gained such attention and support, and the benefits it can provide. We touch upon the topic of how DevOps works in practice. During a live demo, we showcase how codeBeamer ALM supports the implementation of the DevOps approach.
DevOps vs Agile | DevOps Tutorial For Beginners | DevOps Training | EdurekaEdureka!
***** DevOps Masters Program : https://www.edureka.co/masters-progra... *****
This is a short tutorial by Edureka on DevOps vs Agile, which will help you understand the fundamental difference between DevOps and Agile software development strategies.
Based on recent research findings from the EMA Worldwide DevOps 2020 survey, leading IT analyst firm Enterprise Management Associates (EMA) provides insights into where DevOps is headed.
SD DevOps Meet-up - Exploring Quadrants of DevOps MaturityBrian Dawson
his is a presentation given at the March 16th San Diego DevOps Meet-up , which maps the enterprise DevOps journey to 4 quadrants of maturity and covers practical process, tools and leadership strategies for "crossing the chasm" from an organization's current quadrant to the next level of maturity.
DOES16 London - Darren Hague - SAP’s DevOps Journey: From Building an App to ...Gene Kim
Darren Hague, Cloud Infrastructure Architect, SAP
SAP has been using a DevOps & Continuous Delivery approach for building its web and mobile apps for several years, and is now building and running a global cloud at the scale needed to support the digital transformation needs of its customers. This talk recaps the story of how SAP originally adopted DevOps practices before moving on to describe how the Cloud Infrastructure Services team is building and operating its 3rd generation cloud automation system using microservices, containers and open-source software.
Technical Capabilities as enabler for Agile and DevOpsNelis Boucké
This presentation was done at Journee Agile in Liege. It explains how technical capabilities are an important part of any transformation. Without tech capabilities you will have a hard time to release, and a hard time to inspect and adapt.
The world of IT is shifting rapidly towards DevOps with analysts predicting the majority of companies will adopt DevOps practices in the next few years. In fact, in a recent study on DevOps by International Data Corp. (IDC), they believe that DevOps will be adopted (in either practice or discipline) by 80% of Global 1000 organizations by 2019!
Forming a DevOps team seems like a natural step, but the idea of creating a dedicated DevOps team has ignited anger in the community. Why? What's the concern? Is a DevOps team evil? Completely necessary? A necessary Evil?
Join IBM UrbanCode's Eric Minick to learn the pitfalls of creating bad DevOps teams, and successful approaches of good ones. Along the way, we’ll explore other heresies such as using tools to change culture.
Continuous Delivery presents a compelling vision of builds that are automatically deployed and tested until ready for production.
Most teams aren't there yet. Some never want to go that far. Others want to push the envelope further.
This deck presents a model for scoring yourself on the continuum and examples of how companies can decide what parts of CD to adopt first, later and not at all.
Showcase development processes and methods with our content ready Devops PowerPoint Presentation Slide. Focus on rapid application delivery using our visually appealing development and operations PPT visuals. The operating system PowerPoint complete deck comprises self-explanatory and editable PowerPoint templates such as need for DevOps, best practices, criteria for choosing a pilot project, DevOps goals, timeline for DevOps transformation, current state future state, 30-60-90 day plan, roadmap for DevOps, transformation post successful DevOps Implementation, RACI matrix, dashboard to name a few. Users can easily customize all the templates as per their specific project needs. Furthermore, you can also use this IT operations management presentation deck to encourage your team to adopt DevOps culture practices and tools. Demonstrate DevOps goals like Increase automation and standardize the process, reduce cost effort & time to market and so on. Download our system development lifecycle PowerPoint templates to present ways to make improved products faster for greater client satisfaction. Handle deficiencies with our DevOps Powerpoint Presentation Slides. Initiate action to acquire desired assets. https://bit.ly/3y8q8NC
5 Steps to Building a Mature DevOps Organization with Sherwin-WilliamsDynatrace
The “wall of confusion” is a common theme for many IT organizations. The development team wants change while the operations team wants stability. But how do you break down the wall and move towards a DevOps model?
Sherwin-Williams shares the 5-point maturity model they used to transform themselves into a full-fledged DevOps company, and how you can learn to build DevOps into your company.
You’ll learn:
• How automation can help you build a bigger and better pipeline
• How to create modular environments for local development all the way through production
• Why testing everything, automatically, and at all tiers is critical to moving at the speed of light
• How to remove the hand offs, streamline the process, and challenge everything that doesn’t add value
Building a DevOps Organization and CultureRapidValue
This whitepaper explains adopting the DevOps practice and how teams should be structured and re-structured. It discusses in detail how organizations can achieve increased collaboration within the team through DevOps. It also, describes the different roles and responsibilities of people involved in the DevOps
approach with real-world examples.
Developing a Testing Strategy for DevOps SuccessDevOps.com
To achieve rapid time-to-market, businesses have embraced DevOps, which places a premium on speed and efficiency. But speed is not the only measure of DevOps success. To release better software faster, enterprises must optimize testing strategy and embed a culture of quality within their DevOps processes.
In this webinar, you will learn:
How to transform QA from a bottleneck to a speed enabler
How to integrate quality and increase visibility throughout the SDLC
How to help your VPs and Directors gauge the success of their current quality initiatives
We provide a brief introduction to DevOps, as well as a more practical analysis on how DevOps can be implemented efficiently. We discuss the genealogy of DevOps: how it came about, what it has to do with Agile, why it has gained such attention and support, and the benefits it can provide. We touch upon the topic of how DevOps works in practice. During a live demo, we showcase how codeBeamer ALM supports the implementation of the DevOps approach.
DevOps vs Agile | DevOps Tutorial For Beginners | DevOps Training | EdurekaEdureka!
***** DevOps Masters Program : https://www.edureka.co/masters-progra... *****
This is a short tutorial by Edureka on DevOps vs Agile, which will help you understand the fundamental difference between DevOps and Agile software development strategies.
Based on recent research findings from the EMA Worldwide DevOps 2020 survey, leading IT analyst firm Enterprise Management Associates (EMA) provides insights into where DevOps is headed.
SD DevOps Meet-up - Exploring Quadrants of DevOps MaturityBrian Dawson
his is a presentation given at the March 16th San Diego DevOps Meet-up , which maps the enterprise DevOps journey to 4 quadrants of maturity and covers practical process, tools and leadership strategies for "crossing the chasm" from an organization's current quadrant to the next level of maturity.
DOES16 London - Darren Hague - SAP’s DevOps Journey: From Building an App to ...Gene Kim
Darren Hague, Cloud Infrastructure Architect, SAP
SAP has been using a DevOps & Continuous Delivery approach for building its web and mobile apps for several years, and is now building and running a global cloud at the scale needed to support the digital transformation needs of its customers. This talk recaps the story of how SAP originally adopted DevOps practices before moving on to describe how the Cloud Infrastructure Services team is building and operating its 3rd generation cloud automation system using microservices, containers and open-source software.
Technical Capabilities as enabler for Agile and DevOpsNelis Boucké
This presentation was done at Journee Agile in Liege. It explains how technical capabilities are an important part of any transformation. Without tech capabilities you will have a hard time to release, and a hard time to inspect and adapt.
DevOps, sibling of Agile is born of the need to improve IT service delivery agility to the more stable environment.
DevOps movement emphasizes tearing the boundaries between makers (Development) & caretakers (Operations) of IT services/products.
In this presentation you will learn how Farm Credit Services of America/Frontier Farm Credit transformed their quality practices and tooling to bring visibility and consistency to Enterprise Quality, including: testing as a team approach, creating an automated test architecture, measuring progress with dashboards and standardizing on a set of testing tools.
Getting started with Site Reliability Engineering (SRE)Abeer R
"Getting started with Site Reliability Engineering (SRE): A guide to improving systems reliability at production"
This is an intro guide to share some of the common concepts of SRE to a non-technical audience. We will look at both technical and organizational changes that should be adopted to increase operational efficiency, ultimately benefiting for global optimizations - such as minimize downtime, improve systems architecture & infrastructure:
- improving incident response
- Defining error budgets
- Better monitoring of systems
- Getting the best out of systems alerting
- Eliminating manual, repetitive actions (toils) by automation
- Designing better on-call shifts/rotations
How to design the role of the Site Reliability Engineer (who effectively works between application development teams and operations support teams)
Market Trends: What new developments are shaping the way teams work?
Replacing HP Quality Center?: What hurdles are typically faced in replacing legacy Test Management?
Moving Beyond HP Unified Functional Tester?: What options exist to move to more modern automation tools?
Migration Best Practices: How are leading companies making the switch?
First DRAFT of a DevOps presentation and posters covering the essentials for a DevOps mindset. Help improve the content by forking and contributing a pull request to https://github.com/wpschaub/DevOps-mindset-essentials/blob/master/README.md.
Talk given by Kelly Currier, Agile Senior Director and Vladimir Gerasimov, Product Management Senior Manager at Salesforce, at STPCon in April 2016
Salesforce adopted agile methodologies over 7 years ago. Over the years, it has helped us to drive innovation, productivity and become the world’s #1 CRM solution. Salesforce has taken agile methodologies and created a unique approach called the Adaptive Delivery Methodology (ADM). During this session, we will provide an ADM overview and how it helps us deliver 3 major releases with hundreds of features every year. We will also cover how we approach testing and quality through ADM. At Salesforce, there is no such thing as throwing code over the fence for someone else to test. Developers and Quality Engineers, we all work together to ensure release quality.
For a beginner, this is a good quality pictorial representation of DevOps and DevOps Center of Excellence.
Opex Software focuses on consulting, implementation and development of DevOps tools and platforms. Have helped small and large data centers! This presentation talks about Continuous Integration, Continuous Delivery at a high level. For detailed presentations and flows, please ping us.
Thanks again, Enjoy!
Puppet + Diaxon: Getting to the next stage of DevOps evolutionPuppet
During this webinar, we’ll discuss the “how” to help you get started or unstuck, and scale DevOps success across your business.
Join us to see where you are in your evolution, how to get to the next stage, and to dig deeper into key findings like these:
- In a DevOps evolution, there are many paths to success, but many more to failure.
- Start with the practices that are closest to production; then address processes that happen earlier in the software delivery cycle.
- Automating security policy configurations is mission-critical to reaching the highest levels of DevOps evolution.
The idea behind DevOps is to demolish the wall between development and operations, and encourage more collaboration and accountability between both groups so that everyone feels responsible for the code no matter where it is in the software development lifecycle. For better understanding of DevOps, we have answered the 5Ws of DevOps.
DevOps es un conjunto de prácticas que automatizan los procesos entre el desarrollo de software y los equipos de infraestructura, de manera que el software pueda ser construido, probado y puesto en producción más rápidamente y con la misma confiabilidad.
El concepto de DevOps esta fundamentado en la construcción de una cultura de colaboración entre equipos que históricamente son silos. Los beneficios aparentes incluyen confianza mutua, más rápidos ciclos de puesta en producción, habilidad para resolución de incidentes más rápidamente y mejor adaptación a los cambios.
En esta sesión revisamos conceptos clave de DevOps, el estado del arte y algunas de las tecnologías involucradas.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
7. High-performing IT orgs are more agile
30x
More frequent
deployments
200x
Faster lead times
than their peers
Source: Puppet Labs 2015 State of DevOps Report
8. High-performing IT orgs are more reliable
60x
Change success
rate
168x
Faster mean time to
recover (MTTR)
Source: Puppet Labs 2015 State of DevOps Report
9. High-performing IT orgs are winning
1.5x
More likely to exceed
profitability, market
share & productivity
goals
50%
Higher market
capitalization growth
over 3 years.*
Source: Puppet Labs 2015 State of DevOps Report
10. Learning is not compulsory,
but neither is survival.
Edward W. Deming
http://bit.ly/deming14pts
18. “Trying to effect process, people, technology and
cultural changes across the entire application
portfolio, in a globally dispersed team and with a lot
of associated technical debt, is an epic challenge.”
Jonathan Fletcher
Enterprise Architect and Lead for Technology,
Platform and DevOps at Hiscox
http://bit.ly/devopshiscox
19. Hiscox: Results
• Reduced cost per release on one application
by 97%
• Reduced time per release by 89%
• Reduced staff required to release by 75%
• Automated testing reduced multiple man days
of effort down to an overnight hands-free
process
20. Conflicting Incentives
Business Delivering value to customers
Dev teams Delivering new features
Ops teams Ensuring stability of systems
Quality teams Ensuring quality of software releases
21. Everyone is responsible for quality
and we’re all trying to deliver the
best solution for our customers.
Reena Mathew, Principle Architect
Quality Engineering, Salesforce
http://bit.ly/sfdevops
24. We can’t do DevOps because our
application is
________________________.
25. Architectural Characteristics
Significant affect on IT performance
• Does not require integrated testing
environment
• Can deploy/release app
independently of other apps/services
it depends on
• Custom software with microservices
architecture
No affect on IT performance
• Packaged commercial software /
COTS.
• Systems of record / systems of
engagement
• New, not-yet-deployed systems.
• Software w/ embedded component that
runs on manufactured hardware device
/ user-installed component that runs on
user’s machine
27. Typical Enterprise Org Structure
IT Operations
NOC
Commercial Banking
Business Units
Credit Cards
Mortgages
Investment Banking
Systems Engineers
Network Engineers
Storage Admins
DBAs
InfosecDev teams reside in BU
29. Pattern 2: Cross-functional team
Characteristics
• Consists of devs, testers, ops, product
owner, etc.
• Focused on delivering a single
application
• Self-sufficient
• Optimized for throughput
30. Pattern 3: DevOps Team
Dev Ops
Dev
Ops
Characteristics
• Consists ideally of devs with systems
experience, or sysadmins with
programming experience
• Focused on automating pain points
• Responsible for building a platform that
allows devs to self-service
• Provides a toolchain to enable devs to
build, test and deploy their systems
• Coaches other teams
31. Roles & Responsibilities
Roles Responsibilities
“The Business” Understand market trends and identify customer needs
IT Manager Build trust with counterparts on other teams; create culture of learning
and continuous improvement; delegate authority; remove roadblocks
Dev Manager Build trust with Ops counterpart; bring Ops into the planning process
early
Systems Engineer Automate the things that are painful; help devs get feedback
QE Provide input into scale and performance; provide feedback on staging
environments
Devs Plan for deployment as you’re planning new features; get feedback from
ops and work with them on deployment process
38. Measuring Results
Throughput
• Deployment frequency
• Change lead time (from dev’s laptop to production)
• Cycle time
Stability / Reliability
• Change fail rate
• Mean time to recover
• Availability / downtime
39. Deployment Pain
Tomorrow, ask your team two questions:
• How painful are your deployments?
• What’s causing the pain?
40. Diversify Your Team
Teams with more women
have higher:
• Financial performance
• Stock market performance
• Hedge fund returns
• Collective intelligence
42. Resources
• The 2015 State of DevOps Report is here! puppetlabs.com/2015-
devops-report
• The Phoenix Project by Gene Kim
• Continuous Delivery by Jez Humble
• PuppetConf 2015: http://2015.puppetconf.com/
• DevOps Enterprise Summit: http://devopsenterprise.io/
Editor's Notes
- Hi, I’m Alanna Brown.
- I spearheaded Puppet Labs’ annual State of DevOps Survey and Report and I’ve spent the past 4 years studying DevOps and high-performing IT teams.
- How many of you have taken our survey or read the report?
- If you’re like most people, you’re struggling with how to “operationalize DevOps” and implement it in a pragmatic and sustainable way.
- Based on data and real world examples from customers, I’m going to share with you the keys to building a high-performing IT team.
- Today, I’m going to help you cut through the noise so you can start your DevOps initiative on the right foot.
Here’s how I’m going to do it:
Today, I’m going to demystify high-performance and show you 5 steps to kickstarting your DevOps initiative, supported by findings from our 2015 State of DevOps Report.
The first and most critical step in kickstarting your DevOps initiative is building the case and creating consensus.
It sounds really simple, but most people get this critical step wrong.
You can’t just say “We’re going to do DevOps now!” and expect everyone to drop what they’re doing and jump on board.
How many of you have ever had a higher up tell you you had to implement the latest buzzword without fully understanding what it would entail?
How many of you have been the ones telling your staff to implement the latest buzzword?
There’s a great TED talk by Simon Sinek, who wrote a book called Start with Why. The basic premise is this: People don’t buy what you do, they buy why you do it.
You probably already know why DevOps matters, but that doesn’t mean the rest of your team, your peers, or the people you report to get it.
Just as an experiment, go ask ten people “What problem are we trying to solve?” and see what answers you get. I bet they’ll be different depending on who you talk to.
Are there any managers or team leads in the room?
Well, listen up: you play a critical role here.
One of the most unexpected findings from the 2015 State of DevOps Report was that when the DevOps initiative was driven purely from the top-down, OR purely from a grassroots level, we saw a negative effect on organizational performance.
That’s why all of you managers and team leads are so important: you’re the ones who connect the strategic goals of the business with on-the-ground execution.
In the next couple of slides, I’m going to give you the tools to make a really strong business case for DevOps in your organization.
One of the challenges every organization faces is the need to move faster without compromising the reliability, security and stability of their systems.
These two seemingly opposing forces — agility and reliability — are possible to achieve. And it’s not just the unicorns who are achieving these results, it’s the horses, too.
Over the past 4 years, our data has consistently shown that:
High performing IT organizations are more agile. They deploy code 30 times more frequently. And they deploy 200 times faster than their peers.
We also know that high-performing IT orgs are more reliable.
We were shocked when we compared our high performing group this year to the high performers last year. We found that while they were deploying at the same speed and frequency, their overall reliability was substantially better than the 2014 respondents.
Our high performers this year have 60 times fewer failures and they’re able to restore service 168 times faster.
This suggests that organizations are shifting quality to the left.
If you think of the software delivery process as a manufacturing assembly line, on the far left you have the developer’s laptop where the code originates and on the far right you have your production environment where that code eventually ends up.
The fact that stability is increasing suggests that orgs are improving the system as a whole and building quality into the entire software development pipeline.
- We also know that strong IT performance is a competitive advantage.
- IT is not just a cost center — recent outages at the Wall Street Journal, New York Stock Exchange and United Airlines — illustrate the point that every company is a technology company and IT is critical to helping businesses achieve their goals.
- Companies with high performing IT orgs are 1.5x more likely to exceed profitability, market share & productivity goals than their peers.
- Preliminary financial analysis from our 2014 report also hints that it can even increase the total value of publicly traded companies as measured by market capitalization.
- I think this quote by Edward Deming sums it up best.
Deming is considered by many to be the godfather of DevOps. I’ve included the link to Deming’s 14 points which has influenced some of the best thinking in DevOps today.
The point of DevOps isn’t to automate all the things — although automation should be one of the outcomes; it’s to create a culture of continuous improvement, because only organizations that can adapt and learn will ultimately survive and win.
After you’ve gotten everyone on the same page about the problems you’re trying to solve as an organization, you need to get everyone aligned on what the desired outcomes are so you have a clear understanding of what success looks like.
- DevOps requires some big changes across the organization: changes that impact culture, processes and people.
- At the organizational level, the desired outcomes are to create a culture of high trust, with high-performing teams that are all aligned around a common business goal.
- To do that, a lot of processes have to change as you go from a very manual and siloed way of working to adopting automation and learning how to collaborate.
- These process changes lead to shorter cycle times, higher productivity and greater visibility.
- Let’s not forget the human cost of all of this.
- Burnout is an important issue in IT and one that we researched for this year’s report. The conditions that lead to burnout — unsustainable workloads, lack of control, and low-trust, pathological cultures — can be prevented.
- Not surprisingly, the data shows that where burnout is high, organizational culture is poor, deployment pain is high and organizational performance is low.
- How many of you are struggling to hire tech talent?
Did you know that it can cost upwards of $20k to hire one engineer?
- What if instead of spending that money on hiring new engineers every time one gets fed up and quits, you spent that money on changing the work conditions that lead to burnout and stagnation in the first place?
- In the next two slides, I’m going to show you what that investment looks like.
Here’s the good news: these desired outcomes are achievable. In the 2015 State of DevOps report, we found a direct link between DevOps practices, IT performance and organizational performance.
The diagram you see here represents a statistical model that shows how the practices that make up continuous delivery — deployment automation, automated testing, continuous integration and use of version control for all production artifacts — those practices predict deployment pain, IT performance and change fail rate. And in turn, IT performance predicts organizational performance.
One of the new constructs we added this year was around lean management practices. Lean management practices include limiting work in process, use of visual displays to monitor quality and productivity, and proactive application and infrastructure monitoring.
This diagram shows how lean management practices, predict organizational culture, IT performance and burnout. While culture and IT performance both predict organizational performance.
I love this finding because it proves that we don’t have reinvent the wheel. Lean manufacturing has evolved over 100 years and there’s so much we can learn from these battle-tested and codified principles and practices. When we apply these principles and practices to software delivery, we get the same results: higher quality products, faster cycle times, lower costs and less waste.
Doing DevOps doesn’t mean you’ll all be sitting around a campfire singing Kumbaya. A DevOps transformation is hard work and there will be plenty of challenges along the way.
One of our customers, Jonathan Fletcher from Hiscox, lead his organization through a DevOps transformation where he faced the epic challenge of driving change across a large, siloed organization. You can read Jonathan’s amazing story on our blog.
- The results speak volumes. Hiscox was able to reduce the cost per release on one application by 97 percent and by automating testing, they reduced multiple days of manual effort to an overnight hands-free process.
- Their transformation didn’t happen overnight. It took a lot of evangelizing, experimenting and restructuring.
- I want to talk about the biggest challenge Hiscox faced and the one you’re going to face as you embark on your journey.
- When I talk to customers about their challenges with adopting DevOps, they often cite resistance to change as their number one barrier.
- But I’d argue that the root cause isn’t resistance to change, but rather the way people are incentivized to do their work.
- The business is incentivized to deliver value to customers so it can generate more revenue
- Dev teams are incentivized to deliver new features faster
- Ops teams are incentivized to keep the systems running at all costs
Quality teams are responsible for the quality of the software.
Those incentives are all different and therefore lead to very different behaviors.
One of our long-time customers, Reena Mathews, principal architect in Quality Engineering at Salesforce said this: “Everyone is responsible for quality and we’re all trying to deliver the best solution for our customers.”
For Salesforce, every single participant in the software delivery process is incentivized to improve the service their teams deliver to their customers, and again the results speak for themselves.
Salesforce has been been ranked the most innovative company by Forbes Magazine for a record of four consecutive years.
They also rank No. 7 on Fortune’s 100 Best Places to Work list.
Salesforce and Hiscox are great examples of companies that are aligned around the goal of delivering value to customers.
In order to achieve alignment, you have to be structured correctly in the first place, which we’ll talk about in a minute.
But first, I want to talk about another common objection you’ll hear.
Who here has tried to make the case for DevOps and heard this: “We can’t do DevOps because our application is <fill in the blank>.
We found in our 2015 report that it doesn’t matter if your apps are greenfield, brownfield or legacy — as long as they are architected for testability and deployability, high performance is possible. We found that high performing respondents shared some common architectural characteristics. They:
- Do most of their testing without requiring an integrated environment
- Can deploy their applications independently of other dependent applications/services
- And many were using a microservices architecture
- Just to illustrate this point, one of our customers has an app running on a mainframe with a million line code base, and they’re doing automated testing.
One of the questions we get asked a lot is “What is the ideal team structure for DevOps?” And I think the answer depends on a few variables, like:
- how flexible is your current org structure
- what skillsets do you currently have on your team
- what’s the relationship between teams and team leaders
- How many of you work in an org structure that looks something like this?
- This is pretty typical of large enterprise organizations and what this results in is multiple silos of highly specialized individuals, which then leads to multiple hand-offs to get changes into production.
- I was talking to the head of infrastructure at a large retailer and he said it took 15 teams to deploy one service.
- If you count each hand-off as a conservative three days to account for lead times, work in progress, configuration errors, etc. that would be 45 days to deploy, and the majority of that time is waste.
Silos exist for a reason, and they’re not going away anytime soon, so how do we work around them?
I’m going to show you the three common patterns we see that work well for DevOps.
The first pattern is one in which Dev and ops remain distinct teams but work closely together to deploy applications.
The goal is not to have devs do operations and ops do development, it’s for each team to have an awareness and understanding of how their work impacts each other.
This pattern works really well for smaller organizations, but it’s extremely important in this structure to have a common toolchain between dev and ops to facilitate smoother collaboration.
A lot of our large enterprise customers, like Salesforce and Hiscox, have had success implementing a cross-functional model.
Cross-functional teams consist of representatives from all disciplines responsible for developing and deploying a service — business analysts, product owners, developers, quality engineers, ops, security, etc.
These teams are fully empowered and self-sufficient — they write it, test it, and deploy it.
These teams are more efficient because there are less hand-offs and more opportunities for knowledge sharing.
- We’re seeing the rise of dedicated DevOps teams: In our 2014 study, 16% of respondents belonged to a DevOps Department. In 2015, that grew to 19%. Dedicated DevOps teams are often made up of experienced operations people with a mix of skills including using version control, writing infrastructure as code, and continuous delivery. They often exist to address a specific pain point such as deployment automation, but often grow to become more than that.
One of the pitfalls of a dedicated DevOps team is that it can become just another silo. In order to prevent that from happening, it’s critical that these teams evolve to providing shared services for the rest of the organization and also provide coaching, training and support to evangelize DevOps best practices.
Best for: orgs where deployments are extremely painful, need quick results, have the necessary skills in-house, and can’t get appropriate buy-in.
What we see in more mature DevOps organizations is a hybrid approach. There’s typically a small team responsible for providing self-service platforms, and also several product-focused teams that own the end-to-end delivery of a product or service.
Another question we get asked a lot is what are the roles and responsibilities of team members in a DevOps implementation? If you’re an IT manager or a team lead, I highly recommend checking out the 2015 State of DevOps Report, because there’s a whole section for how IT managers can help their teams win.
The main thing if you’re a manager, either on the dev or ops side, is to remove roadblocks for your team by building trust with your counterparts on other teams so that everyone can work more effectively together. Earlier, I talked about how lean management practices contribute to IT performance. If you want to increase the performance of your team, the answer isn’t to pile on more work, but to actually limit work in process so people can complete work. Additionally, providing visible metrics that show flow and quality are great ways to keep everyone on track.
If you’re a practitioner, you’re not off the hook. You also have to learn how to collaborate with your counterparts on other teams as well because trust is one of the major factors in both IT and organizational performance.
If you’re in ops, most of your initial work will be automating away the pain points so you can get to a place where you’re no longer constantly fighting fires. Focus on the quick wins to start and share your your successes.
Are there any QA or QE folks in the room? Quality folks have a lot to teach us about building quality in everything we do.
And devs, please talk to ops early and often as you’re planning deployments.
Some people get really grumpy when you start talking about “DevOps tools” — you’ve all heard the argument, “DevOps is about culture, not tools!” I agree with that statement, but I also believe that tools can drive behavioral change, and ultimately our behaviors become part of the culture.
How many of you at some point moved away from email to a ticketing system? Did your behavior change as a result? Did it force you to think about ownership and priority and how to provide the right level of info to actually get your ticket processed?
Or for those of you working in agile organizations - you know Kanban itself doesn’t make you agile, but it does help you rethink the flow of work.
And we know from our research that these tools, and the practices they enable, are highly correlated with IT performance...
This is just the short list of some of the more common tools in a DevOps toolchain which consists of a distributed version control system, configuration management, continuous integration, deployment and monitoring tools.
Here are some considerations as you’re building your toolchain:
Standardize on the toolchain, and make sure that each tool you choose is compatible with the rest of the toolchain.
Where possible, try to use the same tools your devs are using. Are they already using GitHub and Jenkins? Then those are probably the best choices for your team if you want to promote better cross-collaboration. Set up lunch and learns with them, leverage their expertise, this will help build trust between the teams.
If you're starting from scratch, Start on the left with version control and configuration management and work your way towards the right. Figure out what the smallest thing you can do is, and then build on it, whether that means simply getting all of your scripts under version control, or writing a manifest for a basic OS configuration.
1-800-Flowers, another one of our big customers started by standardizing all of their configurations for their PCI requirements. That’s no small feat, they were able to start small by standardizing configurations for each necessary component, such as NTP, firewall, user permissions, etc. until they had fully configured and automated their entire compliance process, replacing dozens of custom scripts.
Infrastructure as code is necessary for many DevOps practices, but it’s not entirely sufficient on it’s own.
When you combine it with version control, you get this force multiplier effect.
This is where ops teams can learn a lot from devs. With infrastructure as code, you can apply proven, agile development best practices to infrastructure code.
Things like code review, automated testing, and continuous delivery are now possible for system configuration code, making your teams more agile and your systems more reliable.
Together, these practices enable fast feedback loops, the ability to iterate, greater collaboration between dev and ops teams because they’re using the same tools and similar processes, and also greater visibility into infrastructure changes. These are the things we see as key to becoming an agile, lean organization that continuously learns and improves.
We found that use of version control is highly correlated with all of our IT performance metrics: deployment frequency, lead time for changes and mean time to recover.
With your infrastructure code in a version control system, you can quickly produce environments for testing and troubleshooting which increases deployment frequency and reduces your lead time for changes.
It also allows you to quickly identify cause of failure and roll back to the last known good state, which significantly reduces your mean time to recover.
Peer review is one of the biggest benefits of a distributed version control system and this is why.
The data tells us that the traditional way of controlling is highly ineffective.
When external approval is required to deploy to production, IT performance decreases, and contrary to popular belief, change approval boards have very little impact on stability. But when the technical team holds itself accountable for the quality of its code through peer review, we saw that performance actually increases.
In a peer review process, code can be contributed by anyone, devs, ops, quality engineers, infosec, etc. It can can be reviewed by anyone and you can work on it as a team.
One of the awesome benefits of having your infrastructure as code is that you can do continuous delivery to make sure each change to your infrastructure is fully tested before it hits production.
This is important because it a) forces your team to work incrementally, in small batches, making it easier to fix issues as they occur.
It also enables fast feedback loops, which is a common theme across the devops toolchain.
Tools like Puppet, have these continuous delivery workflows built into them so you can easily manage and promote your code.
As you start your DevOps initiative, you also want to think about how you measure success.
There are a lot of different metrics, but we suggest you start with with some simple metrics for throughput and reliability.
My favorite new construct from this year’s report hands down is deployment pain.
We found that deployment pain is highly correlated with IT performance.
The more painful code deployments are, the poorer the organization's IT performance, overall performance and culture.
The reason I love this construct so much is because it gives us a really quick temperature gauge to assess IT performance.
Tomorrow, I want everyone to ask their teams this question: “How painful are your deployments?” and then follow up with “What are the things causing the pain?” Then actively work to prioritize and fix those pain points.
One of the things I’m most proud about is our section on #WomenInTech
There’s a whole body of research that shows that teams with more women members have higher collective
intelligence and achieve better business outcomes.
Despite that, women are leaving STEM fields at alarming rates.
In our survey, only 5% of survey respondents were women
More than half of the survey respondents work on teams that are less than 10% female
A third of the survey respondents said they worked on teams with no women.
We can do better and its up to all of us to make IT better for everyone.