On this page you will only see the English-language presentations of the conference. You can find all conference sessions, including the German speaking ones, here.
The times given in the conference program of OOP 2024 correspond to Central European Time (CET).
By clicking on "VORTRAG MERKEN" within the lecture descriptions you can arrange your own schedule. You can view your schedule at any time using the icon in the upper right corner.
Thema: Project Management
- Architecture – for Humans?
- C++ and possible Alternatives
- Domain-Driven Design expands our horizons
- Embedding AI into your Products: Practical Applications of Foundation Models
- Full Day Tutorial
- Half Day Tutorial
- Shaping the future: Overcoming Boundaries with New Ideas in Product Ownership, UX & Requirement Engineering
- Social Integration
- Software Architecture – Systematically Handling Quality Attributes
- Special Event
- Testing & Quality
- Thinking DevOps further
- Trends & Techniques
Are you ready to take your agile development practices to the next level? Join us for a hands-on and interactive workshop where we will explore the interdependencies of eXtreme Programming (XP) practices and how they can help you achieve success in your agile journey. Using the powerful technique of Wardley Mapping, we will uncover the gaps in your agile adoption and gain a new understanding of your actual agile capabilities.
Laptop (with browser access) is required.
Target Audience: Architects, Developers, Leaders, Coaches, Facilitators
Prerequisites: Basic understanding of eXtreme Programming
Wardley Mapping is a visual mapping technique used to understand the evolution of a particular market or product and the relative value that each component provides. In the context of agile development, Wardley Mapping can help you identify the components of your agile process that are providing the most value and where to focus your efforts next. During the workshop, we will guide you through the process of creating your own Wardley Map, analyzing your current agile development practices, and identifying areas for improvement. You will have the opportunity to work with a small group of peers and receive personalized feedback and guidance from our experienced facilitators.
Whether you are using XP practices, Ben Linders' agile coaching cards, or simply following the agile values and principles, this workshop is designed to provide you with the tools and insights you need to achieve agile mastery. Don't miss this opportunity to take your agile development journey to the next level. Sign up for our workshop and discover the power of Wardley Mapping and XP practices. Please note: Participants should bring a laptop* and be familiar with the basics of agile development practices.
* We are going to use Miro for the mapping.
Andreas Schliep is a renowned Scrum Coach and Trainer and a founding member of DasScrumTeam. With a rich experience spanning over two decades in the software industry, Andreas has worked as a software developer, project manager, team leader, and unit manager, before discovering his passion for Scrum in 2003-2004 through his colleagues at WEB.DE.
Since then, Andreas has become a leading figure in the Scrum community, and his expertise in the field is widely recognized. He has served as a Scrum Master, Product Owner, team member, Coach, and Trainer, gaining invaluable insights into the nuances of Scrum implementation. Andreas has been a self-employed Coach and Trainer since 2008, with his main focus being on agile leadership and the sustainable transformation of organizations.
As a certified Scrum Alliance Trainer, Andreas has been instrumental in introducing Scrum to numerous organizations across the globe. His deep understanding of Scrum and his passion for leadership has made him a sought-after speaker at conferences and seminars worldwide. Andreas' special interests lie in responsibility and leadership, and he firmly believes that agile principles are key to unlocking an organization's true potential.
Andreas is a graduate of the University of Applied Sciences in Bremerhaven, where he honed his skills in software engineering. He has received numerous accolades for his work, and his contributions to the Scrum community have been widely acknowledged. Andreas is committed to sharing his knowledge and experience with others and helping organizations achieve their full potential through agile principles.
Peter Beck's mission is to create companies delivering value to their customers and their employees. That was his motivation to found DasScrumTeam, and that is still his motivation today to lead the company in the role as Product Owner. As a German graduate engineer, he believed that everything could be solved with a smart, technical solution. That changed in 2004, when his passion for Scrum began. Since then, he knows: There are no technical problems, only human ones. Since 2009, he has been helping people solve these problems by teaching them Scrum and other agile practices as a Certified Scrum Trainer.
In this workshop, participants will roleplay fictive situations in groups of +/- 7 people.
- divided in groups
- everyone gets a random set of reaction cards (same as number of people in the group
- one person (disturber of the peace) selects a situation card
- the disturber acts out the situation
- everyone in the group selects a way to react and plays that.
- everyone gives their reaction card back
- disturber gives feedback about what the reactions do to them
- repeat until everyone has played a disturbing situation
- Debrief at the end
The game was invited by Yattom
It exists in Japanese, Korean, English, Dutch, French. (if people want to help we can create a German version for the conference)
Target Audience: Team Members
Yves Hanoulle (he/him) discovered extreme programming in 1999. Over the years, he realised that creating working software takes collaborating over writing code. Just like coaching is asking questions over sharing ideas.
As an independent consultant since 1998, Yves works with people around the globe.
Yves calls himself a FireStarter, an agile Instigator, or a Creative Collaboration Agent. Agile friends joke about the Six degrees of agile with Yves at the centre.
The Product Owner role in Scrum is vital, but lacks comprehensive guidance. This talk presents the SMIQ Method (Single Most Important Question), derived from the "48 hour book method," empowering Product Owners and Managers to translate customer needs into software requirements. It simplifies complex techniques into user-friendly steps for effective requirements engineering. The speaker's success in using this method for writing books, organizing conferences, and developing software highlights its simplicity and effectiveness.
Target Audience: Product Owners, Product Managers, Requirements Engineers, UX, Project Managers
Prerequisites: Scrum, Product Owner role in Scrum, beginner level knowledge of User-centered design
Product Owner is one of the most critical roles in the Scrum Framework. However, beyond “the backlog” and “prioritization”, there’s very little guidance as to what that role entails. This talk presents a method (The SMIQ or Single Most Important Question Method, discussed in the “48 hour book method”) that guides Product Owners, and Product Managers in their discovery work, and helps them translate customer needs into Software requirements. It’s a simple method, but it offers the opportunity for in-depth understanding and effective requirements management. The method achieves it’s simple format by codifying some complex techniques into a simple set of steps that anyone can use, and this speaker has used to write books, create conferences, and develop software.
- The challenge of understanding the customer, and what is required to succeed
- How to translate real life into software requirements, reliably, and quickly
- Concrete practices and techniques to implement the method suggested
- Practical application of the SMIQ method in the conference room, with the participants
- How to bring the SMIQ method to our work as Product Owners and Product Managers
Vasco Duarte, a leading figure in the agile community, co-founded Agile Finland and hosts the popular Scrum Master Toolbox Podcast with over 10 million downloads. His book "NoEstimates" provides a unique approach to Agile, enhancing software development's sustainability and profitability. As a keynote speaker, he shares his expertise, empowering organizations to improve effectiveness, adaptability, and responsiveness. Vasco's contributions have reshaped the landscape of software development.
Stoic practitioners know they cannot control circumstances, other people or rather... they know they cannot control anything outside of the realm of their own choices. So as a Stoic Product Leader you should stop focussing on outcome (!). Outcome is always outside of your control. However the CHOICES you need to make the product vision and goals ARE within your power, within your control. So the best thing you can do as a (product) leader is improving the quality of your decisions and teach your teams how to do that too.
Target Audience: Project/Portfolio Leaders, Product Owners, Product Managers, Leadership, Decision Makers
Stoic practitioners know they cannot control circumstances, other people, behaviour of other people in their teams, or simply: they know they cannot control anything outside of their own mind, the realm of their own choices.
So as a Stoic Product Leader you should stop focussing on outcome. Outcome is outside of your control as a leader. Your own choices are within your control. The choices you need to make in the long run (product vision) and the ones you need to make that are right in front of you (iteration goal).
So the best thing you can do as a (product) leader is improving the quality of your decisions and teach your teams how to improve their ability to make better choices.
(Sustainable) product leadership is far more like poker (with uncontrollable circumstances and emerging events that influence possible outcomes) than like chess (if you think long and hard you could predict what is the next best move).
* Learning goals
- know how to move from outcome focus to focus on improving decision quality
- know how to implement habits that will improve your decision making as a product leader
This session will help you make better, more sustainable product choices
Maryse Meinen is a Product Person and a Stoic practitioner, currently working in IT infra. Passionate about sustainability and working on greening IT (software AND hardware). Also working on social sustainability in several ways.
Many of us have worked on death-march projects or rewrote code "just because CTO said so".
How many have seen such endeavours succeed - without burning people, motivation, reputation & lots of money?
The quest for Sustainable Pace is as old as XP. Maybe even older.
It's neither an individual task nor is it only a team’s responsibility. It’s an interaction of both - and beyond: it all is about (organisational) systems!
If we cannot architect livable organisational systems, how are we supposed to architect decent socio-technical systems?
Target Audience: Developers, Architects, System Engineers, Managers of all flavours, Curious human beings
Prerequisites: Curiosity and some work/project experience is beneficial
In this session you will get some of my answers on these questions.
Also you will:
- learn what sustainable pace is about (and what it's NOT)
- connect to all-too-common pitfalls that can “unbalance” a system (i.e. team, a whole organisation, and also yourself)
- get simple yet powerful self-care practises for yourself and for your team(s)
- learn necessary psychological background (e.g. stress & coping)
Bring genuine curiosity with you - the number one “tool” to expand horizons!
Cosima Laube is an independent leadership coach & socio-technical consultant with broad domain experience (e.g. automotive, finance, healthcare, public sector).
Building on a strong foundation as developer & people lead in IT, she enhanced her portfolio with solid coaching skills (ICF-PCC) and a BSc. in Psychology.
Cosima is an introvert, a runner & passionate community "gardener" (involved in several Open Space events on Agile & Software Craft). Her credo is: respect & adapt to achieve more TOGETHER!
In 2011, realizing it desperately needed to offer a competitive product to Airbus’ A320neo, Boeing embarked on a project to upgrade its legendary 737 aircraft to match the A320neo’s efficiency. Limited by the constraints of the 737’s original design and their desire to minimize training needed by pilots to fly the new aircraft, Boeing made multiple critical compromises in the aircraft’s design. 346 deaths and $87 billion later, we have all been reminded of the importance of rigorous design processes and the need to engineer systems for the realities of the end users and their environment. This talk dives into the motivations for the design compromises, the human factors considerations that were disregarded, and how a Fortune 100 company’s prioritization of profit over good design practice led to its stunning fall from grace.
Dr. Kyle Kotowick is the founder of a Canadian consulting and development firm focusing on cloud infrastructure, security, and Internet-of-Things implementations for high-growth clients. He completed his Ph.D. in MIT's Computer Science and Artificial Intelligence Laboratory, joint with the Department of Aeronautics and Astronautics. He has served as a consultant, systems architect, and developer for global firms, startups, and universities; as a Lead Engineer for the Government of Canada; and as a researcher for military navigation systems and for life support systems in space.