Micro-Frontends eigenen sich nicht in allen Szenarien! Diese Session stellt einen alternativen Ansatz vor: Frontend-Modulithen. Wir besprechen das Abbilden fachlicher Domänen, die Kategorisierung von Bibliotheken sowie Zugriffseinschränkungen zum Erzwingen entkoppelter Teilsysteme. Außerdem nutzen wir inkrementelle Builds und einen Build Cache zur drastischen Beschleunigung des CI-Prozesses. Am Ende wissen Sie, ob Frontend-Modulithen für Sie der richtige Ansatz sind und wie Sie Ihre Anwendungen damit aufbauen.

Zielpublikum: Architekt:innen, Entwickler:innen
Voraussetzungen: Grundlagenwissen zu JavaScript von Vorteil
Schwierigkeitsgrad: Fortgeschritten

Imagine you have an enterprise frontend monolith. Due to explosive growth, around 30 teams work on it, with about 100 different use cases. How do you keep this system scalable and consistent?
That's the question we faced inside Partner Home at Wayfair. I'm going to share our experience implementing a micro frontend architecture based on React to distribute shared concerns as long-lived applications. We used module federation, a new feature in Webpack 5.
I'll talk about the general architecture, plus an overview of our technical solution.

Target Audience: Architects, Developers
Prerequisites: English, Frontend Architecture, React
Level: Expert

Orchestrating the work of hundreds or thousands of people working at different locations around the world presents a set of challenges specific to that kind of context. It is not simply a matter of “scaling up", we need to understand underlying principles and patterns and make them work. With this session we invite you into a conversation about how to improve the way leaders and teams collaborate in our organizations. You will experience a workshop that you can reproduce for your organisation to create supporting structures that scale

Target Audience: Thinkers, Decision Makers, Architects, Managers, Coaches, Scrum Masters, Product Owners
Prerequisites: Curiosity and some experience in working in large organisations
Level: Advanced

Extended Abstract
Orchestrating the work of hundreds or thousands of people working at different locations around the world presents a set of challenges specific to that kind of context. It is not simply a matter of “scaling up” what works for orchestrating the work of a small number of co-located people, or even a small number of distributed teams. The specific practices necessary for success will vary and evolve. Variety of practice is essential to creating successful outcomes.
There is a useful set of underlying principles and patterns that we bring to our work. They enable us to create a wide variety of context-aware practices that serve the needs of the people in our organizations, and support them in collaborating to create value for our customers.
With this session we invite you into a conversation about how to improve the way leaders and teams collaborate in our organizations. We will look at teams’ needs regarding autonomy, leadership, and support, and at leaders’ needs regarding strategy, challenges, and responsibility. One specific theme we explore in this session is that of the relationships between leaders and teams, and how we leverage those relationships to orchestrate work and outcomes.
Through this session you will experience a workshop that you can reproduce for your organisation. We will share our setup guides, tools, and materials with you so that you can create supporting structures to more effectively orchestrate collaboration at different scales in your organization.

How will organizations keep agility alive after their initial agile transformation? The question of what happens if agile becomes daily business is even more intriguing in this post-pandemic COVID era. Will AGILE survive these unparalleled insecure times? Participants in this workshop will explore what is needed to sustainably ‘safeguard’ an enterprise agile delivery culture after the initial ‘agile transformation’. The workshop hosts will share their observations of working in a big financial organization and will invite participants to share theirs so that collectively, we can gain insight and define potential countermeasures.

Target Audience: Anyone interested in transformational agility challenges, e.g. Change Lead, Coach, BusArchitect
Prerequisites: None
Level: Advanced

Extended Abstract
Participants in this workshop will explore what is needed to move forward after the initial ‘agile transformation’, to sustainably ‘safeguard’ an enterprise agile delivery culture. The question of what happens if agile becomes daily business is even more intriguing in this post-pandemic COVID era. How will organizations keep agility alive after their initial agile transformation? When organizational systems come under too much pressure; how ‘VUCA’* resistant are our agile enterprise cultures?
Lieke Jansen and Eric Abelen are senior Agile Enterprise Coaches at ING in the Netherlands. They both contributed to ING's Spotify inspired, big-scale transformation towards an agile way of working, some seven years ago. As of then, they have successfully coached a wide variety of departments and organizations within ING to adopt and sustain an effective healthy agile delivery culture. Being key players of a massive enterprise agile transformation, they also observe some challenges related to upkeep of the resulting way of working. Because people come and go, and in our VUCA world business and process change is frequent. What options do we have in this reality of ongoing change to keep the ‘agile enterprise culture’ strong and resilient?
Also, in the Covid pandemic we learned that people and organizations can respond to change quickly, especially those organizations that adopted a culture of agility. But after a period of unparalleled social restrictions, how does this affect our agile corporate cultures? Has the trauma of the pandemic infected us with a renewed urge to feel ‘in control’ of the future and has this irrevocably injured our appetite for organic growth and agility?
In this workshop we will explore this interesting and urgent question together with you. We will share key observations from experience working with a wide variety of delivery and leadership teams and their related organizational structures. We hope that workshop participants are willing to add their observations and experiences to ours. In interactive dialogue sessions we hope to collectively engage in sense-making and to define basic anti-patterns and growth-paths.
( * VUCA = Volatility, Uncertainty, Complexity, Ambiguity)

C++20 is now a year old. Time to take a closer look at the benefits you get when using C++ for standards 11 to 20. You learn about Coroutines by building a coroutine-based parser. The new ranges and the spaceship operator help you write less code. You will learn how Concepts help you to express constraints better and improve error messages. Doing things at compile-time saves run-time. Let‘s see how C++20 improves your code with the new features consteval and constinit. After this talk, you learned some C++20 features and saw the improvements to C++17 code.

Target Audience: Developers
Prerequisites: Knowledge about at least C++11
Level: Advanced       

Extended Abstract
C++20 is now a year old. The major compilers already provide a solid support for the new standard. It is time to take a closer look and figure out the benefits you get when using C++20. Because there are so many improvements in C++20, we will focus on: Concepts, Coroutines, ranges, the spaceship operator, and compile-time evaluation.
Coroutines are the feature that likely will have a strong impact on future finite state machine code. In a brief tour, we will see what we need to do for building a coroutine-based byte-stream parser and how this code is so much more beautiful than without Coroutines.
Less code is always a good thing. The new ranges part of the STL helps us achieve this goal. We will take a brief look at how ranges simplify our code.
Speaking about less code, how about writing a class with all comparison operations without having to write an awful amount of boilerplate code? Sounds good? Then let's see how C++20 helps us there with the spaceship operator.
And while we are speaking about less code, generic programming comes to mind. Concepts give us a whole new way to express constraints and requirements in generic code. Concepts make our code better readable while, at the same time, give us way better error messages.
We don't stop there. Together we will look at the updates to the compile-time world. With consteval and constinit we have two new keywords allowing us new things to do. A lot of former restrictions of constexpr functions were dropped as well. The most popular is probably the ability to dynamically allocate memory at compile-time. We will explore these features using some practical examples.
After this talk, you will have seen the probably most impactful features of C++20. You learned by examples how to use them. The comparisons to pre-C++20 code give you a good understanding of what your benefits are by using C++20.

While Rust is typically pitched as systems programming language, it is equally adept at application development thanks to its high level features and great tooling. In addition to increased performance, native code has the advantage that it can easily be reused across different system components, an advantage even more pronounced in polyglot environments. In this talk, we would like to present our experience of using Rust to write core components in such a polyglot system.

