On this site, there is only displayed the English speaking sessions of the OOP 2021 Digital. You can find all conference sessions, including the German speaking ones, here.
The times given in the conference program of OOP 2021 Digital 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.
Track: Trends & Techniques
- Back to Architecture
- Business Agility
- Design Erosion & Learning from Failure
- DevOps & Continuous Everything
- Diversity & Inclusion
- Domain-Driven Design moving forward
- Full Day Tutorial
- Fusion: IT-Future-Society
- Half Day Tutorial
- Modern C++ Programming
- Modern Enterprise Architecture
- Product Discovery, Customer Centricity & RE
- Signature Track: Back to the Future
- Social Integration
- Testing & Quality
- Trends & Techniques
35 years ago, Eliyahu Goldratt introduced the Theory of Constraints (ToC) in his seminal book "The Goal" as a new management paradigm for manufacturing plants, struggling with excess inventory, late deliveries, poor quality. The ToC solved this through five focusing steps - a guideline to systematic improvement and continuous learning.
Today, the ToC is one of the pillars of the DevOps movement. This talk will present its principles, and how it applies to the software industry, through a mix of theory, stories and experiences, and practical advice.
Target Audience: Architects, Developers, Project Leaders, Managers, Decision Makers
Prerequisites: Some previous knowledge of software delivery is helpful, but not required
Having found a home as consultant, crafter and coach at codecentric in 2014, he strives to help customers to build and improve not only their product, but also how it is made.
He is a passionate advocate for collaborative work environments, knowledge sharing, and diversity.
On the side, he founded ThinkingLabs where he advises organisations in the adoption of Continuous Integration and Continuous Delivery.
Thierry is a lean software engineer, junior ops engineer, CI/CD advocate and jack-of-all-trades with a passion to help teams create meaningful software, with a keen eye for code quality and the software delivery process, from customer interaction to continuous delivery. Instead of balancing quality and delivery, he believes and practices, that better quality is actually a way to more and better deliveries.
This talk will provide insights for a successful integration of lean-quality management to scaled agile projects. We will show based on our project experience that by improving process quality, higher product quality is achieved, resulting in significantly increased customer satisfaction. We will share how the lean principles and an easy-to-use toolkit helped us to tackle complex problems by providing a proven and scalable approach for continuous improvement and boost business agility at the same time.
Target Audience: Quality & Test Engineers, Agile Coaches, Project Managers, Quality Managers
Prerequisites: Solid agile knowledge, basic lean understanding, basic understanding of quality assurance
Apache Kafka became the de facto standard for microservice architectures. Decoupled applications and Domain-driven Design (DDD) are key benefits. However, that also introduces new challenges like observability of the whole ecosystem. This session explores the problems of distributed Microservices communication and how Kafka, Kubernetes and a Service Mesh like Istio address them. Learn some approaches for combining them to build a reliable and scalable microservice architecture with decoupled and secure microservices.
Target Audience: Software Architects, Consultants, Developers, Project Leads
Prerequisites: Experience with distributed systems / messaging frameworks is helpful
Apache Kafka became the de facto standard for microservice architectures. It goes far beyond reliable and scalable high-volume messaging. In addition, you can leverage Kafka Connect for integration and the Kafka Streams API for building lightweight stream processing microservices in autonomous teams. Decoupled applications and Domain-driven Design (DDD) are key benefits. However, microservices also introduce new challenges like observability of the whole ecosystem.
A Service Mesh technology like Istio (including Envoy) complements the architecture. It describes the network of microservices that make up such applications and the interactions between them. Its requirements can include discovery, load balancing, failure recovery, metrics, and monitoring. A service mesh also often has more complex operational requirements, like A/B testing, canary rollouts, rate limiting, access control, and end-to-end authentication.
This session explores the problems of distributed Microservices communication and how both Apache Kafka and Service Mesh solutions address it together on top of Kubernetes. I cover different approaches for combining both to build a reliable and scalable microservice architecture with decoupled and secure microservices.
We took advantage of the COVID digitalization challenge and converted our Design Sprints and UX workshops into a digital format. A dozen customer workshops in a wide variety of contexts (including logistics, public and chemical clients) have demonstrated UX workshops can also work virtualized with some advantages, e.g. being able to integrate participants from remote locations cost-effectively. In this session evaluated tools, techniques, best practices and lessons learned virtualizing UX workshops will be presented and discussed.
Target Audience: UX Practitioners, Business Analysts, Project Leaders, Decision Makers
Prerequisites: Familiarity with regular onsite Design Sprints does help, although I will provide a short recap
Languages that raise the level of abstraction closer to the problem domain help improve quality and productivity. This can be best achieved when the language is directly based on the problem domain, not implementation concepts or existing languages. We describe how to create domain-specific languages in tight collaboration with domain expert users: as soon as a language concept is defined it can be immediately applied by users. We demonstrate this with examples from various fields, such as automotive, home electronics and automation systems.
Target Audience: Developers, subject matter/domain experts, managers
Prerequisites: experiences on applying some modeling language
This talk is based on industry experiences on applying domain terminology directly in a modeling language (in its grammar). This way domain experts can apply familiar terminology, and map the specifications directly to code, to other more technical models, or the same set of models are shared by both domain experts and developers. The talk starts with a practical example how domain experts from different fields can collaboratively edit the same specifications each having own background (industry process, software, hardware, communication). Next the talk describes guidelines how such languages can be created: how domain terminology is defined into a language and how such language can be applied. These guidelines are demonstrated with examples from practice, such as how functional safety engineers can collaborate using ISO26262 (functional safety standard) terminology and related them to the technical system development; and how UX and UI persons can define user interfaces and their behavior in a manner allowing developers to join and work with the same models. The talk is concluded with guidelines and hints backed by industry cases from companies like Panasonic and Elektrobit.
Picture burnout as a system where you have multiple variables and details to combine:
Expectations, rules, routines, emotions and workload.
Now add Agile Transformation where all of the above are present. And see a receipt for personal disaster.
Agile Transformations play a big role in my experience, for I have seen many of them both as a professional coach and a team member in a transforming organization. Being burned out, on the edge and enduring burnout.
The session is a case with steps I have uncovered in serving teams and myself.
Target Audience: Managers, Decision Makers, Leaders, Coaches
Prerequisites: Team working experience, leadership experience
Picture burnout as a system.
Now add Agile Transformation.
And see a receipt for personal disaster.
Change of structure, roles, policies, and, most importantly – expectations. This is where humans suffer the most, and where coaches can help the most if we are sufficiently equipped.
There is an individual burnout that occurs due to the pressure that you exert on yourself – this is very common among those who are perfectionists (CEOs or CIOs in our context).
There is also interpersonal attrition, which is caused by complicated work relationships (can you imagine working alone on your routine tasks and now being in a team with that particular person you dreaded for decades?)
And finally, there is organizational exhaustion, which is caused by poor organization and unrealistic demands made on you by others (the tremendous top-down start of transformation).
Transformation missions where coaches are hired to observe, lead, encourage others to mastery, and set up daily routines and ceremonies. Is there more?
First of all, hence you are in a coaching position, your main task is not to have a strong opinion from day one, rather download, expand your perception filter, connect emotionally and act from an open heart.
The session aims at providing the toolkit to those in transformation and those in burnout. We will use Theory U practices, personal resilience coaching, and emotional intelligence assessments. To see how these combine with leadership and agile coaching on a daily basis and very hands-on activities.