The document discusses lean product management and user-centered app design. It covers topics like doing just enough to provide early value to users, eliminating waste, engaging workforces with few meetings and continuous delivery, and learning just enough, designing just enough, and delivering just enough. The secrets to being a modern software organization are said to be speed to market, customer focus, and engaged workforce. Critical components of a successful product are described as being desirable, viable, and feasible.
This document discusses developer nirvana and DevOps excellence at WWT. It introduces Jim Hopkins, the Container Practice Manager. It then defines nirvana and explains how DevOps aims to achieve nirvana in IT through work-life balance, reducing toil, workplace joy, team development, and blameless learning. The document outlines that DevOps is a way of working through culture, automation, lean practices, measurement, and sharing. It emphasizes key DevOps metrics like deployment frequency and time to recovery. Finally, it describes WWT's DevOps journey and highlights experimentation.
So often, we talk about doing the DevOps for money, fame, and high performance. But DevOps was the original hipster of changing the way we work to take care of ourselves and each other. In this talk, Nicole Forsgren will discuss how these technology transformations can not only help us ship software with speed and stability, they can reduce burnout, improve our culture, and communicate better. She will also share the latest research from her team about productivity, and what this means for the future of work -- spoiler alert: productivity is personal. As we shift back into work patterns that look like normal (whatever normal is), we can reimagine cultures and technologies that shift to support us and our teams -- just like DevOps did in its beginning.
The Home Depot has over 3500 engineers averaging nearly 6000 git commits per day, with 91% of software written in-house. They have invested $11.1 billion over 4 years, hiring over 1000 new engineers to transform the company from projects to products and experiences. They focus on living their culture and values by investing in associates through cohorts, ongoing education, and onboarding to create an attractive environment for engineers while accomplishing great things like award-winning mobile apps and changing associates' lives.
What I learned from 5 years of sciencing the crap out of DevOpsDevOpsDays DFW
For years we laboured under the misapprehension that going faster meant breaking things. After several years of science-ing, Jez and Dr Nicole Forsgren have identified the key elements that enable not just higher throughput but also higher stability, availability and quality, lower cost, and happier teams. Discover how continuous delivery, cloud infrastructure, and effective management and leadership practices produce higher software delivery performance (and indeed what we might mean by performance), along with how to measure culture and its impact on IT and organizational culture. Find out how we actually ensure our results are reliable and meaningful. Learn the patterns and practices used by high performing organizations to outcompete their peers.
Soaring in the Clouds - Don't be dragged down by ITIL bloat! Navvia
Cloud computing is here and being used by organizations to allow them to be more fleet footed in time to market, and nimble in aligning to changing business needs when it comes to delivering the services to the business and its customers. From a service management perspective it makes no difference wether the service is delivered from the "Cloud", an in house hosted infrastructure or a combination of both. You still need a framework for managing service delivery and ensuring services.
Presentation by Brian Lenner, Principal Consultant at Navvia.
Visit http://navvia.com to know more.
The document discusses lean product management and user-centered app design. It covers topics like doing just enough to provide early value to users, eliminating waste, engaging workforces with few meetings and continuous delivery, and learning just enough, designing just enough, and delivering just enough. The secrets to being a modern software organization are said to be speed to market, customer focus, and engaged workforce. Critical components of a successful product are described as being desirable, viable, and feasible.
This document discusses developer nirvana and DevOps excellence at WWT. It introduces Jim Hopkins, the Container Practice Manager. It then defines nirvana and explains how DevOps aims to achieve nirvana in IT through work-life balance, reducing toil, workplace joy, team development, and blameless learning. The document outlines that DevOps is a way of working through culture, automation, lean practices, measurement, and sharing. It emphasizes key DevOps metrics like deployment frequency and time to recovery. Finally, it describes WWT's DevOps journey and highlights experimentation.
So often, we talk about doing the DevOps for money, fame, and high performance. But DevOps was the original hipster of changing the way we work to take care of ourselves and each other. In this talk, Nicole Forsgren will discuss how these technology transformations can not only help us ship software with speed and stability, they can reduce burnout, improve our culture, and communicate better. She will also share the latest research from her team about productivity, and what this means for the future of work -- spoiler alert: productivity is personal. As we shift back into work patterns that look like normal (whatever normal is), we can reimagine cultures and technologies that shift to support us and our teams -- just like DevOps did in its beginning.
The Home Depot has over 3500 engineers averaging nearly 6000 git commits per day, with 91% of software written in-house. They have invested $11.1 billion over 4 years, hiring over 1000 new engineers to transform the company from projects to products and experiences. They focus on living their culture and values by investing in associates through cohorts, ongoing education, and onboarding to create an attractive environment for engineers while accomplishing great things like award-winning mobile apps and changing associates' lives.
What I learned from 5 years of sciencing the crap out of DevOpsDevOpsDays DFW
For years we laboured under the misapprehension that going faster meant breaking things. After several years of science-ing, Jez and Dr Nicole Forsgren have identified the key elements that enable not just higher throughput but also higher stability, availability and quality, lower cost, and happier teams. Discover how continuous delivery, cloud infrastructure, and effective management and leadership practices produce higher software delivery performance (and indeed what we might mean by performance), along with how to measure culture and its impact on IT and organizational culture. Find out how we actually ensure our results are reliable and meaningful. Learn the patterns and practices used by high performing organizations to outcompete their peers.
Soaring in the Clouds - Don't be dragged down by ITIL bloat! Navvia
Cloud computing is here and being used by organizations to allow them to be more fleet footed in time to market, and nimble in aligning to changing business needs when it comes to delivering the services to the business and its customers. From a service management perspective it makes no difference wether the service is delivered from the "Cloud", an in house hosted infrastructure or a combination of both. You still need a framework for managing service delivery and ensuring services.
Presentation by Brian Lenner, Principal Consultant at Navvia.
Visit http://navvia.com to know more.
This document provides guidance on transitioning an organization to a DevOps model. It discusses how organizational structures can impact technical designs based on Conway's Law. It then covers common anti-patterns when shifting to DevOps like relying on a single consultant. The document proposes using a logical rather than structural view of the organization and modeling it after Spotify's Guild model. It offers tips for facilitating collaboration between teams and overcoming challenges to change. Finally, it addresses technical transition topics like security as code and environment consistency. The overall message is that organizational change requires clear communication, addressing business needs, facilitating cross-team work, and setting ambitious yet achievable goals.
If you don't know where you're going it doesn't matter how fast you get thereNicole Forsgren
The best-performing organizations have the highest quality, throughput, and reliability while also delivering value. They are able to achieve this by focusing on a few key measurement principles, which Nicole and Jez will outline in this talk. These include knowing your outcome measuring it, capturing metrics in tension, and collecting complementary measures… along with a few others. Nicole and Jez explain the importance of knowing how (and what) to measure—ensuring you catch successes and failures when they first show up, not just when they’re epic, so you can course correct rapidly. Measuring progress lets you focus on what’s important and helps you communicate this progress to peers, leaders, and stakeholders, and arms you for important conversations around targets such as SLOs. Great outcomes don’t realize themselves, after all, and having the right metrics gives us the data we need to be great SREs and move performance in the right direction.
This document appears to be a slide presentation on DevOps practices and culture. Some key points discussed include:
- High-performing IT organizations are twice as likely to exceed goals in areas like profitability and customer satisfaction.
- DevOps focuses on continuous delivery, quality, lean processes, effective collaboration, and a culture of learning from failures.
- Culture can be measured and influenced by providing employees the tools and training to do their jobs successfully.
- Adopting DevOps practices may lead to improved lead times, release frequency, change fail rates, and service restoration times.
iSQI Certification Days DASA – DevOps & ISTQB Frank FrambachIevgenii Katsan
Frank Frambach presented on DevOps and testing. Some key points:
1. DevOps is driven by digital business models that require faster development and delivery of new features.
2. The DevOps Agile Skills Association (DASA) provides a competence model and certification program to develop high-performing IT professionals in DevOps.
3. Testing is an important part of DevOps and is integrated into several areas of the DASA competence model, including test specification, programming, and infrastructure engineering.
4. Bob, a tester, is shown undertaking a journey through the DASA model, first learning about DevOps and then developing his skills in related areas to transition into a DevOps
Successful writing at work copyright 2017 cengage learnssusere73ce3
This document is the table of contents for a book about successful writing at work. It outlines the contents of the book, which covers topics such as identifying audiences, establishing purpose, adapting style and tone for different audiences, characteristics of job-related writing, writing ethically, the writing process of researching, planning, drafting, revising and editing, collaborative writing, and conducting effective meetings. The table of contents provides an overview of what is covered in each chapter to help readers understand what content is included in the book.
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.
The Phoenix Project DevOps Simulation - Paul WilkinsonPink Elephant
ncorporating DevOps – The Phoenix Project Simulation
Businesses are demanding ever shorter release cycles for new applications. Traditionally ‘Operations’ is seen as a barrier with lengthy bureaucratic controls and delays in provisioning production systems. DevOps is a growing movement for shortening development and deployment and integrating Development and Operations. However, this requires a mind-set shift, new behaviours and a cultural shift in both Development and Operations. Traditionally suspicious of each other, they must now work closely together. Yet many companies are struggling to adopt and deploy DevOps and how to change the culture.
The “Phoenix Project” Simulation game is based upon The Phoenix Project. Parts Unlimited is in trouble. Newspaper reports reveal the poor financial performance of the organisation. The only way forward to not only save the company but to make it competitive and profitable is “The Phoenix Project” which represents an IT enabled business transformation, with Retail Operations as the business owner of this project. The VP of IT Operations is asked to take the lead of the IT department and ensure that “The Phoenix Project” will be a success. But the VP of IT Operations is facing a tremendous amount of work. A huge backlog of issues, features and projects. Are you up for the challenge…?
DOES15 - Elisabeth Hendrickson - Its All About FeedbackGene Kim
Elisabeth Hendrickson, VP of Engineering, Pivotal’s Big Data Suite
Fifteen years ago I was running a traditional QA department, and I had a horrifying realization: the better I got at my job, the worse I made things for the organization as a whole. This counter-intuitive realization spurred me on a journey to understand the relationship between testing and quality, and ultimately to the study of feedback loops in software development processes. Ultimately I found my way to Extreme Programming, and now work at Pivotal where we practice a particularly opinionated form of it. In this talk you’ll hear about my journey from the traditional silos with inherently long feedback latency to my current reality of increasingly tight feedback loops, and the lessons I’ve learned along the way.
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017DevOpsGroup
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017. 9 steps to DevOps Transformation
#SystemsThinking
#MakeWorkVisible
#MeasureWhatsImportant
#ActOnFeedback
#IdentifyTheGoal
#BeAgile
#DeliverContinuously
#BuildTrust
#AlignToValue
#OptimiseForFlow
The Key to High Performance - What the Data SaysNicole Forsgren
Over the past five years, the State of DevOps Report has shown that high-performing IT teams decisively outperform their peers: they deploy 200x more frequently, with 2,555 faster lead times and 1/3 change fail rate. This year, we investigate architecture, experimentation in work, other business outcomes (e.g., for gov't). Come see the latest in what it takes to make software amazing.
DevOps – the future of Agile – why, what, how? Agile Israel 2014Yuval Yeret
DevOps is the new favorite buzzword in many organizations. We will understand what it is all about, why it is necessary and what makes it so popular, how it is related to Agile, some pitfalls/myths, and most importantly some concrete steps organizations can take to become a more DevOps-oriented organization and enjoy benefits like more frequent less painful software deployments and operation and better collaboration between Dev and Ops organizations.
http://agileisrael2014.com/devops-the-future-of-agile/
Eind augustus is het Accelerate: State of DevOps Report 2018 uitgebracht. Zoals in dit rapport wordt aangegeven is IT belangrijk voor veel organisaties, en door goed te zijn op IT gebied wordt het eenvoudiger om (commerciële) bedrijfsdoelstellingen te behalen. Goed presteren als organisatie kan worden bereikt door goed te zijn (en elke dag beter te worden) DevOps gebied. Beter worden in DevOps betekent dat je elke dag moet werken aan het verbeteren van competenties die belangrijk zijn wanneer je in DevOps werkt. Maar welke competenties moet je ontwikkelen? En hoe presteer je daar vandaag op? Hoe kun je verbeteren op deze competenties zodat je morgen, volgende week en volgende maand beter wordt?
In deze sessie zal ik een overzicht geven van het DevOps Acceleration Program zoals wij deze hebben ontwikkelen. Dit programma zal een antwoord geven op voorgaande vragen en helpen te bepalen waar je welke verbetering kunt en moet doorvoeren. Belangrijk onderdeel van dit programma is het DevOps Assessment ontwikkeld door DevOps Research and Assessment (DORA), maar het is meer dan dat. Door een gezamenlijk een verbeterplan voor de komende 6 maanden op maat op te stellen en te focussen op een beperkt aantal competenties kun je daadwerkelijk verbeteren. Na 6 maanden doen we een meting om de gerealiseerde voortgang te bepalen en input te geven voor een nieuw verbeterplan.
Why #DevOps Transformation has to start with youDevOpsGroup
Why #DevOps Transformation has to start with you.
You are part of your organisation's culture, and in order to change the culture you need to change yourself, first. Learn some useful ideas of personal and DevOps Transformation from the @DevOpsGuys.
Moving forward in your DevOps journey—What's your next step after CA World?CA Technologies
A perspective from within CA Technologies on where to start and how to progress in your DevOps journey to ultimately become successful in today's application economy.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
Navvia is always looking for ways to improve how we do things and we’ve come to see DevOps as our compass on the road to continual improvement. However, DevOps means different things to different people.
To our company, it has become the rallying cry for organizational change. It is the standard that leads us on a path towards better alignment across teams, enhanced agility, higher quality and the elimination of waste.
What you will learn:
- Why Navvia embarked on DevOps
- An overview of DevOps including common misconceptions
- A case study entitled “a tale of two apps”
- How Navvia is implementing DevOps
- What we’ve learned so far
It’s an exciting journey with the destination being improved customer experience, higher rates of innovation and a faster path to business value.
AgileLIVE: Continuous Product Learning - Part 1VersionOne
How sure are you that you are “building the right thing?” How often do you validate your assumptions versus simply measuring your progress? While agile methods often help organizations build products faster, many software teams get hyper-focused on points completed over real value delivered – or, more important, learning about customers and validating product ideas. Some people obsess over “backlog grooming,” but still produce weak stories that do not provide the context needed for teams and programs to deliver valuable products. Watch the webinar recording here: http://ow.ly/C5F09
Agile 2014- Metrics driven development and devopsKarthik Gaekwad
There are many facets of devops, and we will spend our time in this presentation focusing on collecting and using metrics (business, application, system, etc.) and building a metrics driven culture in organizations.
We will define how we have seen devops progress in our organizations and how we’ve realized that different teams in our organizations can find common ground when teams (who have different roles) can work well together when they use metrics as the common language.
Karthik will talk about how we are using the principles from the Lean Startup to define our development cycles, sprints and using metrics to quantify how successful the products we are trying to come out with in R&D. Initially we started practicing devops on the dev and ops side of the house but realized this was still a black box to the business side of the house, so we pivoted to what our business actually understood, and that was metrics; today, we focus more on metrics (business and system level), and can fail or succeed fast to achieve our business goals faster than before.
Ernest will go into detail on how a large, mature SaaS organization uses metrics in conjunction with distributed agile development and DevOps to guide their development at scale. How much a product is used, how much each feature is used, and how much value each user gets out of it are key drivers for a business strategy - and it’s all information that’s emitted by a system. He'll show how large companies have invested time in collecting and using these metrics to guide their decisions and influence their culture.
5 Keys to Building a Successful DevOps CultureMandi Walls
This document provides 5 keys to building a successful DevOps culture: 1) Setting clear and measurable goals, 2) Gaining executive support, 3) Building pilot projects to test changes, 4) Providing training and prioritizing workloads, and 5) Doing outreach and evangelism. It emphasizes that culture change is difficult and requires focusing on behaviors and values over tools. Pilot projects allow practicing new processes in a controlled way before organization-wide adoption. Training, workload prioritization, and addressing dissenters are important for successful adoption of changes. Regular communication and showcasing results helps spread DevOps practices. Patience, executive engagement, and overcommunication are also advised.
DOES15 - Heather Mickman & Ross Clanton - (Re)building an Engineering Culture...Gene Kim
Heather Mickman, Senior Group Manager, Target
Ross Clanton, Director, Target
This talk will largely be a reflection on the DevOps journey at Target and the focus on (re)building an engineering culture at Target. In the DevOps community you hear a lot of talk about whether you should drive DevOps in to an organization tops down or bottoms up. Well, we did a hybrid of both. It definitely started at Target as a grass roots movement in a few small teams and started to gain broader grassroots momentum when we kicked off our first internal DevOps Days in February 2014. This enabled us to start engaging a community, finding out who had passion for this across our IT organization, and providing them a forum to connect, share, and learn about DevOps awesomeness. We fostered and grew this community by leveraging social media and guerilla marketing to start driving the conversation across our organization as well as demonstrating the success that teams were having. We then leveraged some of this early energy to engage more leader champions to start building the tops down support for DevOps. Now, having completed four DevOps Days conferences at Target, we will share more details on our approach, results, speakers, and topics.
We did much more than just hosting DevOps Days. We tapped in to that growing community to start testing and learning some different approaches and we have lots to share, both in terms of results we’ve achieved and how we’re focusing on changing culture and mindsets. From a technology perspective, we will discuss how we rapidly drove momentum on our automation toolchain across our IT organization. Our vision was to enable and empower all technologists to automate the things that they were accountable for. We pursued this vision in many ways, including Automation hackathons, establishing an embedding/coaching model for our deep SMEs to help teach, open labs, community based support, and even schemed some creative work models that we will share.
The end result of these various activities is driving full stack ownership that will ultimately enable the expansion of CI/CD across our Enterprise. This is the overarching theme and next step in our enterprise transformation. It is through this foundation we are building around culture, tooling, collaborative and flexible work models that will enable our acceleration in 2015. Moving forward, we are leveraging these learnings to shift to more of a full-stack product model for our technology delivery and management. We’re also transforming infrastructure from a model based on technology silos to an end to end infrastructure service model focused on enabling business agility.
These changes haven’t been easy. In fact, we’ve already had a lot of learnings on our journey. We will share some of those key challenges and lessons learned, specifically on talent, culture, and leadership.
How DevOps is Transforming IT, and What it Can Do for AcademiaNicole Forsgren
This document discusses how DevOps is transforming IT and what it can do for academia. DevOps is a cultural and professional movement focused on building and operating high-velocity organizations. It promotes people, technology, process, culture and experience. DevOps delivers more throughput and stability for companies. It also fosters a culture of innovation, experimentation and open communication. The document suggests academia can benefit from DevOps by embracing an open culture, sharing curriculum resources, using minimum viable products and iterating based on different team needs. DevOps principles can help improve collaboration and innovation in academic settings.
This document provides guidance on transitioning an organization to a DevOps model. It discusses how organizational structures can impact technical designs based on Conway's Law. It then covers common anti-patterns when shifting to DevOps like relying on a single consultant. The document proposes using a logical rather than structural view of the organization and modeling it after Spotify's Guild model. It offers tips for facilitating collaboration between teams and overcoming challenges to change. Finally, it addresses technical transition topics like security as code and environment consistency. The overall message is that organizational change requires clear communication, addressing business needs, facilitating cross-team work, and setting ambitious yet achievable goals.
If you don't know where you're going it doesn't matter how fast you get thereNicole Forsgren
The best-performing organizations have the highest quality, throughput, and reliability while also delivering value. They are able to achieve this by focusing on a few key measurement principles, which Nicole and Jez will outline in this talk. These include knowing your outcome measuring it, capturing metrics in tension, and collecting complementary measures… along with a few others. Nicole and Jez explain the importance of knowing how (and what) to measure—ensuring you catch successes and failures when they first show up, not just when they’re epic, so you can course correct rapidly. Measuring progress lets you focus on what’s important and helps you communicate this progress to peers, leaders, and stakeholders, and arms you for important conversations around targets such as SLOs. Great outcomes don’t realize themselves, after all, and having the right metrics gives us the data we need to be great SREs and move performance in the right direction.
This document appears to be a slide presentation on DevOps practices and culture. Some key points discussed include:
- High-performing IT organizations are twice as likely to exceed goals in areas like profitability and customer satisfaction.
- DevOps focuses on continuous delivery, quality, lean processes, effective collaboration, and a culture of learning from failures.
- Culture can be measured and influenced by providing employees the tools and training to do their jobs successfully.
- Adopting DevOps practices may lead to improved lead times, release frequency, change fail rates, and service restoration times.
iSQI Certification Days DASA – DevOps & ISTQB Frank FrambachIevgenii Katsan
Frank Frambach presented on DevOps and testing. Some key points:
1. DevOps is driven by digital business models that require faster development and delivery of new features.
2. The DevOps Agile Skills Association (DASA) provides a competence model and certification program to develop high-performing IT professionals in DevOps.
3. Testing is an important part of DevOps and is integrated into several areas of the DASA competence model, including test specification, programming, and infrastructure engineering.
4. Bob, a tester, is shown undertaking a journey through the DASA model, first learning about DevOps and then developing his skills in related areas to transition into a DevOps
Successful writing at work copyright 2017 cengage learnssusere73ce3
This document is the table of contents for a book about successful writing at work. It outlines the contents of the book, which covers topics such as identifying audiences, establishing purpose, adapting style and tone for different audiences, characteristics of job-related writing, writing ethically, the writing process of researching, planning, drafting, revising and editing, collaborative writing, and conducting effective meetings. The table of contents provides an overview of what is covered in each chapter to help readers understand what content is included in the book.
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.
The Phoenix Project DevOps Simulation - Paul WilkinsonPink Elephant
ncorporating DevOps – The Phoenix Project Simulation
Businesses are demanding ever shorter release cycles for new applications. Traditionally ‘Operations’ is seen as a barrier with lengthy bureaucratic controls and delays in provisioning production systems. DevOps is a growing movement for shortening development and deployment and integrating Development and Operations. However, this requires a mind-set shift, new behaviours and a cultural shift in both Development and Operations. Traditionally suspicious of each other, they must now work closely together. Yet many companies are struggling to adopt and deploy DevOps and how to change the culture.
The “Phoenix Project” Simulation game is based upon The Phoenix Project. Parts Unlimited is in trouble. Newspaper reports reveal the poor financial performance of the organisation. The only way forward to not only save the company but to make it competitive and profitable is “The Phoenix Project” which represents an IT enabled business transformation, with Retail Operations as the business owner of this project. The VP of IT Operations is asked to take the lead of the IT department and ensure that “The Phoenix Project” will be a success. But the VP of IT Operations is facing a tremendous amount of work. A huge backlog of issues, features and projects. Are you up for the challenge…?
DOES15 - Elisabeth Hendrickson - Its All About FeedbackGene Kim
Elisabeth Hendrickson, VP of Engineering, Pivotal’s Big Data Suite
Fifteen years ago I was running a traditional QA department, and I had a horrifying realization: the better I got at my job, the worse I made things for the organization as a whole. This counter-intuitive realization spurred me on a journey to understand the relationship between testing and quality, and ultimately to the study of feedback loops in software development processes. Ultimately I found my way to Extreme Programming, and now work at Pivotal where we practice a particularly opinionated form of it. In this talk you’ll hear about my journey from the traditional silos with inherently long feedback latency to my current reality of increasingly tight feedback loops, and the lessons I’ve learned along the way.
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017DevOpsGroup
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017. 9 steps to DevOps Transformation
#SystemsThinking
#MakeWorkVisible
#MeasureWhatsImportant
#ActOnFeedback
#IdentifyTheGoal
#BeAgile
#DeliverContinuously
#BuildTrust
#AlignToValue
#OptimiseForFlow
The Key to High Performance - What the Data SaysNicole Forsgren
Over the past five years, the State of DevOps Report has shown that high-performing IT teams decisively outperform their peers: they deploy 200x more frequently, with 2,555 faster lead times and 1/3 change fail rate. This year, we investigate architecture, experimentation in work, other business outcomes (e.g., for gov't). Come see the latest in what it takes to make software amazing.
DevOps – the future of Agile – why, what, how? Agile Israel 2014Yuval Yeret
DevOps is the new favorite buzzword in many organizations. We will understand what it is all about, why it is necessary and what makes it so popular, how it is related to Agile, some pitfalls/myths, and most importantly some concrete steps organizations can take to become a more DevOps-oriented organization and enjoy benefits like more frequent less painful software deployments and operation and better collaboration between Dev and Ops organizations.
http://agileisrael2014.com/devops-the-future-of-agile/
Eind augustus is het Accelerate: State of DevOps Report 2018 uitgebracht. Zoals in dit rapport wordt aangegeven is IT belangrijk voor veel organisaties, en door goed te zijn op IT gebied wordt het eenvoudiger om (commerciële) bedrijfsdoelstellingen te behalen. Goed presteren als organisatie kan worden bereikt door goed te zijn (en elke dag beter te worden) DevOps gebied. Beter worden in DevOps betekent dat je elke dag moet werken aan het verbeteren van competenties die belangrijk zijn wanneer je in DevOps werkt. Maar welke competenties moet je ontwikkelen? En hoe presteer je daar vandaag op? Hoe kun je verbeteren op deze competenties zodat je morgen, volgende week en volgende maand beter wordt?
In deze sessie zal ik een overzicht geven van het DevOps Acceleration Program zoals wij deze hebben ontwikkelen. Dit programma zal een antwoord geven op voorgaande vragen en helpen te bepalen waar je welke verbetering kunt en moet doorvoeren. Belangrijk onderdeel van dit programma is het DevOps Assessment ontwikkeld door DevOps Research and Assessment (DORA), maar het is meer dan dat. Door een gezamenlijk een verbeterplan voor de komende 6 maanden op maat op te stellen en te focussen op een beperkt aantal competenties kun je daadwerkelijk verbeteren. Na 6 maanden doen we een meting om de gerealiseerde voortgang te bepalen en input te geven voor een nieuw verbeterplan.
Why #DevOps Transformation has to start with youDevOpsGroup
Why #DevOps Transformation has to start with you.
You are part of your organisation's culture, and in order to change the culture you need to change yourself, first. Learn some useful ideas of personal and DevOps Transformation from the @DevOpsGuys.
Moving forward in your DevOps journey—What's your next step after CA World?CA Technologies
A perspective from within CA Technologies on where to start and how to progress in your DevOps journey to ultimately become successful in today's application economy.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
Navvia is always looking for ways to improve how we do things and we’ve come to see DevOps as our compass on the road to continual improvement. However, DevOps means different things to different people.
To our company, it has become the rallying cry for organizational change. It is the standard that leads us on a path towards better alignment across teams, enhanced agility, higher quality and the elimination of waste.
What you will learn:
- Why Navvia embarked on DevOps
- An overview of DevOps including common misconceptions
- A case study entitled “a tale of two apps”
- How Navvia is implementing DevOps
- What we’ve learned so far
It’s an exciting journey with the destination being improved customer experience, higher rates of innovation and a faster path to business value.
AgileLIVE: Continuous Product Learning - Part 1VersionOne
How sure are you that you are “building the right thing?” How often do you validate your assumptions versus simply measuring your progress? While agile methods often help organizations build products faster, many software teams get hyper-focused on points completed over real value delivered – or, more important, learning about customers and validating product ideas. Some people obsess over “backlog grooming,” but still produce weak stories that do not provide the context needed for teams and programs to deliver valuable products. Watch the webinar recording here: http://ow.ly/C5F09
Agile 2014- Metrics driven development and devopsKarthik Gaekwad
There are many facets of devops, and we will spend our time in this presentation focusing on collecting and using metrics (business, application, system, etc.) and building a metrics driven culture in organizations.
We will define how we have seen devops progress in our organizations and how we’ve realized that different teams in our organizations can find common ground when teams (who have different roles) can work well together when they use metrics as the common language.
Karthik will talk about how we are using the principles from the Lean Startup to define our development cycles, sprints and using metrics to quantify how successful the products we are trying to come out with in R&D. Initially we started practicing devops on the dev and ops side of the house but realized this was still a black box to the business side of the house, so we pivoted to what our business actually understood, and that was metrics; today, we focus more on metrics (business and system level), and can fail or succeed fast to achieve our business goals faster than before.
Ernest will go into detail on how a large, mature SaaS organization uses metrics in conjunction with distributed agile development and DevOps to guide their development at scale. How much a product is used, how much each feature is used, and how much value each user gets out of it are key drivers for a business strategy - and it’s all information that’s emitted by a system. He'll show how large companies have invested time in collecting and using these metrics to guide their decisions and influence their culture.
5 Keys to Building a Successful DevOps CultureMandi Walls
This document provides 5 keys to building a successful DevOps culture: 1) Setting clear and measurable goals, 2) Gaining executive support, 3) Building pilot projects to test changes, 4) Providing training and prioritizing workloads, and 5) Doing outreach and evangelism. It emphasizes that culture change is difficult and requires focusing on behaviors and values over tools. Pilot projects allow practicing new processes in a controlled way before organization-wide adoption. Training, workload prioritization, and addressing dissenters are important for successful adoption of changes. Regular communication and showcasing results helps spread DevOps practices. Patience, executive engagement, and overcommunication are also advised.
DOES15 - Heather Mickman & Ross Clanton - (Re)building an Engineering Culture...Gene Kim
Heather Mickman, Senior Group Manager, Target
Ross Clanton, Director, Target
This talk will largely be a reflection on the DevOps journey at Target and the focus on (re)building an engineering culture at Target. In the DevOps community you hear a lot of talk about whether you should drive DevOps in to an organization tops down or bottoms up. Well, we did a hybrid of both. It definitely started at Target as a grass roots movement in a few small teams and started to gain broader grassroots momentum when we kicked off our first internal DevOps Days in February 2014. This enabled us to start engaging a community, finding out who had passion for this across our IT organization, and providing them a forum to connect, share, and learn about DevOps awesomeness. We fostered and grew this community by leveraging social media and guerilla marketing to start driving the conversation across our organization as well as demonstrating the success that teams were having. We then leveraged some of this early energy to engage more leader champions to start building the tops down support for DevOps. Now, having completed four DevOps Days conferences at Target, we will share more details on our approach, results, speakers, and topics.
We did much more than just hosting DevOps Days. We tapped in to that growing community to start testing and learning some different approaches and we have lots to share, both in terms of results we’ve achieved and how we’re focusing on changing culture and mindsets. From a technology perspective, we will discuss how we rapidly drove momentum on our automation toolchain across our IT organization. Our vision was to enable and empower all technologists to automate the things that they were accountable for. We pursued this vision in many ways, including Automation hackathons, establishing an embedding/coaching model for our deep SMEs to help teach, open labs, community based support, and even schemed some creative work models that we will share.
The end result of these various activities is driving full stack ownership that will ultimately enable the expansion of CI/CD across our Enterprise. This is the overarching theme and next step in our enterprise transformation. It is through this foundation we are building around culture, tooling, collaborative and flexible work models that will enable our acceleration in 2015. Moving forward, we are leveraging these learnings to shift to more of a full-stack product model for our technology delivery and management. We’re also transforming infrastructure from a model based on technology silos to an end to end infrastructure service model focused on enabling business agility.
These changes haven’t been easy. In fact, we’ve already had a lot of learnings on our journey. We will share some of those key challenges and lessons learned, specifically on talent, culture, and leadership.
How DevOps is Transforming IT, and What it Can Do for AcademiaNicole Forsgren
This document discusses how DevOps is transforming IT and what it can do for academia. DevOps is a cultural and professional movement focused on building and operating high-velocity organizations. It promotes people, technology, process, culture and experience. DevOps delivers more throughput and stability for companies. It also fosters a culture of innovation, experimentation and open communication. The document suggests academia can benefit from DevOps by embracing an open culture, sharing curriculum resources, using minimum viable products and iterating based on different team needs. DevOps principles can help improve collaboration and innovation in academic settings.
Jan de Vries - How to convince your boss that it is DevOps that he wantsAgile Lietuva
- We all know that we could implement DevOps a lot faster if we only would have commitment from our boss. We all know that there is a shiny business case for almost every DevOps implementation
- And we all know that the whole company will reap the benefits regarding speed, agility and stability once we implemented DevOps. Actually, it provides good, fast and cheap at the same time. So, what are we waiting for? What is your boss waiting for? What is C-level waiting for?
- That’s something we will do research on in this workshop. We will also share our research on this from the recent past.
- The workshop starts with a presentation about 7 practices that a company should adopt to be able to apply DevOps.
- The technique that we use is called Appreciative Inquiry. To tackle a problem, it discovers the best practices that work, the reason they work and how these combined practices can be used to avoid the problem ahead and create a strategic change. The aim is to build – or even rebuild – organizations around what works, rather than trying to fix what doesn’t.
- So we want to know what your boss is afraid of and what you have already tried to convince him that he is better off with DevOps. You will leave the workshop with the combined Appreciative Inquiry insights of all the attendees
Here are the estimated story points for the items using Planning Poker:
Spain - 13
China - 13
Luxembourg - 5
Denmark - 8
South Africa - 8 (reference point)
Belize - 3
2016 velocity santa clara state of dev ops report deck finalNicole Forsgren
The document summarizes findings from the 2016 State of DevOps Report. It shows that high-performing organizations outperform their peers in terms of throughput and lead time for changes. Employees in high-performing organizations are more likely to recommend their organization as a great place to work. These organizations spend less time fixing security issues by addressing security at every stage of development. The document also discusses how high performers spend more time on new work and less time on unplanned work and rework through the use of continuous delivery practices.
This document discusses work-in-process (WIP) limits in Kanban systems. It explains that WIP limits help improve workflow by surfacing problems. There are three types of WIP limits: personal, team execution limits to improve flow, and organizational structural limits to provide focus. Managing WIP limits can be challenging due to variability, constraints, and personal work styles, but lowering WIP limits over time helps identify issues. The document recommends several resources for learning more about Kanban and WIP limits.
Are We There Yet? Signposts On Your Journey to AwesomeNicole Forsgren
If you listen to grandiose tales of DevOps journeys, everything is awesome. But how can those of us not living in The Lego Movie transform our technology in smart and systematic ways? What is “awesome”? How do we point our organizations in that direction, and how will we know progress when we see it?
The best-performing IT organizations have the highest quality, throughput, and reliability while also showing value on the bottom line. When embarking on a journey of transformation, you want to measure your current status and subsequent progress while keeping tabs on factors that drive improvement in technology performance. Nicole Forsgren explains the importance of knowing how (and what) to measure—ensuring you catch successes and failures when they first show up, not just when they’re epic. Measuring progress lets you focus on what’s important and helps you communicate this progress to peers, leaders, and executives who decide budget. Business outcomes don’t realize themselves, after all, and “doing DevOps” doesn’t define stakeholder value any more than “being awesome” does.
The Data Behind DevOps: Becoming a High PerformerNicole Forsgren
This document discusses high performance in technology organizations and the DevOps movement. It finds that technology organizations that are high performers are twice as likely to achieve goals like productivity and profitability. High performers have code deployments 46 times more frequent and lead time from commit to deploy is 440 times faster. They also recover from downtime 96 times faster. Achieving high performance requires a focus on technology, processes, and organizational culture together. Leadership is also important but not sufficient on its own. The document provides recommendations for accelerating improvement, including starting with architecture and approval processes.
eSynergy Paul Swartout - DevOps - what is it and why is it valuable to businessPatrickCrompton
This document discusses DevOps, which aims to improve collaboration between software development (Dev) and IT operations (Ops) teams. It notes the benefits of Agile software development and continuous delivery. The document then discusses how one company moved from releasing software every 2 weeks with a team of 200 people to having a single engineer release software every 30 minutes with no downtime, by adopting DevOps practices like automation and collaboration between Dev and Ops. Key business benefits of DevOps mentioned include focusing on new features rather than releases, improved platform understanding, aligned team vision and goals, and reduced "us vs them" mentalities. Some pointers on DevOps adoption are that it requires time, tools help but aren't essential, and progress must be
Behind the Book: Gene Kim's Top Takeaways from Researching and Writing 'The D...XebiaLabs
The secure and effective management of technology is more critical than ever for business competitiveness. In the new bestseller, The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, Gene Kim and his co-authors shed light on how high-performing organizations are using DevOps principles to routinely and reliably deploy code into productions hundreds, if not thousands, of times per day.
What metrics matter from deploys per day, developer productivity and reduced feedback cycles to employee satisfaction and burnout
Striking the right balance between automation and manual steps and the role value stream mapping can play in achieving performance breakthroughs
Conway’s Law and how it's applied to change technology work processes
Integrating infosec into the daily work of Dev, Test and Ops
Common challenges encountered in automated testing and ways to overcome them
How to Pitch a Software Development Initiative and Ignite Culture ChangeRed Gate Software
You’ve got a great idea for transforming software development or IT processes in your organization, but you’re not sure how to get buy-in from key stakeholders, or how to change your company culture.
In this session, Microsoft MVP Ike Ellis will draw on his experience as a consultant and leader in software development to give you real-world tips to define, shape, and share your pitch successfully. Whether you are launching a revolutionary new initiative or expanding an existing effort to improve your software development, Ike’s tips will help you create a plan to effect change in your teams.
The document discusses common pitfalls organizations face when adopting agile processes. It notes that without discipline, agile approaches may fail due to lack of closure on work items and endless scope changes. It also highlights challenges with testing, changes in team roles and responsibilities, and difficulties adjusting working styles to more collaborative ways of working. Critical success factors include training, experience adopting agile, and support from experienced practitioners.
DevOps is driven by three factors: technical practices like continuous delivery, management practices like lean principles, and organizational culture and identity. Research shows these factors drive both IT and organizational performance. High performing DevOps teams deploy code more frequently, have faster lead times, lower failure rates, and faster mean time to recovery. This level of reliability and agility benefits organizations through increased market share, productivity, and profitability without traditional tradeoffs.
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.
Dev ops – what and why - Bristech - July 2016Paul Swartout
DevOps aims to improve collaboration between development and operations teams. It values individuals, working software, customer collaboration, and responding to change over processes and documentation. Case studies show DevOps allows for more frequent software releases with less people, improved predictability, innovation, and focus on building features rather than delivering them. Key benefits are cost reduction, removing waste, and competitive advantage from faster time to market. Cultural change takes time but starting with influential people, identifying problems, and running safe experiments can help organizations adopt DevOps practices.
This document contains Ken DeLong's work history, activities, favorite books, strengths, and views on software engineering best practices. It emphasizes hiring the best engineers, optimizing for learning, reducing waste, attention to quality, and avoiding technical and cultural debt.
Agile is a set of principles for iterative software development that values collaboration, adaptability, and delivering working software frequently. It aims to address shortcomings of traditional "waterfall" approaches which were inflexible, took too long, and did not provide value until late in the project. Key principles of Agile include satisfying customers through early delivery, welcoming changing requirements, frequent delivery of working software, daily collaboration between developers and business teams, and trusting self-organizing teams. Agile methods have benefits like increased productivity, faster time to market, and improved quality, but require constant business involvement and greater testing discipline.
Move past the jargon. See how DevOps plays into incident management and resolution.
Join guest Forrester Analysts and experts from local Colorado companies for a ½ day event focused on the latest and greatest DevOps practices for those tasked with maintaining uptime.
Are we there yet? Rev up your productivity with project management toolsMargot
This document summarizes a pre-conference workshop on project management tools held at the CARL Conference on April 4, 2014. The schedule included an introduction to project management case studies, a discussion of project management theory and best practices, a workshop to plan a project using paper and pencils, and a software showroom and test drive of various project management software options. Speakers included representatives from California Maritime Academy, William Jessup University, and Golden Gate University.
What AI Means For Your Product Strategy And What To Do About ItVMware Tanzu
The document summarizes Matthew Quinn's presentation on "What AI Means For Your Product Strategy And What To Do About It" at Denver Startup Week 2023. The presentation discusses how generative AI could impact product strategies by potentially solving problems companies have ignored or allowing competitors to create new solutions. Quinn advises product teams to evaluate their strategies and roadmaps, ensure they understand user needs, and consider how AI may change the problems being addressed. He provides examples of how AI could influence product development for apps in home organization and solar sales. Quinn concludes by urging attendees not to ignore AI's potential impacts and to have hard conversations about emerging threats and opportunities.
Make the Right Thing the Obvious Thing at Cardinal Health 2023VMware Tanzu
This document discusses the evolution of internal developer platforms and defines what they are. It provides a timeline of how technologies like infrastructure as a service, public clouds, containers and Kubernetes have shaped developer platforms. The key aspects of an internal developer platform are described as providing application-centric abstractions, service level agreements, automated processes from code to production, consolidated monitoring and feedback. The document advocates that internal platforms should make the right choices obvious and easy for developers. It also introduces Backstage as an open source solution for building internal developer portals.
Enhancing DevEx and Simplifying Operations at ScaleVMware Tanzu
Cardinal Health introduced Tanzu Application Service in 2016 and set up foundations for cloud native applications in AWS and later migrated to GCP in 2018. TAS has provided Cardinal Health with benefits like faster development of applications, zero downtime for critical applications, hosting over 5,000 application instances, quicker patching for security vulnerabilities, and savings through reduced lead times and staffing needs.
Dan Vega discussed upcoming changes and improvements in Spring including Spring Boot 3, which will have support for JDK 17, Jakarta EE 9/10, ahead-of-time compilation, improved observability with Micrometer, and Project Loom's virtual threads. Spring Boot 3.1 additions were also highlighted such as Docker Compose integration and Spring Authorization Server 1.0. Spring Boot 3.2 will focus on embracing virtual threads from Project Loom to improve scalability of web applications.
Platforms, Platform Engineering, & Platform as a ProductVMware Tanzu
This document discusses building platforms as products and reducing developer toil. It notes that platform engineering now encompasses PaaS and developer tools. A quote from Mercedes-Benz emphasizes building platforms for developers, not for the company itself. The document contrasts reactive, ticket-driven approaches with automated, self-service platforms and products. It discusses moving from considering platforms as a cost center to experts that drive business results. Finally, it provides questions to identify sources of developer toil, such as issues with workstation setup, running software locally, integration testing, committing changes, and release processes.
This document provides an overview of building cloud-ready applications in .NET. It defines what makes an application cloud-ready, discusses common issues with legacy applications, and recommends design patterns and practices to address these issues, including loose coupling, high cohesion, messaging, service discovery, API gateways, and resiliency policies. It includes code examples and links to additional resources.
Dan Vega discussed new features and capabilities in Spring Boot 3 and beyond, including support for JDK 17, Jakarta EE 9, ahead-of-time compilation, observability with Micrometer, Docker Compose integration, and initial support for Project Loom's virtual threads in Spring Boot 3.2 to improve scalability. He provided an overview of each new feature and explained how they can help Spring applications.
Spring Cloud Gateway - SpringOne Tour 2023 Charles Schwab.pdfVMware Tanzu
Spring Cloud Gateway is a gateway that provides routing, security, monitoring, and resiliency capabilities for microservices. It acts as an API gateway and sits in front of microservices, routing requests to the appropriate microservice. The gateway uses predicates and filters to route requests and modify requests and responses. It is lightweight and built on reactive principles to enable it to scale to thousands of routes.
This document appears to be from a VMware Tanzu Developer Connect presentation. It discusses Tanzu Application Platform (TAP), which provides a developer experience on Kubernetes across multiple clouds. TAP aims to unlock developer productivity, build rapid paths to production, and coordinate the work of development, security and operations teams. It offers features like pre-configured templates, integrated developer tools, centralized visibility and workload status, role-based access control, automated pipelines and built-in security. The presentation provides examples of how these capabilities improve experiences for developers, operations teams and security teams.
The document provides information about a Tanzu Developer Connect Workshop on Tanzu Application Platform. The agenda includes welcome and introductions on Tanzu Application Platform, followed by interactive hands-on workshops on the developer experience and operator experience. It will conclude with a quiz, prizes and giveaways. The document discusses challenges with developing on Kubernetes and how Tanzu Application Platform aims to improve the developer experience with features like pre-configured templates, developer tools integration, rapid iteration and centralized management.
The Tanzu Developer Connect is a hands-on workshop that dives deep into TAP. Attendees receive a hands on experience. This is a great program to leverage accounts with current TAP opportunities.
The Tanzu Developer Connect is a hands-on workshop that dives deep into TAP. Attendees receive a hands on experience. This is a great program to leverage accounts with current TAP opportunities.
Simplify and Scale Enterprise Apps in the Cloud | Dallas 2023VMware Tanzu
This document discusses simplifying and scaling enterprise Spring applications in the cloud. It provides an overview of Azure Spring Apps, which is a fully managed platform for running Spring applications on Azure. Azure Spring Apps handles infrastructure management and application lifecycle management, allowing developers to focus on code. It is jointly built, operated, and supported by Microsoft and VMware. The document demonstrates how to create an Azure Spring Apps service, create an application, and deploy code to the application using three simple commands. It also discusses features of Azure Spring Apps Enterprise, which includes additional capabilities from VMware Tanzu components.
SpringOne Tour: Deliver 15-Factor Applications on Kubernetes with Spring BootVMware Tanzu
The document discusses 15 factors for building cloud native applications with Kubernetes based on the 12 factor app methodology. It covers factors such as treating code as immutable, externalizing configuration, building stateless and disposable processes, implementing authentication and authorization securely, and monitoring applications like space probes. The presentation aims to provide an overview of the 15 factors and demonstrate how to build cloud native applications using Kubernetes based on these principles.
SpringOne Tour: The Influential Software EngineerVMware Tanzu
The document discusses the importance of culture in software projects and how to influence culture. It notes that software projects involve people and personalities, not just technology. It emphasizes that culture informs everything a company does and is very difficult to change. It provides advice on being aware of your company's culture, finding ways to inculcate good cultural values like writing high-quality code, and approaches for influencing decision makers to prioritize culture.
SpringOne Tour: Domain-Driven Design: Theory vs PracticeVMware Tanzu
This document discusses domain-driven design, clean architecture, bounded contexts, and various modeling concepts. It provides examples of an e-scooter reservation system to illustrate domain modeling techniques. Key topics covered include identifying aggregates, bounded contexts, ensuring single sources of truth, avoiding anemic domain models, and focusing on observable domain behaviors rather than implementation details.
Lee Barnes - Path to Becoming an Effective Test Automation Engineer.pdfleebarnesutopia
So… you want to become a Test Automation Engineer (or hire and develop one)? While there’s quite a bit of information available about important technical and tool skills to master, there’s not enough discussion around the path to becoming an effective Test Automation Engineer that knows how to add VALUE. In my experience this had led to a proliferation of engineers who are proficient with tools and building frameworks but have skill and knowledge gaps, especially in software testing, that reduce the value they deliver with test automation.
In this talk, Lee will share his lessons learned from over 30 years of working with, and mentoring, hundreds of Test Automation Engineers. Whether you’re looking to get started in test automation or just want to improve your trade, this talk will give you a solid foundation and roadmap for ensuring your test automation efforts continuously add value. This talk is equally valuable for both aspiring Test Automation Engineers and those managing them! All attendees will take away a set of key foundational knowledge and a high-level learning path for leveling up test automation skills and ensuring they add value to their organizations.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
inQuba Webinar Mastering Customer Journey Management with Dr Graham HillLizaNolte
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...DanBrown980551
This LF Energy webinar took place June 20, 2024. It featured:
-Alex Thornton, LF Energy
-Hallie Cramer, Google
-Daniel Roesler, UtilityAPI
-Henry Richardson, WattTime
In response to the urgency and scale required to effectively address climate change, open source solutions offer significant potential for driving innovation and progress. Currently, there is a growing demand for standardization and interoperability in energy data and modeling. Open source standards and specifications within the energy sector can also alleviate challenges associated with data fragmentation, transparency, and accessibility. At the same time, it is crucial to consider privacy and security concerns throughout the development of open source platforms.
This webinar will delve into the motivations behind establishing LF Energy’s Carbon Data Specification Consortium. It will provide an overview of the draft specifications and the ongoing progress made by the respective working groups.
Three primary specifications will be discussed:
-Discovery and client registration, emphasizing transparent processes and secure and private access
-Customer data, centering around customer tariffs, bills, energy usage, and full consumption disclosure
-Power systems data, focusing on grid data, inclusive of transmission and distribution networks, generation, intergrid power flows, and market settlement data
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
ScyllaDB is making a major architecture shift. We’re moving from vNode replication to tablets – fragments of tables that are distributed independently, enabling dynamic data distribution and extreme elasticity. In this keynote, ScyllaDB co-founder and CTO Avi Kivity explains the reason for this shift, provides a look at the implementation and roadmap, and shares how this shift benefits ScyllaDB users.
Getting the Most Out of ScyllaDB Monitoring: ShareChat's TipsScyllaDB
ScyllaDB monitoring provides a lot of useful information. But sometimes it’s not easy to find the root of the problem if something is wrong or even estimate the remaining capacity by the load on the cluster. This talk shares our team's practical tips on: 1) How to find the root of the problem by metrics if ScyllaDB is slow 2) How to interpret the load and plan capacity for the future 3) Compaction strategies and how to choose the right one 4) Important metrics which aren’t available in the default monitoring setup.
"What does it really mean for your system to be available, or how to define w...Fwdays
We will talk about system monitoring from a few different angles. We will start by covering the basics, then discuss SLOs, how to define them, and why understanding the business well is crucial for success in this exercise.
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project.
📕 Detailed agenda:
Variables and Datatypes
Workflow Layouts
Arguments
Control Flows and Loops
Conditional Statements
💻 Extra training through UiPath Academy:
Variables, Constants, and Arguments in Studio
Control Flow in Studio
MySQL InnoDB Storage Engine: Deep Dive - MydbopsMydbops
This presentation, titled "MySQL - InnoDB" and delivered by Mayank Prasad at the Mydbops Open Source Database Meetup 16 on June 8th, 2024, covers dynamic configuration of REDO logs and instant ADD/DROP columns in InnoDB.
This presentation dives deep into the world of InnoDB, exploring two ground-breaking features introduced in MySQL 8.0:
• Dynamic Configuration of REDO Logs: Enhance your database's performance and flexibility with on-the-fly adjustments to REDO log capacity. Unleash the power of the snake metaphor to visualize how InnoDB manages REDO log files.
• Instant ADD/DROP Columns: Say goodbye to costly table rebuilds! This presentation unveils how InnoDB now enables seamless addition and removal of columns without compromising data integrity or incurring downtime.
Key Learnings:
• Grasp the concept of REDO logs and their significance in InnoDB's transaction management.
• Discover the advantages of dynamic REDO log configuration and how to leverage it for optimal performance.
• Understand the inner workings of instant ADD/DROP columns and their impact on database operations.
• Gain valuable insights into the row versioning mechanism that empowers instant column modifications.
3. DevOps is the original
hipster for well-being
and sustainable work
4. @nicolefv
Here’s what we’ll talk about today
● How DevOps helps us
● Productivity is personal
● Tiny wins
● The future of productivity and well-being
5. @nicolefv
When we stir up tech, process, and culture
improvements, we can develop and deliver
our tech in better ways.
7. @nicolefv
Elite performers do better -- LOTS better
more frequent code
deployments
973x 6570x
Comparing to low performers, DORA’s latest research finds that elite performers have…
faster lead time from
commit to deploy
2021 Accelerate State of DevOps Report (DORA)
lower change fail rate
(changes are ⅓ less likely to
fail)
3x 6570x
faster time to recover
from incidents
8. @nicolefv
These improvements help us reduce friction,
stop repeating mindless tasks, decrease our
cognitive load, improve security, [all the things]…
… so we can get back to doing the fun cool stuff
9. @nicolefv
DevOps improves developer well-being
as likely to experience
burnout during the pandemic
1/2
A positive team culture mitigates burnout
during challenging circumstances. Teams
with an inclusive, generative culture
2021 Accelerate State of DevOps Report (DORA)
Improvements in automation
and continuous delivery
reduce deployment pain and
burnout
2018 Accelerate State of DevOps Report (DORA)
Improving culture,
process, and
automation is key
10. @nicolefv
Automation makes things better
faster time to merge
pull requests
18% 34%
Once an open source repository starts using
Actions with their pull requests, we see…
more pull requests
merged
2020 State of the Octoverse Report (GitHub)
11. @nicolefv
Tiny wins
Improving productivity doesn’t have
to come from large projects.
Sometimes the most rewarding
things we do are small things with big
impact.
Joel talks about “tiny” projects with
big impact
https://joelcalifa.com/blog/tiny-wins/
14. Charles Dickens’ “A Tale of Two Cities”
begins, “It was the best of times, it was
the worst of times.” Adapting Dickens’ line
to leading an engineering team during the
global pandemic, I’d say “We’re doing very
well, we’re barely hanging in there.”
—
Shane O’Flynn
15. @nicolefv
The TL;DR: on developer patterns globally during 2020
● Overall, developer patterns matched prior years (plus growth) year over year
● Working days (measured as push window) increased by 25-50 minutes
● Work volume (measured as push volume) didn’t drop -- or increased
● Pull request merge times got faster -- up to seven hours faster in open source
and up to 4.5 hours faster in work contexts -- a sign of increased
collaboration
But these patterns don’t reveal the whole story (the what or the why), and likely
aren’t sustainable.
2020 State of the Octoverse Report (GitHub)
16. @nicolefv
What developers say: Productivity
● For most, productivity had not changed or had improved (62% - 68%)
● However, many less productive (32% - 38%)
○ For those that were less productive, that lack of productivity decreased
over time (38% to 30%), suggesting they found ways to accommodate
Productivity is personal.
People are affected differently, based on work styles, and the challenges and
benefits they face
https://arxiv.org/pdf/2008.11147.pd
f
17. @nicolefv
What developers say: The good about WFH
● Less time on commute
● Spending less money
● Flexible work hours
● Closer to family
● More comfortable clothing
● Reduced health risks
● Better focus time
● Less distractions or interruptions
● More time to complete work
● More breaks
● Better work life balance
● Better work environment
● More efficient meetings
● More control over work
● More physical activity
https://arxiv.org/pdf/2008.11147.pd
f
18. @nicolefv
What developers say: The good about WFH
● Less time on commute
● Spending less money
● Flexible work hours
● Closer to family
● More comfortable clothing
● Reduced health risks
● Better focus time
● Less distractions or interruptions
● More time to complete work
● More breaks
● Better work life balance
● Better work environment
● More efficient meetings
● More control over work
● More physical activity
● Less time on commute and More
time to complete work
Significant impact on productivity
Strongest impact on productivity
https://arxiv.org/pdf/2008.11147.pd
19. @nicolefv
What developers say: The bad about WFH
https://arxiv.org/pdf/2008.11147.pd
f
● Missing social interactions
● Lack of work-life boundary
● Poor ergonomics
● Less awareness of colleagues work
● Less physical activity
● Difficult to communicate with
colleagues
● Insufficient hardware
● Connectivity problems
● Poor work life balance
● Too many meetings
● More distractions or interruptions
● Lack of a routine
● Fewer breaks
● Friction with collaboration tools
● Lack of motivation
● Blocked waiting on others
● Poor home work environment
● Lack of dining options
● Lack of childcare
● Less time to complete work
20. @nicolefv
What developers say: The bad about WFH
Significant impact on productivity
Strongest impact on productivity
https://arxiv.org/pdf/2008.11147.pd
● Missing social interactions
● Lack of work-life boundary
● Poor ergonomics
● Less awareness of colleagues work
● Less physical activity
● Difficult to communicate with
colleagues
● Insufficient hardware
● Connectivity problems
● Poor work life balance
● Too many meetings
● More distractions or interruptions
● Lack of a routine
● Fewer breaks
● Friction with collaboration tools
● Lack of motivation
● Blocked waiting on others
● Poor home work environment
● Lack of dining options
● Lack of childcare
● Less time to complete work
● Lack of childcare and Less time to
complete work
21.
22. @nicolefv
WFH before COVID-19
The Good The Bad The Worrisome
● Improved
productivity
● Better punctuality
● Less attrition
● Fewer promotions
● Workplace stress
can compound for
those with young
children
● Fewer breaks
● Longer workdays
See Appendix
Key success factors:
● suitable working conditions at home
● efficient communication with coworkers
● supervisor trust and support
23. @nicolefv
Daily gratitudes
Butler & Jaffe
47%
daily gratitude reflection
positively impacted well-
being
Flexibility &
time with family
are bright spots
Resources for
mental health
are important
24. @nicolefv
Daily challenges
Butler & Jaffe
Coping with
WFH is elusive
for some
41% report no
improvement, 61% report
improvements
Feeling
overworked, and
lacking
motivation &
focus
are continued themes
Physical &
mental health
are a struggle,
and getting worse
25. @nicolefv
Each of us can do small things to make our
days better in measurable ways
27. @nicolefv
Good Day Project
We did a study to help developers get quick and easy signals and patterns to
help them have better days, more consistently. (“What makes a good day, and
how can I have one more often?”)
The deets:
● Based on holistic concept of productivity using the SPACE framework
● Focus on individual: measures for us, not for managers
○ To help us measure our energy, not our time
● Goal is quick and easy measures with actionable signal
https://github.blog/2021-05-25-octoverse-spotlight-good-day-
project/
28. @nicolefv
What is the SPACE framework?
https://queue.acm.org/detail.cfm?id=3454124
Dimension Definition
S: Satisfaction and Well-being How fulfilled, happy, and healthy one is
P: Performance An outcome of a process
A: Activity The count of actions or outputs
C: Communication and Collaboration How people talk and work together
E: Efficiency and Flow Doing work with minimal delays or interruptions
A holistic way to measure productivity
29. @nicolefv
Good Day Project
To capture SPACE quickly, we asked questions like:
● How was your work day?
● I worked with other people
● My work was interrupted
● How many meetings did you have today?
● Today, I felt most productive… (and least productive)
[the full instrument is available online!]
https://github.blog/2021-05-25-octoverse-spotlight-good-day-
project/
30. @nicolefv
Good Day Project
We did a study to help developers get quick and easy signals and patterns to
help them have better days, more consistently. (“What makes a good day, and
how can I have one more often?”)
The deets:
● Based on holistic concept of productivity using the SPACE framework
● Focus on individual: measures for us, not for managers
○ To help us measure our energy, not our time
● Goal is quick and easy measures with actionable signal
https://github.blog/2021-05-25-octoverse-spotlight-good-day-
project/
31. @nicolefv
Finding flow is key, and interruptions are a drag
chance of having a
good day
82% 7%
Minimal or no interruptions
give developers:
chance of having a
good day
2020 State of the Octoverse Report (GitHub)
Interruptions
throughout the day:
32. @nicolefv
Meetings are both awesome and terrible
-60%
Collaboration is a key
enabler of doing work,
connecting with people, and
can even help us do more
development.
chance of making
progress on goals
2020 State of the Octoverse Report (GitHub)
Too many meetings can be a
blocker. Going from 2 to 3
meetings per day
33. @nicolefv
Two minute daily reflection can help improve our days
● Developers liked the quick check-in as a way to reflect
● As a nice bonus: a wrap-up at the end of the day
● This echoes the Daily Gratitude study
For more info, including the survey questions we used and example reports, check
out https://github.blog/2021-05-25-octoverse-spotlight-good-day-project/
35. @nicolefv
Future of development and well-being
There are some important questions to ask
● How do new tools help us be more productive?
○ Let’s further reduce the repeatable things and focus on new work
● What is “productivity” when traditional (easy) measures no longer apply?
● How can we think about reducing harm?
● How can we expand our conceptualization of “developer”
○ Low-code and no-code tools create new opportunities and
challenges
● How can we rethink well-being -- for work and boundaries?
36. @nicolefv
TL;DR
● How DevOps helps us
● Productivity is personal
● Tiny wins
● The future of productivity and well-being
Stay tuned!
Octoverse Report is coming
soon, with even more data
(omg!)
39. @nicolefv
Citations and papers
● On workplace productivity: https://future.a16z.com/on-workplace-productivity/
● Good Day Project: https://github.blog/2021-05-25-octoverse-spotlight-good-day-project/
● Tiny Wins: https://joelcalifa.com/blog/tiny-wins/
● Ford et al: A Tale of Two Cities: Software Developers Working from Home During the COVID-19 Pandemic:
https://arxiv.org/pdf/2008.11147.pdf
● Butler and Jaffe: Challenges and Gratitude: A Diary Study of Software Engineers Working From Home During Covid-19
Pandemic https://www.microsoft.com/en-us/research/publication/challenges-and-gratitude-a-diary-study-of-software-
engineers-working-from-home-during-covid-19-pandemic/
● 2020 GitHub Octoverse https://future.a16z.com/on-workplace-productivity/
● 2021 Accelerate State of DevOps Report (DORA): https://cloud.google.com/devops/state-of-devops
● 2018 Accelerate State of DevOps Report (DORA): https://services.google.com/fh/files/misc/state-of-devops-2018.pdf
● SPACE of developer productivity: https://queue.acm.org/detail.cfm?id=3454124