Target Audience: Architects, Developers
Prerequisites: Basic knowledge of Python, Java
Level: Advanced

Extended Abstract
While Rust is typically pitched as systems programming language, it is equally adept at application development thanks to its high level features and great tooling. In addition to increased performance, native code has the advantage that it can easily be reused across different system components, an advantage even more pronounced in polyglot environments.
In this talk, we would like to present our experience of using Rust to write core components in such a polyglot system. The systems spans different contexts, from client to cloud, and different programming languages, from Python to Java, respectively. We will showcase how the Rust language itself and its tooling simplified this task and discuss different integration patterns.

Women in technology leave the industry at a higher rate than any other profession. In her invited talk, Nicola Marsden draws on deep research into what women love about work and what they don’t. Together with Karen Holtzblatt, the visionary behind Contextual Design, she has developed a research-driven framework and best-practice interventions to achieve better retention and work life culture for women in technology. She presents the framework and looks at Scrum as an example in terms of challenges and benefits for women.

Target Audience: Managers, Decision Makers, Agile Coaches, Project Leaders, Developers
Prerequisites: Interest :-)
Level: Basic

Today Computer vision has taken a significant spot in our phones, our roads, our markets that we don’t always even recognize if and where it is deployed. Nonetheless, our industries today have so much potential to automate (using CV) their recurrent tasks to reduce costs, while simultaneously increasing quality of the product and efficiency of the process itself. We will learn about some interesting industrial examples which benefit first-hand from simple automation and perhaps get inspired by it.

Target Audience: Software Developers, Data Scientists, AI Engineers, Managers, Project Leader, Decision Makers
Prerequisites: None
Level: Advanced

Extended Abstract
In the era of Industry 4.0, we are focusing on digitalizing operations using data. We let cameras ‘see’, detect and classify objects and even take some decisions for us. In this talk, we discuss what is Computer Vision (CV), and learn how could different industries benefit / save recurring costs from it. We will discuss some interesting industrial applications of Computer Vision, for you to get some inspiration on how it can potentially help your company grow, or just to understand the advancements in today’s world.
In these 45 mins, we discuss how CV can:
- automate the industrial processes
- be more then more efficient,
- ensure the product quality,
- or detect anomalies.
Using some demos and videos you’ll get the chance to consolidate the knowledge acquired during the talk.

C++ class design has been error prone since the beginning, until Scott Meyers told us about the Rule-of-Three. But even that is not enforced by the language. In addition, C++11 changed the set of compiler-provided special member functions and the intrinsic rules have become more complicated. However, instead of starting from the rules for special member functions, we will look at what role a class type plays and how that maps on what special member functions to define and how, if any. Examples for class roles are Value, Relationship, Manager (scoped, unique, general), Mix-in.  

We will also look at the roles of member variable types that influence or imply the role of the class type. The role of a class will also take out many mysteries of move operations and will lead to clear guidance when and how to provide move operations: for suppressing copying, for managing unique ownership (Unique Manager) or for optimizing object copies (General Manager). We will rehearse the Rule of Zero and learn more about the Rule of Five/Six, the Rule of DesDeMovA, and the Rule of Unique Three. This all will enable you to much more consciously and safely design your class types and combine types of member variables. You will have then the ability to select from a few reasonable combinations from the plethora of possibilities of special member function combinations: {public:,protected:,private:} x {destructor, default constructor, copy constructor, copy assignment, move constructor, assignment} x {noexcept(true),noexcept(false)} x { =default, =delete, {/body/}, not declared } (math as homework)

Target Audience: Developers
Prerequisites: C++ class design
Level: Expert

Many of us have a rough idea of what side-effects are and a vague sense that they're bad. It's a shame we're not more precise about it, because when you really understand side-effects you have an excellent new lens through which you can judge individual blocks of code, larger architectural patterns, and even whole system designs. So let's start by clarifying our understanding of what side-effects are and how to spot them. We'll see how easily they arise, leaving code that's harder to understand, harder to test and harder to decouple. Then we'll look at tools and techniques for eliminating those side-effects where it's possible and managing them where it isn't. Finally we'll zoom out to see how those ideas get expressed in every field of computing, yielding fundamentally different approaches to programming language design, DevOps, system architecture, and database design. There's an iceberg of complexity hiding in your systems' side-effects and by the end of this talk you'll be able to spot it and start tackling it, rethinking the way we deal with data and the systems around it."
 

Software is often resistant to modernization efforts, no matter if it's about phasing out obsolete technologies, migration to the cloud, or establishing modern architecture. The culprit is usually a dependency or obsolete assumption that's too closely coupled to the codebase. But what's the underlying root cause of all that coupling? Often, it's shared, mutable, synchronous state. We will look at a real-world project, and we'll dig ourselves out of the hole it's dug itself into using refactoring, event sourcing, and functional programming.

Target Audience: Architects, Developers
Prerequisites: Some programming
Level: Basic

Extended Abstract:
As shared mutable state is the core paradigm of object-oriented programming, it tends to be ubiquitous in OO projects. How to avoid it then? The example has followed a familiar path: Convenient tooling allowed the project to get off the ground fast, but tied it to its underlying technologies. By the time support for those technologies has expired, coupling has gotten so strong that huge resources are expended on keeping things going "just one more day". If you've seen projects like this hit a wall, this talk is for you.

In today’s software-driven world, the integrity of software assets isn’t just a regulatory and compliance requirement, it’s critical for maintaining trust and avoiding irreparable damage to your brand and reputation. We found that Compliance, Software Chain of custody and in-App Security as well as API Security are seen as an overburdened bureaucracy. But they have to be part of your software value stream. So the question is, how they can be so lean, automated and optimized that they can contribute actual value inside your DevSecOps Approach?

Target Audience: Architects, Developers
Prerequisites: Project development experience
Level: Advanced

Extended Abstract
In today’s software-driven world, the integrity of software assets isn’t just a regulatory and compliance requirement, it’s critical for maintaining trust and avoiding irreparable damage to your brand and reputation.
The same also applies to Quality, In-App Security, and API Security in a more and more digitized world.
In a lot of case studies, we found that Compliance, Software Chain of custody and in-App Security as well as API Security are seen as an overburdened bureaucracy. But in all cases, they have to be part of your software value stream.
So the question is, how they can be so lean, automated, and optimized that they can contribute actual value inside your DevSecOps Approach? In the lecture we provide some key insight in how to solve that dilemma and integrate them into your day-to-day work.

For many embedded C++ applications, compliance with the AUTOSAR or Misra rules is required. Among them is AUTOSAR Rule A18-5-5 which does not allow memory allocations with new. Since new and delete violate A18-5-5, the default STL containers must not be used in applications requiring AUTOSAR compliance. This holds for many embedded applications. With the allocators available since C++17 in the namespace std::pmr (polymorphic memory resources) these requirements can often be satisfied.

Target Audience: Architects, Developers, Project Leader
Prerequisites: Good C++ knowledge
Level: Advanced

Extended Abstract
For many embedded C++ applications, compliance with the AUTOSAR or Misra rules is required. Among them is AUTOSAR Rule A18-5-5.
Memory management functions shall ensure the following:
(a) deterministic behavior resulting with the existence of worst-case execution time,
(b) avoiding memory fragmentation,
(c) avoid running out of memory,
(d) avoiding mismatched allocations or deallocations,
(e) no dependence on non-deterministic calls to kernel.

