On this site, there is only displayed the English speaking sessions of the OOP 2022 Digital. You can find all conference sessions, including the German speaking ones, here.
The times given in the conference program of OOP 2022 Digital correspond to Central European Time (CET).
By clicking on "EVENT 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.
Today we must deal with shorter time-to-market, increasing complexity and more agility while keeping quality and other key system properties high.
To address these challenges the right timing in testing is critical but often not explicitly tackled. Therefore, in this interactive tutorial we reflect on our current approach on timing in testing, investigate and discuss needed strategies, tactics, and practices in different areas, and share experiences and lessons learned to improve timing in testing – because it is time to act now!
Maximum number of participants: 50
Target Audience: Test Architects, Test Engineers, Product Owners, Quality Managers, Software Architects, Developers
Prerequisites: Basic knowledge about testing and quality engineering
Today we must deal with shorter time-to-market, increasing complexity and more agility while keeping quality and other key system properties high. Our test systems increase in size, volume, flexibility, velocity, complexity, and unpredictability. Additionally, digitalization requires more than just a face lift in testing.
To address these challenges the right timing in testing (“when to do what kind of testing and how?”) is critical, but often not explicitly tackled. Therefore, in this interactive tutorial we reflect on our current approach on timing in testing, investigate and discuss needed strategies, tactics, and practices in different areas, and share experiences and lessons learned to improve timing in testing – because it is time to act now!
Some of the areas in testing that are covered in the tutorial are:
Peter Zimmerer is a Principal Key Expert Engineer at Siemens AG, Technology, in Munich, Germany. For more than 30 years he has been working in the field of software testing and quality engineering. He performs consulting, coaching, and training on test management and test engineering practices in real-world projects and drives research and innovation in this area. As ISTQB® Certified Tester Full Advanced Level he is a member of the German Testing Board (GTB). Peter has authored several journal and conference contributions and is a frequent speaker at international conferences.
This tutorial introduces to agile requirements engineering. The half day delivers practical guidance from our projects across different industries. While being based on the IREB agile RE primer curriculum, it has more practical focus and avoids agile basics and theory. Yet, participants are eligible to IREB certification. We give practical tips for designing agile requirements processes. Attendees will learn how to combine needs of systematic requirements engineering with agile principles. Special focus is given to connect RE with agile project management and with testing. A hands-on case study shows practical usage of agile RE.
Target Audience: Project Managers, Architects, Analysts, Requirements Engineers, Product Owners, Software Engineers
Agile projects need agile requirements engineering. Innovations in increasingly complex systems under cost pressure and in global competition demand for continuous alignment towards value and costs. The key to value delivery is requirements. They are no longer "collected" but must be developed in a targeted manner with suitable interest groups. Requirements are not frozen at an early stage but must be flexibly addressed throughout the project and product. However, agile requirements engineering is difficult to implement, especially in critical systems because of complex dependencies, growing quality requirements and diverse coordination processes.
Agile requirements engineering is not just a trivial priority setting. Leaving our some requirements when time and budget are scarce does not work in critical systems. Design thinking and team-based decision-making are nice for small applications, but hardly scale in larger industrial projects. Describing requirements vaguely and hoping that they become clear in the course of the project has already ruined many projects. Agile requirements engineering in critical and compliant context must combine the needs of classic requirements engineering with the flexibility of agile action.
This tutorial introduces to agile requirements engineering. It offers many practical examples from our industry projects when introducing agility. The training considers the IREB agile RE primer curriculum, however with more practical focus from many agile projects across industries. Participants are eligible to IREB certification. We give practical tips for designing agile requirements processes.
This begins with a value-oriented elaboration of the actual need. Then we look at techniques like Kano model, planning poker, design thinking, Kanban etc. In an industry case study, we present experiences and benefits of agile requirements engineering in a medical technology project with Siemens Healthineers. In particular, we use concrete examples and industry experience to show how agile requirements engineering is implemented in practice. This allowed us to reduce the costs for reworking by about 30%. The experience gained can be transferred to other projects and environments.
As a product manager or project manager, you will learn how to merge systematic requirements engineering with agile principles. As a successful requirements engineer or system analyst, you will learn how to use and scale agile techniques for requirements engineering.
Christof Ebert is managing director at Vector Consulting Services. He supports clients around the world in agile transformations. Before he had been working for ten years in global senior management positions. A trusted advisor and a member of several of industry boards, he is a professor at the University of Stuttgart and at Sorbonne in Paris. He authored several books including "Requirements Engineering" published by dPunkt and in China by Motor Press. He is serving on the editorial Boards of "IEEE Software" and "Journal of Systems and Software (JSS)".
Functional programming is the future of software development. As software gets ever more complex, unintended side effects flourish - you push on one side, and something unexpected squirts out the other. Functional programming cuts down on complexity through high-level abstractions and avoids unintended side effects through pure functions. The result is simple and elegant code that captures the essence of the problem you're trying to solve. Fortunately, functional programming is easy to learn, and this tutorial will get you started.
Target audience: Architects, Developers
Functional programming is the logical continuation of object-oriented programming: OOP managed to encapsulate mutable state with the goal of ultimately eliminating it one day, and functional programming finally realizes that vision. Language implementations have been mature and robust for many years now, and the practical functional languages - Haskell, OCaml, Scala, Clojure, F#, Racket, Erlang, Elixir, Swift - all have thriving communities and ecosystems. Moreover, decades of experience and research teaching functional programming have produced effective didactic approaches that enable anyone into programming to easily get into FP. The time to get started is now!
Michael Sperber is CEO of Active Group in Tübingen, Germany. Mike specializes in functional programming and has been an internationally recognized expert in the field: He has spoken at the top conferences in programming languages, authored many papers on the subject as well as several books. Moreover, he is an expert on teaching programming.
Security is an important topic, especially when developing software. But it is seen as complex and is holding everyone back, often put off until the end and delegated to an external person or group.
To be effective security needs to be a continuous part of the development process and to involve the whole team.
Security games can help to achieve this. They involve the whole team and facilitate the learning and application of security principles. They offer a way to integrate expert knowledge and make security less scary, maybe even fun.
Maximum number of participants: 50
Target Audience: Architects, Developers, Project Leaders, Testers, Security Experts
Prerequisites: General interest in security, basic development experience
Traditionally, requirements were used as a means to communicate between customers and development organizations. Unfortunately, requirements suffer from many limitations.
An alternative approach is to focus on outcomes and to use value modeling as a mechanism to quantitatively define the desired outcomes. This value model can then be used for experimentation by humans using DevOps and A/B testing or using machine learning models for automated experimentation.
The tutorial provides introduction of the topics and exercises.
Target Audience: Architects, Product Managers, Senior Developers, Business Leaders
Do you know that some forecasts project that in 2030 IT will account for 21% of all energy consumption? So, if we do not change the way we implement software, we will contribute to the increase in the carbon footprint. This means it is about time to take another look at how agile development can help decrease energy consumption.
In this workshop, we'll explore how the agile principles can guide us to more sustainability, and we'll provide you with concrete ideas for increasing sustainability in your product development.
Maximum number of participants: 100
Target Audience: Developers, Managers, Scrum Master, Product Owners, Coaches, ...
Prerequisites: Basic knowledge in agile would be helpful
The Agile Manifesto captures "better ways of developing software" yet, could this better way also take the environmental, economic, and social footprints of your software into account?
Software lifecycle creates direct and indirect carbon emissions: it has a footprint, worsening environmental problems. So, this session tries to provide the first answers to "how can the agile principles contribute to or guide sustainability?" In this workshop, we want to examine how the principles of the Agile Manifesto can provide guidance for implementing sustainability in IT.
In this workshop, we will explore the impact of the agile principles on sustainability, and how a greater awareness can change our current way of working for providing our contribution to addressing climate change.
Jutta Eckstein arbeitet weltweit als Business-Coach, Change-Managerin & Beraterin. Ihr Fokus liegt auf unternehmensweiter Agilität in großen & verteilten Organisationen. Sie war von 2003 bis 2007 im Vorstand der AgileAlliance. Sie hat einen M.A. in Business Coaching & Change Management, einen Dipl.-Ing. in Product-Engineering und ist als Immissionsschutzbeauftragte (Umweltschutz) zertifiziert. Jutta wurde 2011 von der Computerwoche in die Top 100 der bedeutendsten Persönlichkeiten der Deutschen IT gewählt.
There are several architecture models with prescribed views and notations. The Keep It Short & Simple architecture model is different. We create pieces of documentation iff they benefit stakeholders. We do so using drawing tools, not modeling tools. We say no to BDUF and yes to Important Design Up Front. We follow 7 tips for creating diagrams that are expressive, not ambiguous, and help you to successfully understand and evolve them, and build a system from them. We complement the design diagrams that describe structure and behavior with ADRs.
Target Audience: Developers and anyone else who plays the role of architect.
Prerequisites: If you've ever developed software, you're ready.
Do you create or use architecture documentation? Have you ever been confused and wondered about the meaning of a box or arrow in a design diagram? Do you think architecture documentation is costly or time consuming? If your answer is yes to any of these questions, this tutorial has practical and valuable information for you. There are several proposed architecture models with prescribed views and notations. The Keep It Short and Simple architecture model is different. We create pieces of documentation if they benefit stakeholders. We do so primarily use drawing tools, not modelling tools. We say no to Big Design Up Front (BDUF) but say yes to Important Design Up Front (IDUF). We follow 7 guidelines for creating informal design diagrams that are expressive, not ambiguous, and effectively help you and others to successfully understand them, evolve them, and build a system from them. Finally, we complement the essential design diagrams that describe structure and behaviour with architecture decision records (ADRs) for the important design decisions.
In the tutorial we look at several example architectures from real world systems. Most are good examples, but we also turn a critical eye on known products' architecture diagrams with several opportunities for improvement. Participants can also share their experience throughout. The tutorial also includes a fun online game and a hands-on exercise.
Tutorial minutiae include: what is the minimum architecture documentation expected, what design decisions are important enough to deserve an ADR, examples of drawing tools, who should be responsible for architecture documentation, how to complement structural diagrams with behavior diagrams.
Despite being hyped in the Agile community because of Google discovering its importance, psychological safety alone is not enough. It is a necessary but not sufficient precondition for successful intelligent and high-performing teams. But what else is needed? This workshop will present additional research as well as tools used by psychologists that boost team intelligence and performance and explore the potential for their use in their teams. Participants will have the opportunity to try some tools and learn how to design their own.
Maximum number of participants: 30
Target Audience: Coaches, Scrum Masters
Prerequisites: English, basic knowledge of statistics
Despite being hyped in the Agile community because of Google discovering its importance, psychological safety alone is not enough. It is a necessary but not sufficient precondition for successful intelligent and high-performing teams. But what else is needed? This workshop will present additional research as well as tools used by psychologists that boost team intelligence and performance and explore the potential for their use in Scrum teams.
After attending this workshop, the attendee will
A quiet and reserved researcher and practitioner with over 25 years experience, Joseph Pelrine is considered by cognoscenti to be one of the pioneers and top experts on Agile methods. As a psychologist, his focus on people and his experience in applying leading-edge techniques from social complexity and psychology to process optimisation goes far beyond the domain of software development, and extends to the whole organisation.