15 years of DevOpsDays
Registration and Breakfast
Welcome to DevOpsDays 15 years Anniversary Edition
Wiring for Fast Flow
Based on a paper I co-wrote with Cisco's John Rauser, this talk introduces the key mechanisms and principles that enable the internet's extreme flow at scale and our best collaboration. This talk will introduce three critical missing pieces in almost every company's attempt to enable fast flow, and how those pieces can be easily missed in a performance improvement journey.
Based on his experience helping customers with Team Topologies during the last 5 years, Manuel will rant about... sorry, share what are the most common blockers to fast flow in tech organizations. From the classics originally illustrated in the Team Topologies book to the "new kids on the block", some of which come from misinterpretations of ideas in the book! This rant talk also contains personal reflections on what we would have done differently if we had to rewrite the book today.
DORA will publish its tenth report on software delivery performance this year, marking more than a decade of research into what it takes to build and scale high-performing technology teams.
Let's take a moment to reflect on how far we've come, celebrate the successes of today's DORA community, and make some predictions about the future.
This session will explore some of DORA's key findings including:
- Speed and stability are not tradeoffs
- A healthy culture is essential
- Improve by alleviating your team's constraints
- Software delivery performance is good for organizational outcomes and practitioner well-being
We will also look at the future of DORA and whether it inform our adoption of new technologies like AI and practices like Platform Engineering.
Join us for success stories, cautionary tales, and advice about how to leverage DORA to help your team get better at getting better.
Coffee Break
We've been thinking about building and optimizing cross functional product teams (Engineering, Product, and UX) for decades. Our guiding philosophical principles have their roots in factory and process optimization, and those roots influence everything we do when trying to build and organize high performing teams. In this talk we'll break down those roots, and show how rather than framing product teams as a factory, we can more easily build high performing organizations if we treat them like professional sports teams. You'll leave with practical tips on how to think differently about your people, and how to optimize them as a team.
One core truth of software that has held true over paradigm shifts is that if you deploy software, you’ll sooner or later have to deploy a fix to that software. DevOps, Cloud Native, & containers have all led the way in forcing us to rethink how we accomplish deployments with efficiency & scale. But these paradigms have also made the patching problem much worse. The explosion of FOSS, shifting choice left to development teams, decoupling applications into microservices, & the rise of the Cloud have all made patching that much more difficult in the modern day.
During this talk, we will explore the complications of patching a modern application platform, and will explore how teams can more effectively collaborate on the CVE mitigation process. We will also discuss how teams can go beyond patching for CVE mitigation by leveraging defense in depth practices. Attendees will leave with a better understanding of the challenges of modern architectures & practices, how to build effective CVE mitigation strategies, and how to collaborate with security teams better on the topic.
"What are we using for pipelines? Which infrastructure do we support? Is service mesh enabled?”. These types of questions - revolving on tech choices and implementation - currently occupy most of the conversations around platform engineering.
According to most evidence, though, these are not the only things that make a cloud-native platform successful: cultural change, communication and collaboration, reorganized processes, shared vision and roadmap - among others - play a key role in determining the success of platform transformation. If we don’t address change comprehensively, the risk is that in a few years we’ll discover that platforms are not bringing the results we expected.
In this talk we’ll see some key aspects that are often overlooked in implementing a platform and how it’s possible to address them along the way. We’ll also share some of the pitfalls and lessons we learned in our experience, supporting large and small organizations in building their cloud-native platforms.
Lunch
In a continuously changing IT world, not being able to adapt is the difference between yesterday's and tomorrow’s projects. Everybody wants the benefits of changes but nobody wants to endorse its associated risk. I’ll share why we created Updatecli, an open-source declarative dependency manager. How automation helps us to anticipate, and fix early, our day-to-day challenges, and where the traps lie.
Developer Experience (DevEx) encompasses all aspects of a developer's interaction with the technology from the moment they start writing code until the changes get shipped.
Why you never should upgrade, instead create new infrastructure. The presentation are created in co-operation with my daughters
Opening of the Open Spaces
Open Space https://devopsdays.org/open-space-format/
https://devopsdays.org/open-space-format/
https://devopsdays.org/open-space-format/
Coffee Break
https://devopsdays.org/open-space-format/
Open Space Slot 5 day 1
In todays tech environment, both people and organizations must continuously learn and adapt to be successful. Yet study after study shows that learning is difficult for most organizations.
In this talk, we will discuss whats preventing smart people from learning new things, the development of personal and organizational growth mindset, and how leading by example proves to be extremely important for creating a learning organization.
Dr. Edwards Deming and his System of Profound Knowledge - past, present, and future musings.
Closing Session Day 1
Walking Dinner
Registration and Breakfast
Welcome to Day 2
The value of the new genAI capabilities shine when they really become part of our daily workflows.
In this talk I’ll take you through the engineering workflow, from ideas to production and how genAI technology is making an impact there. From the simple asking questions to GPTs all the way to agents acting on our behalf. No role will go untouched , from product owner, over developer all the way to support and operations. Using real world examples showing the collaborative power this new technology has to enhance us to do a better job.
As this is so much work in progress, I will bring realism on where we are in practice and what is coming up next. This should give you a better grasp of its power beyond the first experiences you may have had and understand the rough edges of the current reality.
Get ready for a high paced and humorous overview to learn more on the exciting technology wave we’re currently experiencing. Buckle up!
This talk delves into the incorporation of sustainability within DevOps, aiming to diminish the environmental footprint of software systems. We explore various strategies to achieve sustainability in software development and operations, including optimizing server use, enhancing code efficiency, selecting green infrastructure, and improving resource management. The session emphasizes how sustainable practices in DevOps not only contribute to environmental goals but also enhance operational efficiency and reduce overall costs.
SAP has ~30.000 people working in it's development organization, with >1000 products on their price list using various technology stacks. How to increase developer productivity at this scale?
Backed by inhouse user research and industry trends they decided to lower their teams cognitive load by introducing an internal developer platform called 'Hyperspace'.
Dirk will talk about the obstacles of creating 'Hyperspace' with an "Platform as a Product" approach to an organization that is highly fragmented.
Concepts of Paved Roads (a.k.a. Golden Paths) helped them to provide guidance to teams with the aim to reduce team cognitive load while decreasing support load on central teams.
Join Dirks talk for lessons learned, impacts which they can already see and an outlook on what they envision in the Hyperspace.
Coffee Break
Based on my practical experience, I will be talking about:
- What kind of culture keeps a team an ever-changing DevOps team?
- How can leadership enable a team to be a continuously changing DevOps team?
Medical care in Japan is still going through the journey of digitization, therefore it is still inconvenient for both the recipients and providers of care. Kakehashi, a Japanese medical startup, is taking on the challenge of developing a variety of products to make the Japanese medical experience more flexible.
My team is dedicated to launching new businesses. After about six months of PoC, we aim to work with an existing product for pharmacies and pharmacists, which has a high market share in Japan, and to spread the results of PoC to existing customers.
Our team's relationship with DevOps has transitioned over the past year throughout our ways of working.
MVP Phase: Prioritize shortening lead time to release. However, laid the foundation for trunk-based development with a future perspective.
PoC Phase: A high-speed hypothesis testing cycle was conducted with actual customers using the system. The DevOps element of the project became more clear.
Collaboration Phase:
Develop while adopting a release flow that can withstand the quality expected by the enterprise. Develop while collaborating with team members in charge of existing products through pair programming and other means.
Culture is hard. People are messy. Organizational culture may be in direct opposition to the values and practices of a local community or country. Research and recommendations are everywhere, and if the culture of your organization isn't what you need it to be, it might not be completely your fault.
DevOps spread has leveled out, it's no longer a fast growing mindset and set of accompanying tools. Some surveys show that 70% of people are still not automating their builds, let along production deployment. DevOps companies are facing growth challenges. It can feel like we're yet again re-discovering the early days of DevOps instead of evolving it to the next stage. Is this bad? Is it good? Is it expected? This talk is an analysis of slowing DevOps growth and what it means for you.
Based on my master's dissertation, in this topic I will cover an introduction to mathematical optimization and Integer Programming and how these can help reduce pod scheduling costs for us in Kubernetes, building an algorithm that could be a Kube-Scheduler plugin and seek an optimal pod-to-node allocation scenario, always aiming for the cheapest node or a rearrangement of pods to reduce scaled nodes, thus reducing costs for the operated infrastructure.
Jim Collins’ Five Stages of Decline shows how many great companies overstep themselves and suddenly find themselves falling, more and more rapidly. See, most startups only care about early growth—just like tech debt, we think we can always come back to sustainability after we’ve made it. Open source community is a great way to kickstart that initial success and growth. It’s practically free and your users are throwing contributions at you left and right....
We hit that peak much sooner than we anticipated and without having built a sustainable community foundation we shoot right off the cliff and go screaming down the decline on the other side. As we fall, we grasp at whatever straws we can, chasing new technologies or rapidly throwing new products at the wall hoping they’ll stick. Nothing does, of course. The accountants show up to bleed you dry, and then the lawyers finish you off.
And you? You’ve probably still got a few of those rad swag t-shirts from the heyday, right?
This doesn’t have to be the only story. David is here to tell you how to recognize when you've reached maturity so you know how to ease into the long tail of maintenance, engaging and working with your community to build a long-term sustainable business, solving the problems your customers bring to you. It’s hard work and it takes every-single-day consistency. But it does get easier with practice.
Drawing a comparison between my past and current professions. Looking at stages of baking in preparing, mixing, baking, and feedback while comparing to DevOps stages of planning, building, deploying, and monitoring.
Open Space Opening
Lunch
https://devopsdays.org/open-space-format/
https://devopsdays.org/open-space-format/
Coffee Break
https://devopsdays.org/open-space-format/
https://devopsdays.org/open-space-format/
https://devopsdays.org/open-space-format/
Closing session of 15 years of DevOpsDays