This rule has far-reaching consequences, because per default the C++ standard library containers allocate their memory with new and free it with delete. These calls
• do not have deterministic execution times.
• can cause memory fragmentation.

Since new and delete violate A18-5-5, the default STL containers must not be used in applications requiring AUTOSAR compliance. This holds for many embedded applications.
With the allocators available since C++17 in the namespace std::pmr (polymorphic memory resources) these requirements can often be satisfied. This means that, for the first time in the history of C++, the containers and algorithms of the C++ standard library can be used in applications that require AUTOSAR Rule A18-5-5.

The purpose of Serverless is to focus on writing the code that delivers business value and offload undifferentiated heavy lifting to the Cloud providers or SaaS vendors. Today’s code quickly becomes tomorrow’s technical debt. The less you own, the better it is from the maintainability point of view. In this talk I will go through examples of the various Serverless architectures on AWS where you glue together different Serverless managed services, significantly reducing the amount of the code written to perform the task. Own less, build more!

Target Audience: Developers, Architects, Decision Makers
Prerequisites: Basic understanding of AWS Serverless Services
Level: Advanced 

In a world of rapid changes and increasing uncertainties, organizations have to continuously adapt and evolve to remain competitive and excel in the market. In such a dynamic business landscape organizations need to design for adaptability. Designing for adaptability requires understanding the landscape organizations are operating in, identifying patterns of change, applying principles for organizational fitness, and making mindful strategic decisions to adapt change.

Target Audience: Software Architects, Tech Leads, Engineering Manager, VP of Engineering
Level: Basic

Extended Abstract
Organizations need to aim for building systems and team organizations aligned to the business needs and business strategy and evolving them for adaptability to new changes and unknown environments.
This talk brings different perspectives and techniques together from business strategy (Wardley Mapping), software architecture (Domain-Driven Design), and team organization (Team Topologies) as a powerful toolset to design, build and evolve adaptive systems and team structures for a fast flow of change.

New MISRA C++ 202x are coming. This release will address modern C++ and thus is relevant not only for safety critical code in the automotive sector, but also for day-to-day C++ development. Expect the new MISRA rules to be less "miserable" for your day-to-day coding and use static analysis tooling to enforce them. Understand what kind of C++ will be considered unsafe, get examples of guidelines and learn which rules better to suppress in static analysis tools in non-safety-critical software.

Target Audience: Developers
Prerequisites: C++
Level: Advanced 

Extended Abstract
New MISRA C++ guidelines are coming. In contrast to the previous release in 2008, MISRA C++ will address modern C++ as it is used in modern automotive systems. It is expected that other domains with safety critical software will incorporate MISRA C++ as well. In addition many of the rules, especially those supported by corresponding static analysis tools, can make your own C++ coding practices better. The talk briefly introduce the development of safety critical software, highlight some of the modern MISRA C++ rules applicable to all kinds of code and will also show corners of the rule set, better avoided for "normal" C++ code. The latter is important to know, when you are asked to retrofit your code to the output of a static analyzer tuned to MISRA-C++.
* History of MISRA C++ guidelines
* Peculiarities of software development for safety-critical systems
* Example guidelines and how they influence coding
* "strong stuff" that should not bother in normal C++
* Outlook on further revisions

What have we learnt from the transformations in large companies? And how can that help you improving your chances for success?

The DACH30 group is a workgroup of experienced transformation drivers and coaches from over 30 large companies across different industries. One sub-workgroup has been working on these two questions and we recently published our findings.

In this workshop we will share our transformation experiences and work out with you on patterns, that have proven to be helpful in driving agile transformations successfully.

Target Audience: Leaders especially on executive level and organizational development coaches
Prerequisites: Experiences in driving an agile transformation in a large organization
Level: Advanced

Extended Abstract

As internal Agile Transformation Coaches from large enterprises we have been supporting quite a number of transformations in various contexts. And as members of a workgroup for Business Agility we were asking ourselves „What can we learn from the different company transformations in the different markets and branches with different cultures? Is there anything they have in common?“ We were quite thrilled to identify some principles and helpful insights and learnings based on success and failures which we found applicable to most of the transformations.

To provide inspiration for others, executives and leaders especially, we summarized these principles and learnings in a Transformation Travel Guide for Growing Adaptive Organizations, including a Travel Map, Travel Tips and also some exemplary Travel Routes based on real-life case studies.

In this session we will provide an overview on the Travel Guide and some deeper insights into learnings from two Transformation Journeys. Study.

Our focus is not on scaling Agile working but rather on achieving Agility on an enterprise level. Hence we are not only looking towards Agile but rather at various methods, thinking models, and techniques in order to find the right approach for specific business problems to solve and for developing organizational towards more adaptivity and resilience.

We are a smaller group from the DACH30 Initiative working on ‚Growing Adaptive Organizations’. growing-adaptive-organizations.org

(Agile) Games are sounding throughout the land. Everyone plays games and anyone guides games. However, what makes playing games "interesting" from the business owner's perspective? 

We look into the criteria of effectiveness and efficiency of games and thus the capabilities of creating business impact for the company.

As such, it turns out a game - is just a game and remains a play if one does not align with underlying business needs. Sounds familiar? But you wonder how to do so?

In this talk, we will look in a 4-Step-Modelmaking the obvious tangible. And in the end, it becomes a structured approach how one might create business impact too.

Target Audience: Moderators, (young) Scrum Masters, Project Leaders, Managers, Decision-Makers, Facilitators
Prerequisites: General understanding of games and agility, and how to lead games successfully
Level: Basic

So many challenges, so little time. As testers or quality engineers, we need to sharpen the saw, but how? Gamification can be a way to look at how you're doing and find out where to improve. It's a great way to have everyone engaged and get the best out of people.

In this presentation, Ben Linders will show how playing games (onsite or online) with the Agile Testing Coaching Cards and Agile Quality Coaching Cards help to explore your current quality and testing practice and decide as a team on what to improve or experiment with.

Target Audience: Testers, Agile Teams, Tech Leads, Technical Coaches, Scrum Masters
Prerequisites: None
Level: Advanced

Extended Abstract

The Agile Testing Coaching Cards and Agile Quality Coaching Cards are a deck of cards with statements that help people to share and reflect. Examples of cards are "Testers help developers design acceptance criteria for user stories", "Failing tests get proper attention even when no defect in the product has been detected", and "Refactoring is done to keep code maintainable and reduce technical debt".

Playing games with these coaching cards (onsite or online), you can learn from each other. Teams can use the coaching cards to discuss quality and testing values, principles, and practices, and share their experiences and learnings.

Different game formats can be used to share experiences on testing and quality principles and practices and explore how they can be applied effectively. The playing formats from the Agile Self-assessment Game (benlinders.com/game) can be used to play with these cards. This presentation provides an overview of playing formats and will inspire you to come up with your own formats.

Facilitation is key when playing with these coaching cards. Ben Linders will present how to prepare a game session and facilitate it, what can be done to keep people engaged, and how debriefing can help to pull out learnings and ideas for improvement.

Takeaways:

- Show how to use gamification to self-assess your current way of working.

- Present examples of playing games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards.

- Explore how facilitating games can help to enhance quality and testing in agile teams.

