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.
Thema: Requirements Engineering
- Artificial Intelligence Now!
- C++ and Programming of Embedded Systems
- DevOps & Automation Now!
- Diversity & Inclusion
- From Projects to Products/Services: Aligning Architecture and Organization for Sustainable Speed
- Full Day Tutorial
- Fusion: IT-Future-Society
- Half Day Tutorial
- Modern Software Architecture
- Product Development in Times of Digitalization
- Signature Track: The Time is Now!
- Social Integration
- Software Architecture Communication & Assessment
- Testing & Quality
- Trends & Techniques
- Use Domain-Driven Design Now!
- Artificial Intelligence
- Domain-Driven Design
- Product Development
- Programming Languages
- Requirements Engineering
- Soft Skills/Social Skills
- Software Engineering
- Talks with Limited Attendance
- Testing & Quality
- Virtual Reality
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.
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
The world in which a software system lives is filled with meaning. The structure, concepts and names that inform the code, its changes and the mental models held by developers are expressions of meaning. The very act of development is an exercise in meaning — it's discovery, its formulation, its communication.
But just because we are immersed in concepts of meaning from an early age, and just because the daily work of software development is about wrangling meaning, that doesn't mean we're necessarily good at it. Let's talk about what we mean.
Target Audience: Developers, Architects, UX, Product Owners
Prerequisites: No specific prerequisites
"It's just semantics." How many conversations about philosophy, politics and programming are derailed by this thought-stopping comment?
Semantics is all about meaning. If there is one thing we struggle with and need to get better at, it is the search for and clarification of meaning. The world in which a software system lives is filled with meaning. The structure, concepts and names that inform the code, its changes and the mental models held by developers are expressions of meaning. The very act of development is an exercise in meaning — it's discovery, its formulation, its communication. Paradigms, processes and practices are anchored in different ways of thinking about and arriving at meaning.
But just because we are immersed in concepts of meaning from an early age, and just because the daily work of software development is about wrangling meaning, and just because it's just semantics, that doesn't mean we're necessarily good at it. It takes effort and insight. Let's talk about what we mean.