This document summarizes research from four years of studying DevOps practices through surveys. It discusses how the researchers ensured high quality data through psychometrics and statistical analysis of survey questions. Some of their key findings include: IT performance is predictive of organizational performance when implemented effectively; high performing organizations spend more time on new work and less on unplanned work; culture and testing practices are important factors. The researchers were surprised to find correlations did not support some common assumptions, like the relationship between work in progress and performance.
Four years and over 20,000 respondents later, and we have learned a lot about what makes IT and organizational performance awesome. This year we include insights into security, containers, trunk-based development, and lean product management. Tune in for practical take-aways to make your teams' technology transformations even better.
Publish or Perish: Questioning the Impact of Our Research on the Software Dev...Margaret-Anne Storey
A Video for this talk can be found here: https://www.youtube.com/watch?v=DvRdBb9TEUI
Abstract: How often do we pause to consider how we, as a community, decide which developer problems we address, or how well we are doing at evaluating our solutions within real development contexts? Many of our research contributions in software engineering can be considered as purely technical. Yet somewhere, at some time, a software developer may be impacted by our research. In this talk, I invite the community to question the impact of our research on software developer productivity. To guide the discussion, I first paint a picture of the modern-day developer and the challenges they experience. I then present 4+1 views of software engineering research --- views that concern research context, method choice, research paradigms, theoretical knowledge and real-world impact. I demonstrate how these views can be used to design, communicate and distinguish individual studies, but also how they can be used to compose a critical perspective of our research at a community level. To conclude, I propose structural changes to our collective research and publishing activities --- changes to provoke a more expeditious consideration of the many challenges facing today's software developer.
(Thanks to Brynn Hawker for slide design and proposed new badges. brynn@hawker.me)
What I Learned from Four Years of Science-ing the Crap Out of DevOpsVMware Tanzu
SpringOne Platform 2016
Speaker: Nicole Forsgren; IT Impacts Expert, Chef
Four years, over 25,000 DevOps data points, and some science... What did we find? Well, the headline is that IT does matter if you do it right. With a mix of technology, processes, and a great culture, IT contributes to organizations' profitability, productivity, and market share. We also found that using continuous delivery and lean management practices not only makes IT better -- giving you throughput and stability without tradeoffs -- but it also improves quality and security outcomes and makes your work feel better -- making your organizational culture better and decreasing burnout. Dr. Nicole Forsgren will share these findings as well as tips and tricks to help make your own DevOps.
Building evidence-based guidelines: the role of emotions in Stack Overflow
15th International Advanced School on Empirical Software Engineering (IASESE 2018), October 10, 2018 - Oulu, Finland
An overview of RATIONAL DECISION-MAKING AFFECTING LONG- TERM DECISIONS
For my Problem Analysis and Decision Making class, Doctor of Education major in Educational Administration
Four years and over 20,000 respondents later, and we have learned a lot about what makes IT and organizational performance awesome. This year we include insights into security, containers, trunk-based development, and lean product management. Tune in for practical take-aways to make your teams' technology transformations even better.
Publish or Perish: Questioning the Impact of Our Research on the Software Dev...Margaret-Anne Storey
A Video for this talk can be found here: https://www.youtube.com/watch?v=DvRdBb9TEUI
Abstract: How often do we pause to consider how we, as a community, decide which developer problems we address, or how well we are doing at evaluating our solutions within real development contexts? Many of our research contributions in software engineering can be considered as purely technical. Yet somewhere, at some time, a software developer may be impacted by our research. In this talk, I invite the community to question the impact of our research on software developer productivity. To guide the discussion, I first paint a picture of the modern-day developer and the challenges they experience. I then present 4+1 views of software engineering research --- views that concern research context, method choice, research paradigms, theoretical knowledge and real-world impact. I demonstrate how these views can be used to design, communicate and distinguish individual studies, but also how they can be used to compose a critical perspective of our research at a community level. To conclude, I propose structural changes to our collective research and publishing activities --- changes to provoke a more expeditious consideration of the many challenges facing today's software developer.
(Thanks to Brynn Hawker for slide design and proposed new badges. brynn@hawker.me)
What I Learned from Four Years of Science-ing the Crap Out of DevOpsVMware Tanzu
SpringOne Platform 2016
Speaker: Nicole Forsgren; IT Impacts Expert, Chef
Four years, over 25,000 DevOps data points, and some science... What did we find? Well, the headline is that IT does matter if you do it right. With a mix of technology, processes, and a great culture, IT contributes to organizations' profitability, productivity, and market share. We also found that using continuous delivery and lean management practices not only makes IT better -- giving you throughput and stability without tradeoffs -- but it also improves quality and security outcomes and makes your work feel better -- making your organizational culture better and decreasing burnout. Dr. Nicole Forsgren will share these findings as well as tips and tricks to help make your own DevOps.
Building evidence-based guidelines: the role of emotions in Stack Overflow
15th International Advanced School on Empirical Software Engineering (IASESE 2018), October 10, 2018 - Oulu, Finland
An overview of RATIONAL DECISION-MAKING AFFECTING LONG- TERM DECISIONS
For my Problem Analysis and Decision Making class, Doctor of Education major in Educational Administration
Sophos Day Belgium - This is Next-Gen IT Security (Sophos Intercept X)Sophos Benelux
Mark Loman showed the audience Sophos' next-generation signatureless endpoint solution which tackles exploits, zero-days, ransomware and any other known and unknown types of malware.
The Secrets of High Performance: Science Edition - Nicole Forsgren - Codemoti...Codemotion
Nicole has spent the last four years researching high-performing IT teams, and the impact of IT performance on organizational performance. In this talk, she will present the key factors that enable not just higher throughput but also higher stability and quality, lower cost, and happier teams. Discover how continuous delivery and lean management practices produce higher IT performance (and indeed what IT performance means), along with how to measure culture and its impact on our work. Learn the patterns and practices used by high-performing organizations to outcompete their peers.
For years, there have been stories of continuous delivery making teams awesome… but can CD make all teams awesome? And how? Dr. Nicole Forsgren will present data from over 20,000 technical professionals showing the central role that CD plays in software development and delivery. She will show you how doing CD can drive key organizational outcomes like profitability, productivity, and market share. Nicole also presents the key aspects of CD that make your DevOps awesome, like trunk-based development, test data, and test automation, and provides examples of success from teams undergoing their own technology transformations. The presentation also includes other important drivers of DevOps success, like lean product management and team culture. At the end of this talk, you will have the information to help you prove your case (to management or even yourself) about why CD and DevOps are essential to winning, as well as great stories and examples to really bring these concepts to life. You’ll leave with tips you can take back to get started on your own DevOps initiative.
What we learned from three years sciencing the crap out of devopsNicole Forsgren
Three years, 20,000 DevOps professionals, and some science... What did we find? Well, the headline is that IT *does* matter if you do it right. With a mix of technology, processes, and a great culture, IT contributes to organizations' profitability, productivity, and market share. We also found that using continuous delivery and lean management practices not only makes IT better -- giving you throughput and stability without tradeoffs -- but it also makes your work feel better -- making your organizational culture better and decreasing burnout. Jez and Nicole will share these findings as well as tips and tricks to help make your own DevOps transformation awesome.
Sophos Day Belgium - This is Next-Gen IT Security (Sophos Intercept X)Sophos Benelux
Mark Loman showed the audience Sophos' next-generation signatureless endpoint solution which tackles exploits, zero-days, ransomware and any other known and unknown types of malware.
The Secrets of High Performance: Science Edition - Nicole Forsgren - Codemoti...Codemotion
Nicole has spent the last four years researching high-performing IT teams, and the impact of IT performance on organizational performance. In this talk, she will present the key factors that enable not just higher throughput but also higher stability and quality, lower cost, and happier teams. Discover how continuous delivery and lean management practices produce higher IT performance (and indeed what IT performance means), along with how to measure culture and its impact on our work. Learn the patterns and practices used by high-performing organizations to outcompete their peers.
For years, there have been stories of continuous delivery making teams awesome… but can CD make all teams awesome? And how? Dr. Nicole Forsgren will present data from over 20,000 technical professionals showing the central role that CD plays in software development and delivery. She will show you how doing CD can drive key organizational outcomes like profitability, productivity, and market share. Nicole also presents the key aspects of CD that make your DevOps awesome, like trunk-based development, test data, and test automation, and provides examples of success from teams undergoing their own technology transformations. The presentation also includes other important drivers of DevOps success, like lean product management and team culture. At the end of this talk, you will have the information to help you prove your case (to management or even yourself) about why CD and DevOps are essential to winning, as well as great stories and examples to really bring these concepts to life. You’ll leave with tips you can take back to get started on your own DevOps initiative.
What we learned from three years sciencing the crap out of devopsNicole Forsgren
Three years, 20,000 DevOps professionals, and some science... What did we find? Well, the headline is that IT *does* matter if you do it right. With a mix of technology, processes, and a great culture, IT contributes to organizations' profitability, productivity, and market share. We also found that using continuous delivery and lean management practices not only makes IT better -- giving you throughput and stability without tradeoffs -- but it also makes your work feel better -- making your organizational culture better and decreasing burnout. Jez and Nicole will share these findings as well as tips and tricks to help make your own DevOps transformation awesome.
The Data on DevOps: Making the Case for AwesomeNicole Forsgren
What’s the value proposition of DevOps? Does culture change show up in the bottom line? What practices predict high IT performance? We hear many stories to inspire and inform us, but the plural of anecdote is not data. Let’s dive into the research and find out which DevOps practices drive optimal IT and business outcomes.
The data shows that the best IT performers have the highest throughput and reliability while contributing to organizational profitability, productivity, and market share goals. Industry trends around security, containers, continuous delivery, and lean management relate to IT performance and quality: let’s talk about how.
Management and practitioners alike will leave with a better understanding of how to achieve the best outcomes, while armed with the data they need to make the case for change.
Culture is very important in DevOps. It is the first thing in every definition of DevOps, but how can you measure it? Culture is intangible, hard to change, and it is of vital importance to your company and your employee’s satisfaction. Everyone agrees that a culture of trust and collaboration is key to a successful DevOps transformation. Having a culture of collaboration where people feel safe to share their views and work across a diverse group is a must for a successful organization. But how do we measure culture?
In this session we will talk about the culture of DevOps and how the culture enable information flow through organizations. We talk about the Westrum Typology of Organizational Culture and how organizational culture predicts the way information flows through an organization. We’ll talk about how to measure your culture based on the Westrum Typology and steps to move to a generative culture of high trust and high collaboration across the organization.
Perhaps in no other professional field is the dichotomy between theory and practice more starkly different than in the realm of software testing. Researchers and thought leaders claim that testing requires a high level of cognitive and interpersonal skills, in order to make judgments about the ability of software to fulfill its operational goals. In their minds, testing is about assessing and communicating the risks involved in deploying software in a specific state.
However, in many organizations, testing remains a necessary evil, and a cost to drive down as much as possible. Testing is merely a measure of conformance to requirements, without regard to the quality of requirements or how conformance is measured. This is certainly an important measure, but tells an incomplete story about the value of software in support of our business goals.
We as testers often help to perpetuate the status quo. Although in many cases we realize we can add far more value than we do, we continue to perform testing in a manner that reduces our value in the software development process.
This presentation looks at the state of the art as well of the state of common practice, and attempts to provide a rationale and roadmap whereby the practice of testing can be made more exciting and stimulating to the testing professional, as well as more valuable to the product and the organization.
Four years, 25,000+ DevOps professionals, and some science... What did we find? Well, the headline is that IT *does* matter if you do it right. With a mix of technology, processes, and a great culture, IT contributes to organizations' profitability, productivity, and market share. We also found that using continuous delivery and lean management practices not only makes IT better -- giving you throughput and stability without tradeoffs -- but it also makes your work feel better -- making your organizational culture better and decreasing burnout. Nicole will share these findings as well as tips and tricks to help make your own DevOps transformation awesome.
Adopting a Continual Improvement Mindset for ITJosh Atwell
Few organizations feel they are reaching their true potential. Technical debt, antiquated processes, outdated measurements, and a never-ending influx of new requirements leave most feeling incapable of doing much more than keeping the lights on. Overcoming these challenges and achieving meaningful change doesn't happen overnight, but is a necessity in order to create the next generation of IT operations and create the foundation for DevOps success.
This session will explore techniques that modern IT organizations are adopting to become more agile, adopt new technologies like containers, new processes like DevOps, and build a culture of continual improvement. We will touch on how to:
• Improve responsiveness, collaboration, and learning across teams
• Adopting and supporting new technologies like containers, microservices, and automation
• Gain more visibility into your environments and processes to identify constraints
• Grow beyond firefighting and just getting the next feature out
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.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
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.
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.
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.
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
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
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 the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
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.
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
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.
2. @nicolefv
@jezhumble
Outline
How to make your data suck less
• Writing good survey questions
• Making sure the survey questions are good
- with SCIENCE
• (These methods apply to your system and
log data)
What we found… that we did (AND didn’t) expect
Things about Continuous Delivery
Things about Management
6. @nicolefv
@jezhumble
We use
PSYCHOMETRICS
to make our survey data good*
*or give us a reasonable assurance that it’s telling us
what we think it’s telling us (& some of this can also apply
to your log data)
7. @nicolefv
@jezhumble
Psychometrics includes:
Construct creation (manual)
• When possible: use previously validated
constructs
• Based on definitions and theory, carefully and
precisely worded, card sorting task, pilot tested
Construct evaluation (statistics)
• Establishing Validity: discriminant and
convergent
• Establishing Reliability
8. @nicolefv
@jezhumble
Psychometrics Writing
Example: Culture
• Does it matter to our study?
• More than just intuition?
• What KIND of culture?
• National identity and norms
• Adaptive culture
• Value learning (2014 study)
• Value information flow and trust (2014 and 2015
studies -- Westrum culture)
9. @nicolefv
@jezhumble
Psychometrics Writing
Example: Culture
• Does it matter to our study?
• More than just intuition?
• What KIND of culture?
• National identity and norms
• Adaptive culture
• Value learning (2014 study)
• Value information flow and trust (2014 and 2015
studies -- Westrum culture)
10. @nicolefv
@jezhumble
Westrum typology
Pathological
Power-oriented
Bureaucratic
Rule-oriented
Generative
Performance-oriented
Low cooperation Modest cooperation High cooperation
Messengers shot Messengers neglected Messengers trained
Responsibilities shirked Narrow responsibilities Risks are shared
Bridging discouraged Bridging tolerated Bridging encouraged
Failure leads to scapegoating Failure leads to justice Failure leads to inquiry
Novelty crushed Novelty leads to problems Novelty implemented
Try writing
items
yourself!
Use strong
statements
with clear
language.
Westrum, R. (2004). A typology of organisational cultures. Quality and safety in health care, 13(suppl 2), ii22-ii27.
11. @nicolefv
@jezhumble
Westrum Culture Items
• On my team, information is actively sought.
• On my team, failures are learning
opportunities, and messengers of them are not
punished.
• On my team, responsibilities are shared.
• On my team, cross-functional collaboration is
encouraged and rewarded.
• On my team, failure causes inquiry.
• On my team, new ideas are welcomed.
Found
to be
valid &
reliable
Predictive of
IT Performance &
Organizational
Performance
12. @nicolefv
@jezhumble
Psychometrics Analysis
Example: Notification of Failure
Original
in 2014,
but there
was a
surprise.
Can you
spot it?
At my organization…
• We are primarily notified of failures by reports from
customers.
• We are primarily notified of failures by the NOC.
• We get failure alerts from logging and monitoring
systems.
• We monitor system health based on threshold
warnings (ex. CPU exceeds 100%).
• We monitor system health based on rate-of-change
warnings (ex. CPU usage has increased by 25% over the
last 10 minutes).
13. @nicolefv
@jezhumble
At my organization…
• We are primarily notified of failures by reports from
customers.
• We are primarily notified of failures by the NOC.
• We get failure alerts from logging and monitoring
systems.
• We monitor system health based on threshold
warnings (ex. CPU exceeds 100%).
• We monitor system health based on rate-of-change
warnings (ex. CPU usage has increased by 25% over the
last 10 minutes).
Notification
from
NEAR
Notification
from
FAR
Psychometrics Analysis
Example: Notification of Failure
14. @nicolefv
@jezhumble
More data tests!
Plus, we test to make sure the survey doesn’t have
other problems.
• Common method variance (CMV) (aka CMB for
Bias)
• Early vs. late responders
• Survey drop-off rates and bias
16. @nicolefv
@jezhumble
A note about analysis methods
One of three conditions must be met:
1. Longitudinal (no, this is cross-sectional)
2. Randomized, experimental design (no, this
is a non-experimental)
3. Theory-based design
When this condition was not met, only
correlations were tested and reported
17. @nicolefv
@jezhumble
KEY FINDING:
IT Performance and its
behavior
A combination of throughput and stability
• lead time for changes
• release frequency
• time to restore service
• change fail rate
Forsgren, N., J. Humble (2016). "DevOps: Profiles in ITSM Performance and Contributing Factors." In the
Proceedings of the Western Decision Sciences Institute (WDSI) 2016, Las Vegas, NV.
18. @nicolefv
@jezhumble
KEY FINDING:
IT performance matters!
“Firms with high-performing IT organizations were
twice as likely to exceed their profitability, market
share and productivity goals.”
IT Performance is predictive of
organizational performance.
http://bit.ly/2014-devops-report/
http://bit.ly/2015-devops-report/
Forsgren, N., J. Humble (2016). “The Role of Continuous Delivery in IT and Organizational
Performance.” In the Proceedings of the Western Decision Sciences Institute (WDSI)
2016, Las Vegas, NV.
22. @nicolefv
@jezhumble
Which of these measure effective test
practices?
Developers primarily create & maintain acceptance tests
QA primarily create & maintain acceptance tests
Primarily created & maintained by outsourced party
When automated tests pass, I’m confident the software is releasable
Test failures are likely to indicate a real defect
It’s easy for developers to fix acceptance tests
Developers share a common pool of test servers to reproduce failures
Developers create on demand test environments
Developers use their own dev environments to reproduce failures
23. @nicolefv
@jezhumble
Which of these measure effective test
practices?
Developers primarily create & maintain acceptance tests
QA primarily create & maintain acceptance tests
Primarily created & maintained by outsourced party
When automated tests pass, I’m confident the software is releasable
Test failures are likely to indicate a real defect
It’s easy for developers to fix acceptance tests
Developers share a common pool of test servers to reproduce failures
Developers create on demand test environments
Developers use their own dev environments to reproduce failures
26. @nicolefv
@jezhumble
Identity & Google items
• I am glad I chose to work for this
organization rather than another
company.
• I talk of this organization to my friends as a
great company to work for.
• I am willing to put in a great deal of effort
beyond what is normally expected to help
my organization to be successful.
• I find that my values and my organization's
values are very similar.
• In general, the people employed by my
organization are working toward the same
goal.
• I feel that my organization cares about me.
Adapted from adapted from Atreyi Kankanhalli, Bernard C.Y. Tan, and
Kwok-Kee Wei (2005), “Contributing Knowledge to Electronic Knowledge
Repositories: An Empirical Investigation,“ MIS Quarterly, 29, 113-143.
27. @nicolefv
@jezhumble
Identity & Google items
• I am glad I chose to work for this organization
rather than another company.
• I talk of this organization to my friends as a
great company to work for.
• I am willing to put in a great deal of effort
beyond what is normally expected to help my
organization to be successful.
• I find that my values and my organization's
values are very similar.
• In general, the people employed by my
organization are workingtoward the same
goal.
• I feel that my organization caresabout me.
Adapted from adapted from Atreyi Kankanhalli, Bernard C.Y.
Tan, and Kwok-Kee Wei (2005), “Contributing Knowledge to
Electronic Knowledge Repositories: An Empirical Investigation,“
MIS Quarterly, 29, 113-143.
Westrum items
30. @nicolefv
@jezhumble
Now for management stuff
We all know managing WIP is important, right?
Correlation between WIP and ITPerf is negligible
What’s going on?
33. @nicolefv
@jezhumble
Conclusions
• Even if you think it’s obvious, TEST WITH
DATA.
• (if the results don’t surprise you, you’re doing it wrong)
• (if you don’t also confirm some things you expected,
you’re doing it wrong)
• We CAN have it all, or at least throughput
AND stability.
• IT matters (but you have to do it right)
• DevOps culture & practices have a
measurable impact on IT & org perf