Wollen wir unseren Enkeln eine lebenswerte Welt hinterlassen, müssen wir das grundlegende Paradigma unseres Wirtschaftssystems umbauen: Weg vom ausbeuterischen Wirtschaften, hin zu einem regenerativen, demokratischeren und inklusiven Wirtschaften.

Der Vortrag ist ein Plädoyer dafür, nicht auf Politiker, Konzernchefs oder ein Wunder zu warten, sondern selbstbewusst aktiv zu werden. Wir stellen erste Ansätze vor, wie Agilität konkret genutzt werden kann, um den Umbau der Wirtschaft in Angriff zu nehmen.

Zielpublikum: Manager:innen, Entscheider:innen, Projektleiter, Teamleiter, ...
Voraussetzungen: Fachkenntnisse agiler Methoden,
Schwierigkeitsgrad: Fortgeschritten

Extended Abstract

Vor über 20 Jahren entstand das agile Manifest, das eine radikal neue Arbeitsweise für die Software-Entwicklung proklamierte. Was damals von vielen belächelt wurde, ist heute auch außerhalb der Software-Entwicklung gang und gäbe. Wir haben gesehen, dass agiles Arbeiten Teams effektiver machen und damit das Leben von Menschen positiv beeinflussen kann. Doch auch wenn sich das „Wie“ des Arbeitens verändert hat: Neue Geschäftsmodelle sind dadurch kaum entstanden.

Heute stehen wir jedoch vor einer neuen, ungleich größeren Herausforderung. Wenn wir unseren Kindern und Enkeln eine lebenswerte Welt hinterlassen wollen, müssen wir das grundlegende Paradigma unseres Wirtschaftssystems umbauen: Weg vom ausbeuterischen Wirtschaften, das Finanzmittel konzentriert und massive Ungleichheit erzeugt, hin zu einem regenerativen, demokratischeren und inklusiven Wirtschaften.

Die Sache ist: Einerseits weiß kaum jemand genau, wie nachhaltige Geschäftsmodelle tatsächlich aussehen müssen, welche Technologien noch entstehen und sich durchsetzen werden. Andererseits läuft uns die Zeit davon. Es herrscht Unsicherheit, gepaart mit Zeitdruck.

Genau das ist doch das ursprüngliche Spielfeld agiler Denk- und Arbeitsweisen! Gerade die Community hält alle Tools in den Händen, mit denen Unternehmen regenerative Geschäftsmodelle entwickeln können, die sogar wirtschaftlicher sind als die existierenden. Lasst uns doch die Zukunft gemeinsam gestalten, so wie wir es vor 20 Jahren schon mal gemacht haben. Arbeiten wir mit Unternehmen und Menschen, die diesen Planeten durch enkelfähiges Business erhalten wollen!

Der Vortrag ist ein Plädoyer dafür, nicht auf Politiker, Konzernchefs oder ein Wunder zu warten, sondern selbstbewusst aktiv zu werden. Wir stellen erste Ansätze vor, wie Agilität konkret genutzt werden kann, um den Umbau der Wirtschaft in Angriff zu nehmen.

This is a letter from the future: we are working in an organization in a galaxy not so far away … we have a #diverse #social #digital #remote #culture - and we will tell you how we got there. We leave it open to the audience to guess how far this future is away. Or how near they want it to be. Disclaimer: may contain fragments of reality.

Target Audience: Manager, Idealists, Realists, Change Makers
Prerequisites: Open mind
Level: Basic

Digitalization has been changing existing industry B2B businesses, digitalization business models arrived and the Digitalization solutions need to be developed to support this. The sudden enforcement of social distancing has given the digital transformation a significant push forward. How do we develop innovative Digitalization offerings in the future? We will show how to seize these opportunities and forge new paths toward the new normal for Software Engineering.

Target Audience: Software Engineers, System and Software Architects, Software Managers
Prerequisites: Knowledge in Software Engineering Practice
Level: Basic

The adoption of static analysis of C++ and Java requires that the findings and errors can be prioritised in an efficient way. Our work shows that Machine learning (ML) can support this presentation of static analysis results to end-users. The ML engine learns from the codebase itself, and also observes the violations that the user fixes and which he ignores. The ML uses this to suggest the next best violations to fix, relying on probability of violations to be harmful or most likely to be a noise.

Target Audience: Developer Managers, R&D Managers, Software Architects, Software Engineers
Prerequisites: English, Software development, Coding experience, C++, Java, C#.
Level: Expert

Extended Abstract
Static code analysis is often understood as a mandatory part for checking the source code compliance to government and industry regulations, company-wide guidelines and practices. It can play, however, a more fundamental role in estimating the quality of the code in general, understanding the amount of technical debt, creating the strategy to reduce the amount of technical debt, as well as a helper in making decisions on how to speed up the development by creating a more maintainable, understandable, sociable codebase.

However, by its nature, static code analysis is bound to produce a large amount of noise and false alerts that can distract the team from the actual bugs in the code and prevent them from working thoroughly with the findings. One of the reasons for that is the level of soundness of the static analysis tool. If we want to be sure that the analysis is bound to find all errors in the code, the static analysis tool has to report all possible candidates. The more sound the tool is configured to be, the larger the number of the possible errors is reported, which increases the number of false positives as well.

To improve the user experience of working with static analysis technology, we have developed a machine learning (ML) based approach to presenting the results of the static analysis to users. The ML engine can learn from the code base itself, from a user's preferences, as well as from the interaction within the team. At the code level, our engine learns from the syntactical and semantical structure of the analyzed code to understand which violations are more likely to cause more harm, which violations are more likely to be noise, what underlying problems can be fixed to drastically reduce the number of reported violations. At the user level, the ML engine observes which violations the user fixes and which violations the user ignores. Based on these observations, the ML engine builds a model and uses it to suggest the next best violations to fix.

Maintaining a database containing millions of products can be very challenging, especially when the information you require of these products is subject to changes over time.

We show how we used state of the art Deep Learning methods (such as Transformers, BERT) in connection with smart text matching in order to extract relevant information from free-form text.

We also explain how we leveraged the existing database to create an automatically labelled training dataset.

Our model enables us to continuously update idealos database automatically.

Target Audience: Decision Makers, Technical Project Leaders, Developers
Prerequisites: Basic knowledge of machine learning methodology
Level: Advanced

Extended Abstract

To maintain idealos product base, product information in the form of values of predefined product attributes needs to be extracted from free-form text product descriptions.

Before the use of a Machine Learning based solution, this process required a lot of manual work to define rules to extract this information. There is also a high effort connected to keeping these rules consistent across the whole database and different types of products, especially since the source of this information (the product descriptions) as well as the required information (the product properties) are subject to changes over time.

In this talk we present a machine learning solution, based on fine tuned state-of-the-art models such as BERT, which is able to extract product information automatically from product descriptions with production-ready performance.

Our solution contains two different models, each following one of the well-known problem settings in Natural Language Processing (NLP): Semantic Segmentation of text (also known as Token Classification) and Question Answering. We will present both models in detail, as well as discussing their advantages and disadvantages for solving the task at hand and how we measured its performance (metrics).

We will also emphasize the importance of identifying aspects of your data that ensure that the developed model can actually fulfill your business needs before curating your dataset.

This highlights another benefit of implementing a Machine Learning model for a huge database: You will get sanity checks of your existing data “for free”, as consistent data is a prerequisite for a successful Machine Learning project.

One problem that is very common in large organisations is that there is often no or only very little training data in the form of labels for specific text sections available. We show how we mitigated this problem by leveraging the existing database to generate a large artificial training dataset. This allowed us to only use a few thousand manually labelled examples for training and testing to reach sufficient performance.

To continuously deliver IT systems at speed with a focus on business value, high-performance IT delivery teams integrate quality engineering in their way of working.

Quality engineering is the new concept in achieving the right quality of IT systems. Testing only after an IT product was developed is an outdated approach. Built-in quality from the start is needed to guarantee business value in today’s IT delivery models. Quality engineering is about changes in skills, organization, automation and quality measures.

Target Audience: All people involved in high-performance IT delivery teams
Prerequisites: General knowledge of IT delivery
Level: Advanced

Extended Abstract

To continuously deliver IT systems at speed with a focus on business value, high-performance cross-functional IT delivery teams integrate quality engineering in their way of working.

Quality engineering is the new concept in achieving the right quality of IT systems. Testing an application only after the digital product has been fully developed has long been a thing of the past. More is needed to guarantee the quality of applications that are delivered faster and more frequently in today’s high-performance IT delivery models. It is about achieving built-in quality. The road to quality engineering means changes in terms of starting points, skills, organization, automation and quality measures.

Our new VOICE model guides teams to align their activities with the business value that is pursued, and by measuring indicators, teams give the right information to stakeholders to establish their confidence that the IT delivery will actually result in business value for the customers.

Teams benefit from the clear definition of QA&Testing topics that are a useful grouping of all activities relevant to quality engineering. Organizing topics are relevant to align activities between teams and performing topics have a focus on the operational activities within a team.

Also, to be able to deliver quality at speed, for today’s teams it is crucial to benefit from automating activities, for example in a CI/CD pipeline, whereby people must remember that automation is not the goal but just a way to increase quality and speed.

In this presentation the audience will learn why a broad view on quality engineering is important and how quality engineering can be implemented to achieve the right quality of IT products, the IT delivery process and the people involved.

This presentation is based on our new book "Quality for DevOps teams" (ISBN 978-90-75414-89-9) which supports high-performance cross-functional teams in implementing quality in their DevOps culture, with practical examples, useful knowledge and some theoretical background.

In large software projects the assessment of the impact of a code change can be a cumbersome task. If the software has grown and shows an evolutionary design there are always unwanted side effects.

Change control boards are established. But on what data do they judge what can happen with the changes? Very often there is the HIPPO syndrome which means it is the highest paid person's opinion.

In this talk we will show you ways to come to a deterministic prediction of the impact, what data you need and what you can do with it.

Target Audience: Architects, Test Managers, Developers, Testers
Prerequisites: Basic knowledge of collected data in software projects
Level: Advanced

On-Call is an increasing reality for developers, especially when a site has strict uptime requirements. And sadly, the experience often sucks. It's easy to mandate 24x7 support, it's much harder to set it up in a way that doesn't make the life of the people in the rotation miserable.
I want to talk about improving alerting. I'm focusing on creating high-quality alerts that trigger when they should and don't trigger when nothing is happening. Continuous tuning, automation, and using the right metrics are core parts of this process.

Target Audience: Developers, Architects, DevOps, Operators
Prerequisites: Monitoring, operating production software
Level: Advanced

Extended Abstract
Do you believe in “you build it, you run it”? What if you have on-call rotations, where you are responsible 24x7 for the health of a system? Nothing is quite so infuriating as a collection of poorly structured alerts that trigger randomly.
So, let’s do better! I want to talk about how to improve your monitoring capabilities. There are a few topics I want to touch:

• Reduce the noise
• Automate as much as possible
• Build actionable triggers
• Tune your monitoring constantly

After this talk, you’ll have concrete actions to make your engineers’ life easier when on-call.

krankheitsbedingt ein kurzfristiger Wechsel

Content Management Systeme, Web-Browser oder Betriebssystem: Viele der Produkte und Services die wir täglich nutzen werden mittlerweile als Open Source Projekte realisiert. Durch den hohen Einfluss, den die Open Source Entwicklung mittlerweile auf die digitale Welt hat, findet man allerdings auch viele unterschiedliche Aussagen über dieGefahren und Vorteile von Open Source Produkten. Vor allem wenn man sich selber noch nicht intensiv mit der Thematik auseinander setzen konnte ist es hierdurch schwer, fachlich korrekte Bewertungen zu Open Source Produkten treffen zu können.

Basierend auf der Mitarbeit an verschiedenen großen Projekten in der Eclipse Foundation und des Java Ökosystems werde ich in diesem Vortrag nicht nur die theoretische Definition von Open Source vorstellen, sondern auch zeigen, wie Open Source Projekte in der Praxis entstehen und weiterentwickelt werden. Wir werden uns auch anschauen, warumOrganisationen Software als Open Source veröffentlichen und welche neuen und interessanten Geschäftsmodelle sich hierbei ergeben. Hierbei werden auch die Themen wie Lizenzen, Security und Support von Open Source Produkten angesprochen, welche durch Beispiele wie OpenSSL und den 2014 veröffentlichten Heartbleed-Bug konkretisiert werden.

Das im Vortrag vermittelte Wissen soll helfen, Open Source Software besser verstehen und einschätzen zu können. Mit diesem Fachwissen können die verschiedenen Gefahren und Vorteile, die durch die Nutzung von Open Source Komponenten entstehen, in Zukunft besser beurteilt werden.

The idea of looking at your organization as a single coherent system is tempting, but is it realistic? If it isn't, what does that mean for software developers, and how can we make discoverable what we are developing? This talk looks at organizations as ecosystems rather than as systems, and asks what that difference means for software development. It all boils down to focusing on software as components implementing business capabilities, and how to best capture these capabilities and make them findable and useful as reusable components.

Target Audience: Developers, Architects, Project Leaders, API Strategists
Prerequisites: API Basics, Large-scale information systems
Level: Advanced

Stories from a High Performing Team is a talk about the teamwork in a software development team at ThoughtWorks, a global Tech Consultancy. The team including the speakers - Jennifer (Developer), Xiaofan (Experience Designer) and Ursula (Business Analyst) - have been working for 14 month together which is a rare case in the consultancy business. The team is known for being high performing and today they want to share stories and practices for agile software development teams on how to reach this level.

Target Audience: Developers, Business Analysts, Architects, Project Managers, Delivery Principals
Prerequisites: Agile Mindset, Modern Softwaredevelopment understanding
Level: Advanced

If any person or groups of people feel unwelcome because of the language being used in a community, its products, or documentation, then the words should change. We can choose words that are precise, not dependent on metaphors, and convey messages without negative connotations.
We will discuss the process of auditing our own work and identifying divisive language. We will also talk about methods to standardize replacements and collaborate with writers and product developers to carry out these changes in a sustainable way.

Target Audience: Content creators (writers, developers, etc.) and management
Prerequisites: None
Level: Basic

Besides IoT and Machine2Machine communication Digital Twins are a cornerstone of the fourth industrial revolution. In general, a Digital Twin is the virtual replica of a physical object or system. But what does this mean in detail – what are the ingredients of a Digital Twin? How can Digital Twins be built and utilized and what value do they bring? This talk gives an overview of different types of Digital Twins, different applications from public to industrial utilization and architectural approaches how to create and execute them.

Target Audience: System Architects, product owners, software engineers
Prerequisites: None
Level: Basic

Due to the capabilities of Kubernetes, the usage of patterns rises to solve complex questions, but causing often confusion and unnecessary implementations. This talk intends to show what are the right scenarios for and for which cases another pattern is more suitable.
In this talk, Max will introduce you to various patterns, often misused by running applications and services within Kubernetes. The focus will be on structural patterns like Sidecars and Ambassadors as well as more advanced patterns like Controller and Operator.

Target Audience: Architects, DevOps Engineers, Platform Teams
Prerequisites: Good Understanding of Kubernetes
Level: Basic

Additional Information:
From this talk, you should take away in which scenario a pattern will suit most likely and how you can implement it. We will also look critically at the usage of these patterns.

Some codebases are nicer to work with than others. This is true for applications, services, libraries, frameworks, even programming languages themselves. Is this a purely personal choice or are there universal characteristics of software that can make code a joy to work with? Daniel has been thinking about this for a long time, especially since he poked a stick at the SOLID principles for fun a few years ago and people came after him with pitchforks.

Extended Abstract
His recent post about why he feels SOLID is outdated ended up on the front page of Hacker News! Now he has codified his thoughts into his own pithy five-letter acronym, CUPID: Composable, Unix philosophy, Predictable, Idiomatic, Domain-based. Why these characteristics, what do they mean, and why should you care? Can they improve your coding experience or is this just more programmer navel-gazing?

Are you wondering: How is a diary connected with leadership? How can YOU and OTHERS benefit from written reflection?
In this session you will get answers! You will benefit from my extensive (business) journaling experience. You will be introduced to psychological science that makes written self-reflection so powerful.

• You want to change habits in your life's "departments"?
• You want to harvest outstanding outcomes - at work and beyond?
• You want to spark change - in yourself and others?

Then join and get your leadership in ACTion!

Target Audience: All curious human beings (including Developers, Architects, Managers, Project Leads)
Prerequisites: Openness for new ways of thinking (and behaviour) is helpful
Level: Advanced

Extended Abstract
During my career in IT and people development I had several turning points where I either was made to use journaling techniques or experimented with them myself to successfully tackle the next challenge.

Over the years some turning points "beyond business" in life followed. Also I got serious scientific foundations in my psychological studies. Having both – the science and my experience – I started reflecting, why those 'written self-reflection' techniques are so powerful and – at the same time – they are still quite rarely used in the business context.

This session is suitable for all humans: curious newcomers as well as seasoned written-self-reflection experts as I'll share some stories, more than 10 years of experience and actionable tools and techniques.

Leaders of innovation, business and tech are experiencing an unprecedented demand to accelerate the pace of digital transformation. From board rooms to kindergarten classrooms, the unexpected upheaval triggered by the onset of the pandemic saw organizations make drastic changes. In this talk, Layla will share how we can learn from our transformations of past industrial revolutions, how shifts in human behavior help inform opportunities and how we can best consider interventions and take action.

Target Audience: Strategists, Product Owners, Designers, Technologists, Developers, Architects, Managers, - everyone
Prerequisites: None
Level: Advanced

Extended Abstract
Leaders of innovation, business and tech are experiencing an unprecedented demand to accelerate the pace of digital transformation. From board rooms to kindergarten classrooms, the unexpected upheaval triggered by the onset of the pandemic saw organizations make drastic changes. What for some was previously believed to be a process anticipating to take years, or met with resistance or incremental change, happened in months, weeks or even days.

We now have the amazing opportunity to shape our future rather than to react to it. Pandemic affects and evolving needs are converging to drive development towards innovative solutions. We need to build new capabilities towards helping organizations adopt new skills and shape new products and solutions – and simultaneously, we need to make different choices about where to focus efforts and initiatives. While no one can predict future moments of opportunity, or how technology will impact our lives on the short and long term, with certainty, we know opportunities will continue to come.

In this talk, Layla will share how we can learn from our transformations of past industrial revolutions, how shifts in human behavior help inform opportunities and how we can best consider interventions and take action.

Agile is becoming a standard delivery method adopted by organizations across the globe, according to VersionOne’s 11th Annual State of Agile Report. While 94 percent of survey respondents said their organizations practiced Agile, 80 percent said their organization was at or below a “still maturing” level. There are multiple reasons on why the Agile maturity of the teams are low, but the key one is teams look at Agile as a process change rather than a cultural change.
At Accenture we have been delivering solutions using Agile practices and principles and based on our experience we do face the challenges within the Agile teams such as the whole team’s limited experience with Agile, slowing down of work due to limited access to Product Owner, incomplete\less detailed user stories leading to high onshore dependency and struggling to keep momentum with continuous churn of Agile events through active participation and to maintain quality of artefacts (backlog, burndown, impediment list, retrospective action log etc.). These challenges manifold when delivery teams are practicing distributed Agile at scale. Apart from these challenges, at Accenture we are focused on how to make our teams more productive and ease the ways of working for the Agile teams.
In this presentation, we share our experiences in leveraging AI for Agile and the team feedback where these solutions were deployed. Did the AI in Agile help to address or mitigate the challenges it was introduced to address?  

The clean code principles are well-known in modern, agile software development. But what has become the default for our business code, unfortunately by no means applies to our infrastructure code. Instead, we find badly crafted, complicated and highly tangled code that is manually tested using a trial and error approach. However, for modern cloud based systems the infrastructure code plays a crucial role. So it's about time we begin to treat it as a 1st class citizen! This hands-on session shows how to craft clean infrastructure as code.

Target Audience: Architects, Developers, DevOps Engineers, SREs
Prerequisites: Basic knowledge of infrastructure as code practices and tools
Level: Advanced

Data technical debt refers to quality challenges associated with legacy data sources, including both mission-critical sources of record as well as “big data” sources of insight. Data technical debt impedes the ability of your organization to leverage information effectively for better decision making, increases operational costs, and impedes your ability to react to changes in your environment. The annual cost of bad data is in the trillions of dollars, this problem is real and it won't go away on its own.

Target Audience: Developers, Data Professionals, Managers, Architects
Prerequisites: Understanding of basic data terms
Level: Basic

Extended Abstract

Data technical debt refers to quality challenges associated with legacy data sources, including both mission-critical sources of record as well as “big data” sources of insight. Data technical debt impedes the ability of your organization to leverage information effectively for better decision making, increases operational costs, and impedes your ability to react to changes in your environment. Bad data is estimated to cost the United States $3 trillion annually alone, yet few organizations have a realistic strategy in place to address data technical debt.

This presentation defines what data technical debt is and why it is often a greater issue than classic code-based technical debt. We describe the types of data technical debt, why each is important, and how to measure them. Most importantly, this presentation works through Disciplined Agile (DA) strategies for avoiding, removing, and accepting data technical debt. Data is the lifeblood of our organizations, we need to ensure that it is clean if we’re to remain healthy.

Learning objectives:

• Discover what data technical debt is

• Understand the complexities of data technical debt and why they’re difficult to address

• Learn technical and management strategies to address data technical debt

Who drove your digital transformation? Your CEO? Or COVID-19? Across workplaces, markets and everyday habits, the pandemic transformed our world beyond our control. The way that we work, what we work on, even why we work were all transformed in ways that few organisational transformation programs ever achieved. Software played a key role in this transformation and, for better or for worse, it runs the world. We will explore the changes to the way we live that have moved from possibilities to realities and from opportunities to responsibilities.

Target Audience: Everyone interested in Digitalization
Prerequisites: None
Level: Advanced

Extended Abstract
Who drove your digital transformation? Your CEO? CTO? Or COVID-19? Across workplaces, markets and everyday habits, the pandemic transformed our world beyond our control. But for the parts we were able to control, software and technology played key roles. The way that we work, what we work on and even why we work were all transformed in ways that few organisational transformation programs ever achieved.

For better or for worse, software runs the world, and with great power comes great responsibility. Software has always been at the forefront of communication and distributed working, from the invention of the email to the current internet landscape, from social media to making socially distanced work a practical reality. Of course, it's not all good and things have not always turned out the way technologists expected. In this session we will explore the changes to the way we live that have moved from possibilities to realities and from opportunities to responsibilities.

Each project has its own unique technology stack, different business logic and a unique team. The definition of quality in our projects can vary greatly. However, there are good practices that will work everywhere. There are steps that can be taken in every project and team to produce the software of better quality. I will tell you how to improve communication and processes, and what tools we can use not to be ashamed of the fruits of our work. Everything from a programmer's perspective.

Target Audience: Developers and Tech/Project Leaders
Prerequisites: Some experience in profesional software development
Level: Advanced

Extended Abstract
Each project has its own unique technology stack, different business logic and a unique team. Some of us work on mature products that have been in production for many years. Others are constantly struggling to innovate in the race against time. The definition of quality in our projects can vary greatly. However, there are good practices that will work everywhere. There are steps that can be taken in every project and team to produce the software of better quality. I will tell you how to improve communication and processes, and what tools we can use not to be ashamed of the fruits of our work. Everything from a programmer's perspective.

“TDD is when you write tests before implementing the business logic” - a simple sentence that is also often misunderstood.
Moving from one project to another, I have observed how many times people were terrified of TDD. I have been there too.
This session will focus on trying to understand HOW and more importantly WHY you should consider TDD. I've transformed failures from my experience into a series of lessons learned, things that in hindsight should have been obvious.

Target Audience: Architects, Developers
Prerequisites: Basic knowledge in testing techniques
Level: Basic

In this talk, we will give an overview about all the different aspects that affect climate change from the software engineering perspective and discuss a number of concrete actions that every software engineer can take (and should keep in mind day-in day-out) to help fight climate change. During the talk, we will not only provide an overview of the landscape, but also cover topics in more depth and discuss the challenges that come with them.

Target Audience: Architects, Developers, Project Leads
Prerequisites: None
Level: Advanced

Extended Abstract
In this talk, we will give an overview about all the different aspects that affect climate change from the software engineering perspective and discuss a number of concrete actions that every software engineer can take (and should keep in mind day-in day-out) to help fight climate change, including:

• Energy consumption of software and what that means for software engineering
• Research studies about software running in data centers and the problem of zombies
• Work towards operating software in a carbon-aware way
• When and how far do renewable energies help
• How does carbon offsetting works and how to select the right projects
• And more...

In 2020, the three big cloud providers signed us all up for a revolution in the way we write and operate software. The deadline is 2030. Are you ready?

Target Audience: General techie. This works for all
Prerequisites: None
Level: Advanced

Extended Abstract
In 2020, Google Cloud, AWS, and Azure all committed to be carbon zero by 2030. It's the incredibly tough goal of zero emitted carbon as a result for operating our applications and services. They can't do it alone. AWS says "we optimize for sustainability of the cloud, while customers are responsible for sustainability in the cloud, meaning they must optimize their workloads and resource utilization." I don't think this is a request. They've signed up to be carbon zero by 2030. That means we have too. The clock is ticking.

Unfortunately, the session is cancelled without replacement.

With AI entering more and more aspects of our lives, scepticism and worries towards this technology are increasing too. Empathy towards basic human needs and a great User Experience can help AI being more widely accepted and used.
But how to get there?
After covering basic UX principles, the talk will deep dive into the fields of trust, transparency and explainable AI.
The goal is to outline a path to a fruitful collaboration and mutual understanding between humans and AI.

Target Audience: Software Engineers, Data Scientists, Product Owners, Researchers, Designers
Prerequisites: None
Level: Basic

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
Level: Advanced

Extended Abstract
"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.

I will introduce two AWS services: CodeGuru and DevOps Guru.
CodeGuru Reviewer uses ML and automated reasoning to automatically identify critical issues, security vulnerabilities, and hard-to-find bugs during application development.
DevOps Guru analyzes data like application metrics, logs, events, and traces to establish baseline operational behavior and then uses ML to detect anomalies. It does this by having the ability to correlate and group metrics together to understand the relationships between those metrics, so it knows when to alert.

Target Audience: Developers, Architects, Decision Makers
Prerequisites: Basic understanding of the code quality metrics and observability
Level: Basic

Extended Abstract
In this talk I will introduce two AWS services: CodeGuru and DevOps Guru.
Code reviews are one example and are important to improve software quality, software security, and increase knowledge transfer in the teams working with critical code bases. Amazon CodeGuru Reviewer uses ML and automated reasoning to automatically identify critical issues, security vulnerabilities, and hard-to-find bugs during application development. CodeGuru Reviewer also provides recommendations to developers on how to fix issues to improve code quality and dramatically reduce the time it takes to fix bugs before they reach customer-facing applications and result in a bad experience
Amazon DevOps Guru analyzes data like application metrics, logs, events, and traces to establish baseline operational behavior and then uses ML to detect anomalies. The service uses pre-trained ML models that are able to identify spikes in application requests. It does this by having the ability to correlate and group metrics together to understand the relationships between those metrics, so it knows when to alert and when not to.

Everyone wants to innovate, the question is how do you change your environment to support innovation?
Gabrielle will introduce the innovation imperative; why innovation is a necessity, a look at the disruptors threatening the fundamental ways we do business, and how to create a sustainable innovation strategy. 
We then go to the mean streets of Chelsea, London and meet Riccardo Mariti of Riccardo's restaurant. Riccardo will show you need to disrupt your business before you get disrupted and the importance of building continuous innovation into everything you do. Expect many stories and an interactive Q&A

This talk describes how to build and run a successful product development organization that delivers business value, not just features. I will cover what makes effective product development teams, how to structure, loosely couple, align and choreograph them, especially in larger organisations with up to 100 teams. Methods I will talk about include OKRs and Kanban Flight Levels. In this context I will also show when and how decentralised product teams can benefit from centralised platforms.

Target Audience: CTO, Manager, Decision Makers
Prerequisites: Experience with software development at scale
Level: Advanced

Within DDD we have the perspective of strategic design where we can split a large-system into multiple sub-domains, each having its purpose and responsibilities, where teams can work in autonomous, clean bounded contexts. One of the most effective ways to define these boundaries is by collaborative modelling with all the stakeholders involved in these domains. Join us were we share war stories about our experience doing collaborative modelling in several companies with 30+ people.

Target Audience: Architects, Manager, Decision Makers, Tech Leads
Prerequisites: None
Level: Advanced

Extended Abstract
As a business, we want to make sure our software can handle changes when the business changes. We want to define boundaries that support the flow of the business value. Within Domain-Driven Design we have the perspective of strategic design. A perspective where we can split a large-system into multiple sub-domains, each having its purpose and responsibilities. Within these sub-domains, teams can work in autonomous, clean bounded contexts. One of the most effective ways to define these boundaries is by collaborative modelling with all the stakeholders involved in these domains. But that poses real challenges: What exactly is the definition of a (sub)domain? What is problem space? How can we form a common language of these boundaries? How does a customer journey fit in? And how do you decide and come to a single model in a large group, where everyone shares that same model on a high level?
Join us in this talk where we will show and tell war stories about our experience of having done collaborative modelling in several companies. We will tell our successes, but more importantly our failures and what we learned from them. What are the key heuristics we think that makes a collaborative modelling session with 30+ people, without any DDD knowledge, succeed? What are the skills we need to learn to facilitate it, and how can we make a company not dependent on us as consultants to continue their journey? You will leave with the knowledge of how to start your own collaborative modelling of your domain boundaries. We tell you our definition of (sub)domains, problems and solution space, and how we explained it to the companies we consulted. Providing you with new perspectives on how to embed this as a ritual in your company.

For most people, AI means robots taking human jobs or China’s surveillance of its citizens. Despite the hype around it and its image of progress, the real workings of artificial intelligence are not widely understood. Companies are already implementing a web of algorithms to optimize manual business processes. Most of the time, the larger IT organization is not included on the journey. This talk is an overview of how IT leaders can center the development of human teams in a world that is increasingly optimized by algorithms.

When breaking up our software into modules we all too often forget the important social aspects; how the design affects the teams. We need modules that not only make us efficient but also harmonious.
We know that good fences make good neighbours, but only when the boundaries are placed correctly. We are going to take a closer look at why modularity is needed, what it actually can do for us, and how we can increase our chances of getting it right by taking a systems thinking approach.

Target Audience: Software Architects, Developers, Systems Designer
Prerequisites: None
Level: Expert

Extended Abstract
Modularity is a key aspect of software and architectural design, setting explicit boundaries between different parts of the system. But we have been banging on about this since the 70s, and still we are creating big balls of mud -- now even the distributed kind. Either modularity as a concept is insufficient or maybe there are aspects here we seem to get wrong. We know that good fences make good neighbours, but only when the boundaries are placed correctly. How can we create robust and sustainable modular designs when identifying those boundaries are so challenging?
In this talk, we are going to take a closer look at why modularity is needed, what it actually can do for us, and how we can increase our chances of getting it right by taking a systems thinking approach. The claim made is that a holistic view of the problem space is critical; one that considers all its parts, including the business and all the people affected. Software development today is inherently a sociotechnical endeavour and any modularisation effort, be it information hiding, SOA, microservices, DDD, Team Topologies and more, must take this into account in order to be able to create solutions that are sustainable and have the necessary conceptual integrity.
In summary, this talk will help you piece together all of the these good modularisation practices and understand the theory behind them, improving your holistic system design skills, and enabling you to create requisite coherence in your designs. Maybe this will guard you against the dreaded distributed big ball of mud, the killer of agility and productive collaboration.

Machine Learning appears to have made impressive progress on many tasks from image classification to autonomous vehicle control and more. ML has become so popular that its application, though often poorly understood and partially motivated by hype, is exploding. This is not necessarily a good thing. Systematic risk is invoked by adopting ML in a haphazard fashion. Understanding and categorizing security engineering risks introduced by ML at design level is critical. This talk focuses on results of an architectural risk analysis of ML systems.

Target Audience: Architects, Technical Leads, and Developers and Security Engineers of ML Systems
Prerequisites: Risk Managers, Software Security Professionals, ML Practitioners, everyone who is confronted by ML
Level: Advanced

Extended Abstract
Machine Learning appears to have made impressive progress on many tasks including image classification, machine translation, autonomous vehicle control, playing complex games including chess, Go, and Atari video games, and more. This has led to much breathless popular press coverage of Artificial Intelligence, and has elevated deep learning to an almost magical status in the eyes of the public. ML, especially of the deep learning sort, is not magic, however. ML has become so popular that its application, though often poorly understood and partially motivated by hype, is exploding. In my view, this is not necessarily a good thing. I am concerned with the systematic risk invoked by adopting ML in a haphazard fashion. Our research at the Berryville Institute of Machine Learning (BIIML) is focused on understanding and categorizing security engineering risks introduced by ML at the design level. Though the idea of addressing security risk in ML is not a new one, most previous work has focused on either particular attacks against running ML systems (a kind of dynamic analysis) or on operational security issues surrounding ML. This talk focuses on the results of an architectural risk analysis (sometimes called a threat model) of ML systems in general. A list of the top five (of 78 known) ML security risks will be presented.

The primary cause of technical debt in your organization is very likely your project managers – not your programmers nor your architects. In this keynote Scott Ambler explores the root causes of technical debt within organizations, many of which trace back to the project management (PM) mindset and the strategies that result from it. Scott works through how to make leadership aware of technical debt and its implications, how to evolve your management practices, and strategies to embed technical debt thinking and behaviors into your culture.

Target Audience: Developers, Architects, Leaders, Managers
Prerequisites: None
Level: Advanced

Extended Abstract
The primary cause of technical debt in your organization is very likely your project managers – not your programmers nor your architects. The management desire to be “on time and on budget”  often motivates deployment of poor-quality assets and rarely leaves room for investment in long-term quality. Although technical professionals may readily realize this problem managers often do not, or if they do they don’t view technical debt as a priority. It is time for a change.
In this keynote Scott Ambler explores the root causes of technical debt within organizations, many of which trace back to the project management (PM) mindset and the strategies that result from it. Just like the technical challenges of addressing technical debt must be addressed by technical solutions, the management challenges of technical debt must be addressed by management solutions. Scott works through how to make leadership aware of technical debt and its implications, how to evolve your management practices to avoid and address technical debt, and enterprise-level strategies to embed technical debt thinking and behaviors into your culture. Results from industry research will be shared throughout.
Learning objectives:
• Connect project management practices to their impact on technical debt
• Learn how to describe technical debt, its impact, and solutions to leadership
• Discover how to embed technical debt thinking and practices throughout your way of working (WoW)

Unfortunately, the session is cancelled without replacement.

We live in an uncertain world that seems to shift and transform by the second. How can our software teams ever be effective when the ground is shifting below their feet?

While the discomfort of uncertainty and chaos may well make us feel uncomfortable, even fearful. It's precisely where the value in most of our projects lies.

In this session we'll explore how to embrace uncertainty and deliver the right things at the right time. Even when it seems hard to pin down what the right thing is and when it's needed!

Target Audience: Agile Coaches, Product Managers, Product Owners, Project Managers
Prerequisites: Some experience with the application of agility to a team or organisation.
Level: Advanced

Extended Abstract
We liv in an uncertain world that seems to shift and transform by the second. How can our software teams ever be effective when the ground is shifting below their feet?

While the discomfort of uncertainty and chaos may well make us feel uncomfortable, even fearful. It's precisely where the value in most of our projects lies.

In this session we'll explore how to embrace uncertainty and deliver the right things at the right time. Even when it seems hard to pin down what the right thing is and when it's needed!

• How to make your work board (virtual or real) a tool to support group problem solving and collaboration.
• How to use story mapping to plan work and understand the level of uncertainty.
• How to use projections to help with prioritisation and planning.
• Why having a language to discuss uncertainty is so important.
• This tutorial is for anyone wanting to better prioritise their teams' work, respond effectively to an ever changing environment and deliver value.