[ { "date": "2023-10-04T00:00:00", "isDefault": false, "rooms": [ { "id": 34039, "name": "Room 1", "sessions": [ { "id": "866946fe-9feb-4f7e-84b1-3963c7cbf479", "title": "Opening Ceremony", "description": null, "startsAt": "2023-10-04T09:00:00", "endsAt": "2023-10-04T09:20:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "473271", "title": "Metaphors We Code By", "description": "The world in which a software system lives is filled with meaning. The very act of development is an exercise in meaning — its discovery, its formulation, its communication. Domain-driven design makes this first class.\r\n\r\nThe abstract nature of software and its development leads to the extensive use of metaphors to confer meaning on the classes, functions, UI elements, relationships, patterns, etc., of our systems, as well as the mental models we hold about them and reason through.\r\n\r\nBut just because we are immersed in metaphor and meaning from an early age, and just because the daily work of software development employs metaphor and wrangles meaning, that doesn't mean we're necessarily good at it. Let's talk about the whats, whys and hows of metaphor, communication, naming and thinking.", "startsAt": "2023-10-04T09:20:00", "endsAt": "2023-10-04T10:10:00", "isServiceSession": false, "isPlenumSession": true, "speakers": [ { "id": "bc20c5a9-2d7e-4830-827f-8919be0eba88", "name": "Kevlin Henney" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "a6c3dc11-5ce0-4b76-b1f5-ab7f4d14a54c", "title": "20 min break", "description": null, "startsAt": "2023-10-04T10:10:00", "endsAt": "2023-10-04T10:30:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "473268", "title": "Multiple Models with Multiple Perspectives in a Cross-Functional Team - Case Study from Healthcare", "description": "In many cross-functional teams we encounter communication challenges between different roles in the team. Making domain experts, designers, testers, developers and tech leads align on the shared understanding is not an easy task. This is mainly due to different perspectives that each team member brings to the table, each perspective being a valid one however not adequate on its own. The different perspectives are particularly visible when reasoning about different approaches to the decomposition of the domain problem at hand which leads to different perceptions of subdomains and bounded contexts.\r\n\r\nIn this case study we will go through different models of domain problem decomposition that helped align the perspectives in a cross-functional team in the healthcare domain. We will go through functional, role-based, user-context based and business capability based decomposition along with pros and cons of each approach, backed up by the feedback provided by the impact each approach had on the data ownership in resulting bounded contexts.\r\n\r\nWe will wrap-up with the reasoning behind the choice the team actually made and how it played out in structuring the code base, delivering value to their customers, and how it impacted the different roles in the team.\r\n", "startsAt": "2023-10-04T10:30:00", "endsAt": "2023-10-04T11:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "c357c7b1-c328-43fd-86de-9006aac0600d", "name": "Mufrid Krilic" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "ee1b44bf-e5f5-4796-9d58-c4ec834aac0d", "title": "20 min break", "description": null, "startsAt": "2023-10-04T11:20:00", "endsAt": "2023-10-04T11:40:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "460381", "title": "Collaborative Software Design: How to facilitate domain modeling decisions", "description": "Designing a software system is difficult. Understanding the context in which a software system lives is more difficult. In order to understand that context, developers need to communicate with the business. But there is a lot that can go wrong while communicating with the business. For example people can misunderstand what is being said, they are scared to speak up, tensions could grow, and conflict can arise. These social dynamics cause groups to stop sharing their knowledge, which can end up in resistance behaviour from sarcastic jokes, to stopped communication or even not showing up or leaving the session. No wonder a lot of organisations resort to a more autocratic form of decision-making, where one person, the architect, analyses and makes the decision. If we want to make sustainable design decisions for our architecture that is embraced by everyone, it is better to use visual techniques to make assumptions more explicit which will improve collaboration between developer teams and the domain experts.\r\n\r\nIn this talk we will introduce you to collaborative modelling and its social dynamic challenges. Collaborative modelling is a visualisation technique to analyse complex and conflict-laden decision-making processes with all relevant stakeholders and decision-makers to create a shared understanding. And some, maybe even most of these sessions need to be facilitated so that everyone can feel a part of the decision and can potentially give the input they have. I will explain why it requires us to have a different skills set like observing, listening, trying to stay neutral and show compassion. Because that improved collaboration will let software teams understand better the context and underlying problems the business has. That understanding enables the software teams to design and build sustainable quality software products.", "startsAt": "2023-10-04T11:40:00", "endsAt": "2023-10-04T12:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "cc81eb7f-48a8-41cf-ad56-2119ea13bf2f", "name": "Kenny (Baas) Schwegler" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "ab2232c0-4165-4390-9b2b-111ff9d4fc37", "title": "Lunch", "description": null, "startsAt": "2023-10-04T12:30:00", "endsAt": "2023-10-04T13:30:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "469055", "title": "Fluid teams - stories from the trenches", "description": "At Vinted we've been experimenting with fluid teams for over a year. In this talk, I'd like to share the motivation for taking this direction, observations, and insights collected from the experience.", "startsAt": "2023-10-04T13:30:00", "endsAt": "2023-10-04T14:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "d2565dd1-9e7f-4673-b892-9ff6f2a7c08d", "name": "Ornela Vasiliauskaitė" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "b1b13c8d-c394-4793-887b-01c5ad26130a", "title": "20 min break", "description": null, "startsAt": "2023-10-04T14:20:00", "endsAt": "2023-10-04T14:40:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "550801", "title": "The Mario Kart™ guide to building a career", "description": "Mario Kart™ teaches us a lot of things: how to take shortcuts, how to stab your friends in the back, and most of all: how to get to the front of the pack. But have you ever stopped to wonder what lessons you can learn from it when it comes to planning for your own success?\r\n\r\nPersonally, I've had to overcome some obstacles to get to where I am today. And the things I have learned for myself, I have also applied as a coach at Axxes, where I have been involved in a lot of careers besides my own. Seeing other people grow has always been a key motivator for me in my role.\r\n\r\nA sure-fire road to success might not exist, but there are numerous lessons I've learned from doing this over the years. Those tips have been helpful to a lot of people, and I'll gladly share them with you.\r\n\r\nIn this session, I'll dive into building a career head-first. We'll use Mario Kart™ as a guideline and there will be anecdotes from my personal experience as a developer, a consultant and a coach. You'll walk away with some new ideas on how to handle your own career.", "startsAt": "2023-10-04T14:40:00", "endsAt": "2023-10-04T15:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "497f9bfb-7e28-4773-81e3-e853ca09ccde", "name": "Hannes Lowette" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "1251ca06-4fda-4407-9be3-9aff27550c9f", "title": "20 min break", "description": null, "startsAt": "2023-10-04T15:30:00", "endsAt": "2023-10-04T15:50:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "459148", "title": "Making a Difference by Making Sense", "description": "In the early 1970s, professor Niklas Luhmann was given a monumental task: To formulate nothing less than a comprehensive sociological theory of society - as a whole, and for all of its major functional subsystems, such as the law, mass media, arts, etc. - within 30 years. \r\nLeaning on prior systems theories, he developed a unique take on what makes human society special: Not psychology, not individual humans, but what's in between them - communication! And that this communication has a dual form; it makes a difference by making sense: It carries within itself both the information of what is part of the system (included) and what is not (excluded), thereby defining and reinforcing the system boundary. \r\nOver the course of 15 years, Luhmann developed this framework into the \"Theory of Social Systems\", a revolutionary way of understanding the fabric and operations of how these systems appear, stabilize, evolve and differentiate, and of the structural couplings that tie them to their environment. It would help him to finish his work in time, and publish \"The Society of Society\" in 1997, a year before he died.\r\n25 years after Luhmann's death, we as a community have established our own ways to analyze, model and support the socio-technical systems of modern society, outside of the realm of sociology. But our ways still align remarkably with his work: In the way we use language to find system (domain!) boundaries. In how we use maps and adapters to manifest structural coupling between different contexts. In how teams and organizations are doomed to recreate the structure of their communication. And in how a system that is not used and evolved will fade, and cease to exist.\r\nIf \"culture is the ultimate context\" (Avraham Poupko), then society is the ultimate system. And the domains we observe and model are the residue of (sub)system operations. \r\nLet's explore what that means.\r\n \r\n", "startsAt": "2023-10-04T15:50:00", "endsAt": "2023-10-04T16:40:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "e75b7ec8-9d5e-494e-9047-c84094414e45", "name": "Tobias Goeschel" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "4783dfa5-a300-43bb-8bc1-ebb4ecbeb7bb", "title": "20 min break", "description": null, "startsAt": "2023-10-04T16:40:00", "endsAt": "2023-10-04T17:00:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "472958", "title": "Human centred system design", "description": "IT is driven by STEM culture and its technical imperative, enabling the creation of technically advanced products. The issue though is that software development is inherently a sociotechnical enterprise. And the social aspects of it are often undervalued, even overlooked. We write software with people for people and sustainable solutions for both us and the users can only be reached by jointly optimise the technical and the social.\r\n\r\nIn this talk we will explore an approach from social sciences called Open Systems Theory. By looking at the milestones that led to this conceptual framework, like replacing the machine view the world, discovering group dynamics, realising that individuals only grow in groups, defining people as open purposeful systems, democratisation of work, discovering the genotypical organisational design principles, and understanding how critical participative design is to lasting and sustainable solutions. \r\n\r\nThe goal is to show that this approach will not only helps us create a learning organisation where people thrive and technology operates closer to its potential, but also one that performs better in an increasingly complex and competitive environment.", "startsAt": "2023-10-04T17:00:00", "endsAt": "2023-10-04T17:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "40a5fba3-0c7b-487c-9dc9-9d836a8ca999", "name": "Trond Hjorteland" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "932e078e-2a70-4a44-8569-0d54c6d9dbe7", "title": "Evening reception until midnight", "description": "We will be socialising until midnight at the venue. Hannes 'Ceasar' Lowette will be your host for the night and guide you through the rites of passage from powerpoint karaoke in ancient rome to the costume contest. Unwind, relax and don't feed the lions!", "startsAt": "2023-10-04T18:00:00", "endsAt": "2023-10-04T18:50:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false } ], "hasOnlyPlenumSessions": false }, { "id": 34040, "name": "Room 2", "sessions": [ { "id": "458747", "title": "Beyond producers and consumers: Avoiding common issues with event-driven architectures", "description": "Scaling event-driven architectures can be challenging and many companies struggle with schemas, discoverability, and best practices. However, with the right approach, it is possible to overcome these challenges and establish a solid foundation for your event-driven architecture growth within your organizations.\r\n\r\nThis talk will explore the advantages of event-driven architectures and common obstacles associated with their natural growth within organizations. It will provide you with a range of patterns, examples, and resources that will empower you to prepare for and conquer these challenges.\r\n\r\nFollowing this talk, you will be equipped with patterns and resources to help your teams scale and construct event-driven architectures within your organization.", "startsAt": "2023-10-04T10:30:00", "endsAt": "2023-10-04T11:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "19d533a1-5282-4ef5-9ec2-73d3ca829b16", "name": "David Boyne" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "65026289-989e-46e7-8e8d-0c633d5e8e5f", "title": "20 min break", "description": null, "startsAt": "2023-10-04T11:20:00", "endsAt": "2023-10-04T11:40:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "451286", "title": "The Aggregate is dead. Long live the Aggregate!", "description": "DDD's definition of Aggregate may seem somewhat confusing - \"An aggregate is a cluster of associated objects that we treat as a unit for the purpose of data changes.\" Okay, let's try to clarify - \"You should consider your aggregate as a unit of consistency in your Domain.\". That doesn't help either. \r\n\tAs a matter of fact, while modeling our systems, we tend to group together events related to the same domain concept; we tend to define groups based on the nouns we find inside our events’ name: saying \"this is our aggregate!\". \r\nAccording to the aggregate definition, we should instead ignore these nouns, and put together the data that change together. \r\nEasier said than done: in the modeling phase it is easy to make mistakes trying to identify the boundaries of our aggregates based on this rule.\r\nIf we opt for saving the state of our aggregate as a series of events, we are in big trouble - any (serious) refactoring of the aggregate structure becomes close to impossible. The reason for this trouble is that we have to make a decision in the design phase for which we cannot be lenient. We are basically married to this decision forever.\r\n\tDue to the aforementioned reasons (and many others), people struggle with the Aggregate pattern. Some even say it is unnecessary, we are one of those. Let's see whether we can model our business constraints without aggregates. Could we be more relaxed when consistency is in question? Join us to discover how!", "startsAt": "2023-10-04T11:40:00", "endsAt": "2023-10-04T12:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "687f3ff7-4cc5-4659-8480-c8ec8dcb535b", "name": "Sara Pellegrini" }, { "id": "76b24e20-e060-4239-a554-129c2d6ab26f", "name": "Milan Savić" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "473620", "title": "Domain-Driven Refactoring", "description": "Books, workshops, storming and more, all build up an idealized domain model. All describe great techniques for domain-driven greenfield applications. But what about the code we have? How can we take what's already built, and move it towards a better, more cohesive design?\r\n\r\nIn this session, we'll look at anemic, procedural, boring code and examine code smells that can point us in the right direction. We'll also look at standard design patterns for more complex behaviors and models, and how to recognize when (and when not) to apply them. Finally, we'll cover how to safely apply refactoring techniques to achieve our domain-driven model nirvana.", "startsAt": "2023-10-04T13:30:00", "endsAt": "2023-10-04T14:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "f109dd0b-9441-4cbf-8664-19c021a6de4a", "name": "Jimmy Bogard" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "18ccaaec-93ff-4e2a-8f43-494e1b8ee39b", "title": "20 min break", "description": null, "startsAt": "2023-10-04T14:20:00", "endsAt": "2023-10-04T14:40:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "478480", "title": "Hedy: A gradual and multi-lingual programming language for education", "description": "When kids learn to program they often use either a visual language like Scratch, or a textual language like Python. While visual languages are great for the first steps, children and educators often want to move on to a textual language. However early on, a textual language and its error messages can be scary and frustrating.\r\n\r\nHedy aims to bridge this gap with a programming language that is gradual, using different language levels. In level 1, there is hardly any syntax at all; printing is done with: print hello! At every level, new syntax and concepts are added, so learners do not have to master everything at once. Hedy builds up to a subset of Python including conditions, loops, variables and lists.\r\n\r\nTo make learning as accessible as possible, Hedy allows for the use of localized keywords, f.e in Spanish:\r\n\r\nimprimir Hello!\r\n\r\nThis talk will discuss the pedagogy of Hedy as well as its technical aspects, since a set of changing and localized complex grammars poses several interesting challenges for parsing, and a small language offers a lot of potential from improved error messages.", "startsAt": "2023-10-04T14:40:00", "endsAt": "2023-10-04T15:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "b47c3560-95dc-43ed-b956-855af7e313d6", "name": "Mark Giesen" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "461471", "title": "Riding the elevator: DDD in the penthouse", "description": "In his book \"The Software Architect Elevator\" Gregor Hohpe uses the analogy of an elevator in a high building for the daily work which software architects should be doing: They are supposed to talk to folks who build and maintain stuff in the engine room but also make sure that the managment which is residing on the penthouse floors understand and gain interest in what is happening in the engine room.\r\n\r\nIn my talk I will build upon Gregors ideas and show you how you can leverage ideas from Domain Driven Design in this daunting communication tasks. But rest assured: I will not only present the obvious strategic Domain Drivend Design elements like core / supporting / generic subdomains here. We will go deeper and explore links to other initiatives in an org like DevOps, Agile and / org Design Thinking as well which are of interest for the leadership of an organization.\r\n\r\nWe as a community should get better at this topic because Domain Driven Design needs a healthy, blame free and safe environment in order to flourish and this environment needs to be established and lived by the leadership folks. \r\n\r\nPS: The talk idea and usage of Gregors elevator analogy have been approved by Gregor", "startsAt": "2023-10-04T15:50:00", "endsAt": "2023-10-04T16:40:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "c41a4363-aedb-42e0-8495-86be6c23107d", "name": "Michael Plöd" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "c75589e0-c62c-4405-9ba1-423d6d240905", "title": "20 min break", "description": null, "startsAt": "2023-10-04T16:40:00", "endsAt": "2023-10-04T17:00:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "471486", "title": "Journey to implement DDD into an organization", "description": "Top-down organizational journey to implement DDD, during the talk we will look at different decisions levels like, structural, technical, process and persons, because a change needs the enforcement of the organization to happen", "startsAt": "2023-10-04T17:00:00", "endsAt": "2023-10-04T17:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "57ac7058-1fcf-4d9a-802c-73b297e824b0", "name": "Javiera Laso" }, { "id": "846d57fa-0c0a-463c-97c8-31fb9fec084a", "name": "Octavio Valenzuela" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true } ], "hasOnlyPlenumSessions": false }, { "id": 34041, "name": "Room 3", "sessions": [ { "id": "458420", "title": "Tools for Systems Thinking", "description": "There are many digital tools to support linear coordination of software delivery. Jira, for example. But what do we do as complexity increases? What tools support the process of reasoning about something, forming new ideas or concepts? How do we develop a collection of tools that support our creative thinking process? How do we use those tools to think well, together?\r\n\r\nIn this workshop, Diana and Dawn will share their divergent toolset and processes for systems thinking. Then guide attendees towards building their toolkit:\r\n\r\n- Identify my primary thinking (alone and together) activities\r\n- Survey the tools I use now and why.\r\n- Design a better system of inter-related tools to support my thinking.\r\n- Consider an improve workflow in my day-to-day focused thinking delivery process.", "startsAt": "2023-10-04T10:30:00", "endsAt": "2023-10-04T12:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "ffc04f2e-579f-4653-8dad-5779557fd386", "name": "Diana Montalion" }, { "id": "d319c4a1-b8e9-4db3-b7ad-119da2795600", "name": "Dawn Ahukanna" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "492712", "title": "Why does it always go worse than planned? - A Workshop on Ergodicity and Knowledge Workers", "description": "Have you ever noticed that things often seem to go worse than planned, especially regarding complex work tasks? This workshop aims to shed light on the underlying dynamics contributing to this phenomenon and introduces the concept of ergodicity as a key explanatory framework.\r\n\r\nThrough a combination of lecture, discussion, and a hands-on game, participants will learn about the principles of ergodicity and how it relates to how we organize our work. Inspired by Eliyahu Goldratt's book \"The Goal,\" the game will challenge participants to think about how their work processes may unintentionally create bad luck and variability.\r\n\r\nAttendees will leave the workshop with a deeper understanding of ergodicity and how it applies to their work, as well as practical strategies for improving their productivity and reducing the negative impact of variability. Whether you're a knowledge worker looking to enhance your skills or a manager seeking to optimize your team's performance, this workshop offers valuable insights and tools to help you achieve better outcomes.", "startsAt": "2023-10-04T13:30:00", "endsAt": "2023-10-04T15:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "f60639ab-a066-43d3-b187-3a125a82b363", "name": "Jacopo Romei" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "483920", "title": "Let's unFIX organisations! How to use patterns to design your own agile framework.", "description": "Imagine a card set to playfully explore organisational design. A card set which can be used like Lego bricks, to build an individual agile framework serving the needs of your organisation. With unFIX this becomes reality! \r\nLet's discover together the new work from Jurgen Appelo (author \"Management 3.0\") and his unFIX team around organisational patterns to create workplaces for continuous innovation and better human experience.", "startsAt": "2023-10-04T15:50:00", "endsAt": "2023-10-04T17:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "acd98ad8-ebf2-4211-9762-38f88777b8e4", "name": "Tina Dreisicke" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true } ], "hasOnlyPlenumSessions": false } ], "timeSlots": [ { "slotStart": "09:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "866946fe-9feb-4f7e-84b1-3963c7cbf479", "title": "Opening Ceremony", "description": null, "startsAt": "2023-10-04T09:00:00", "endsAt": "2023-10-04T09:20:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "09:20:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "473271", "title": "Metaphors We Code By", "description": "The world in which a software system lives is filled with meaning. The very act of development is an exercise in meaning — its discovery, its formulation, its communication. Domain-driven design makes this first class.\r\n\r\nThe abstract nature of software and its development leads to the extensive use of metaphors to confer meaning on the classes, functions, UI elements, relationships, patterns, etc., of our systems, as well as the mental models we hold about them and reason through.\r\n\r\nBut just because we are immersed in metaphor and meaning from an early age, and just because the daily work of software development employs metaphor and wrangles meaning, that doesn't mean we're necessarily good at it. Let's talk about the whats, whys and hows of metaphor, communication, naming and thinking.", "startsAt": "2023-10-04T09:20:00", "endsAt": "2023-10-04T10:10:00", "isServiceSession": false, "isPlenumSession": true, "speakers": [ { "id": "bc20c5a9-2d7e-4830-827f-8919be0eba88", "name": "Kevlin Henney" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 } ] }, { "slotStart": "10:10:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "a6c3dc11-5ce0-4b76-b1f5-ab7f4d14a54c", "title": "20 min break", "description": null, "startsAt": "2023-10-04T10:10:00", "endsAt": "2023-10-04T10:30:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "10:30:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "473268", "title": "Multiple Models with Multiple Perspectives in a Cross-Functional Team - Case Study from Healthcare", "description": "In many cross-functional teams we encounter communication challenges between different roles in the team. Making domain experts, designers, testers, developers and tech leads align on the shared understanding is not an easy task. This is mainly due to different perspectives that each team member brings to the table, each perspective being a valid one however not adequate on its own. The different perspectives are particularly visible when reasoning about different approaches to the decomposition of the domain problem at hand which leads to different perceptions of subdomains and bounded contexts.\r\n\r\nIn this case study we will go through different models of domain problem decomposition that helped align the perspectives in a cross-functional team in the healthcare domain. We will go through functional, role-based, user-context based and business capability based decomposition along with pros and cons of each approach, backed up by the feedback provided by the impact each approach had on the data ownership in resulting bounded contexts.\r\n\r\nWe will wrap-up with the reasoning behind the choice the team actually made and how it played out in structuring the code base, delivering value to their customers, and how it impacted the different roles in the team.\r\n", "startsAt": "2023-10-04T10:30:00", "endsAt": "2023-10-04T11:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "c357c7b1-c328-43fd-86de-9006aac0600d", "name": "Mufrid Krilic" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "458747", "title": "Beyond producers and consumers: Avoiding common issues with event-driven architectures", "description": "Scaling event-driven architectures can be challenging and many companies struggle with schemas, discoverability, and best practices. However, with the right approach, it is possible to overcome these challenges and establish a solid foundation for your event-driven architecture growth within your organizations.\r\n\r\nThis talk will explore the advantages of event-driven architectures and common obstacles associated with their natural growth within organizations. It will provide you with a range of patterns, examples, and resources that will empower you to prepare for and conquer these challenges.\r\n\r\nFollowing this talk, you will be equipped with patterns and resources to help your teams scale and construct event-driven architectures within your organization.", "startsAt": "2023-10-04T10:30:00", "endsAt": "2023-10-04T11:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "19d533a1-5282-4ef5-9ec2-73d3ca829b16", "name": "David Boyne" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 }, { "id": 34041, "name": "Room 3", "session": { "id": "458420", "title": "Tools for Systems Thinking", "description": "There are many digital tools to support linear coordination of software delivery. Jira, for example. But what do we do as complexity increases? What tools support the process of reasoning about something, forming new ideas or concepts? How do we develop a collection of tools that support our creative thinking process? How do we use those tools to think well, together?\r\n\r\nIn this workshop, Diana and Dawn will share their divergent toolset and processes for systems thinking. Then guide attendees towards building their toolkit:\r\n\r\n- Identify my primary thinking (alone and together) activities\r\n- Survey the tools I use now and why.\r\n- Design a better system of inter-related tools to support my thinking.\r\n- Consider an improve workflow in my day-to-day focused thinking delivery process.", "startsAt": "2023-10-04T10:30:00", "endsAt": "2023-10-04T12:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "ffc04f2e-579f-4653-8dad-5779557fd386", "name": "Diana Montalion" }, { "id": "d319c4a1-b8e9-4db3-b7ad-119da2795600", "name": "Dawn Ahukanna" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 2 } ] }, { "slotStart": "11:20:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "ee1b44bf-e5f5-4796-9d58-c4ec834aac0d", "title": "20 min break", "description": null, "startsAt": "2023-10-04T11:20:00", "endsAt": "2023-10-04T11:40:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "65026289-989e-46e7-8e8d-0c633d5e8e5f", "title": "20 min break", "description": null, "startsAt": "2023-10-04T11:20:00", "endsAt": "2023-10-04T11:40:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 1 } ] }, { "slotStart": "11:40:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "460381", "title": "Collaborative Software Design: How to facilitate domain modeling decisions", "description": "Designing a software system is difficult. Understanding the context in which a software system lives is more difficult. In order to understand that context, developers need to communicate with the business. But there is a lot that can go wrong while communicating with the business. For example people can misunderstand what is being said, they are scared to speak up, tensions could grow, and conflict can arise. These social dynamics cause groups to stop sharing their knowledge, which can end up in resistance behaviour from sarcastic jokes, to stopped communication or even not showing up or leaving the session. No wonder a lot of organisations resort to a more autocratic form of decision-making, where one person, the architect, analyses and makes the decision. If we want to make sustainable design decisions for our architecture that is embraced by everyone, it is better to use visual techniques to make assumptions more explicit which will improve collaboration between developer teams and the domain experts.\r\n\r\nIn this talk we will introduce you to collaborative modelling and its social dynamic challenges. Collaborative modelling is a visualisation technique to analyse complex and conflict-laden decision-making processes with all relevant stakeholders and decision-makers to create a shared understanding. And some, maybe even most of these sessions need to be facilitated so that everyone can feel a part of the decision and can potentially give the input they have. I will explain why it requires us to have a different skills set like observing, listening, trying to stay neutral and show compassion. Because that improved collaboration will let software teams understand better the context and underlying problems the business has. That understanding enables the software teams to design and build sustainable quality software products.", "startsAt": "2023-10-04T11:40:00", "endsAt": "2023-10-04T12:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "cc81eb7f-48a8-41cf-ad56-2119ea13bf2f", "name": "Kenny (Baas) Schwegler" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "451286", "title": "The Aggregate is dead. Long live the Aggregate!", "description": "DDD's definition of Aggregate may seem somewhat confusing - \"An aggregate is a cluster of associated objects that we treat as a unit for the purpose of data changes.\" Okay, let's try to clarify - \"You should consider your aggregate as a unit of consistency in your Domain.\". That doesn't help either. \r\n\tAs a matter of fact, while modeling our systems, we tend to group together events related to the same domain concept; we tend to define groups based on the nouns we find inside our events’ name: saying \"this is our aggregate!\". \r\nAccording to the aggregate definition, we should instead ignore these nouns, and put together the data that change together. \r\nEasier said than done: in the modeling phase it is easy to make mistakes trying to identify the boundaries of our aggregates based on this rule.\r\nIf we opt for saving the state of our aggregate as a series of events, we are in big trouble - any (serious) refactoring of the aggregate structure becomes close to impossible. The reason for this trouble is that we have to make a decision in the design phase for which we cannot be lenient. We are basically married to this decision forever.\r\n\tDue to the aforementioned reasons (and many others), people struggle with the Aggregate pattern. Some even say it is unnecessary, we are one of those. Let's see whether we can model our business constraints without aggregates. Could we be more relaxed when consistency is in question? Join us to discover how!", "startsAt": "2023-10-04T11:40:00", "endsAt": "2023-10-04T12:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "687f3ff7-4cc5-4659-8480-c8ec8dcb535b", "name": "Sara Pellegrini" }, { "id": "76b24e20-e060-4239-a554-129c2d6ab26f", "name": "Milan Savić" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 } ] }, { "slotStart": "12:30:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "ab2232c0-4165-4390-9b2b-111ff9d4fc37", "title": "Lunch", "description": null, "startsAt": "2023-10-04T12:30:00", "endsAt": "2023-10-04T13:30:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "13:30:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "469055", "title": "Fluid teams - stories from the trenches", "description": "At Vinted we've been experimenting with fluid teams for over a year. In this talk, I'd like to share the motivation for taking this direction, observations, and insights collected from the experience.", "startsAt": "2023-10-04T13:30:00", "endsAt": "2023-10-04T14:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "d2565dd1-9e7f-4673-b892-9ff6f2a7c08d", "name": "Ornela Vasiliauskaitė" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "473620", "title": "Domain-Driven Refactoring", "description": "Books, workshops, storming and more, all build up an idealized domain model. All describe great techniques for domain-driven greenfield applications. But what about the code we have? How can we take what's already built, and move it towards a better, more cohesive design?\r\n\r\nIn this session, we'll look at anemic, procedural, boring code and examine code smells that can point us in the right direction. We'll also look at standard design patterns for more complex behaviors and models, and how to recognize when (and when not) to apply them. Finally, we'll cover how to safely apply refactoring techniques to achieve our domain-driven model nirvana.", "startsAt": "2023-10-04T13:30:00", "endsAt": "2023-10-04T14:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "f109dd0b-9441-4cbf-8664-19c021a6de4a", "name": "Jimmy Bogard" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 }, { "id": 34041, "name": "Room 3", "session": { "id": "492712", "title": "Why does it always go worse than planned? - A Workshop on Ergodicity and Knowledge Workers", "description": "Have you ever noticed that things often seem to go worse than planned, especially regarding complex work tasks? This workshop aims to shed light on the underlying dynamics contributing to this phenomenon and introduces the concept of ergodicity as a key explanatory framework.\r\n\r\nThrough a combination of lecture, discussion, and a hands-on game, participants will learn about the principles of ergodicity and how it relates to how we organize our work. Inspired by Eliyahu Goldratt's book \"The Goal,\" the game will challenge participants to think about how their work processes may unintentionally create bad luck and variability.\r\n\r\nAttendees will leave the workshop with a deeper understanding of ergodicity and how it applies to their work, as well as practical strategies for improving their productivity and reducing the negative impact of variability. Whether you're a knowledge worker looking to enhance your skills or a manager seeking to optimize your team's performance, this workshop offers valuable insights and tools to help you achieve better outcomes.", "startsAt": "2023-10-04T13:30:00", "endsAt": "2023-10-04T15:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "f60639ab-a066-43d3-b187-3a125a82b363", "name": "Jacopo Romei" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 2 } ] }, { "slotStart": "14:20:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "b1b13c8d-c394-4793-887b-01c5ad26130a", "title": "20 min break", "description": null, "startsAt": "2023-10-04T14:20:00", "endsAt": "2023-10-04T14:40:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "18ccaaec-93ff-4e2a-8f43-494e1b8ee39b", "title": "20 min break", "description": null, "startsAt": "2023-10-04T14:20:00", "endsAt": "2023-10-04T14:40:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 1 } ] }, { "slotStart": "14:40:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "550801", "title": "The Mario Kart™ guide to building a career", "description": "Mario Kart™ teaches us a lot of things: how to take shortcuts, how to stab your friends in the back, and most of all: how to get to the front of the pack. But have you ever stopped to wonder what lessons you can learn from it when it comes to planning for your own success?\r\n\r\nPersonally, I've had to overcome some obstacles to get to where I am today. And the things I have learned for myself, I have also applied as a coach at Axxes, where I have been involved in a lot of careers besides my own. Seeing other people grow has always been a key motivator for me in my role.\r\n\r\nA sure-fire road to success might not exist, but there are numerous lessons I've learned from doing this over the years. Those tips have been helpful to a lot of people, and I'll gladly share them with you.\r\n\r\nIn this session, I'll dive into building a career head-first. We'll use Mario Kart™ as a guideline and there will be anecdotes from my personal experience as a developer, a consultant and a coach. You'll walk away with some new ideas on how to handle your own career.", "startsAt": "2023-10-04T14:40:00", "endsAt": "2023-10-04T15:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "497f9bfb-7e28-4773-81e3-e853ca09ccde", "name": "Hannes Lowette" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "478480", "title": "Hedy: A gradual and multi-lingual programming language for education", "description": "When kids learn to program they often use either a visual language like Scratch, or a textual language like Python. While visual languages are great for the first steps, children and educators often want to move on to a textual language. However early on, a textual language and its error messages can be scary and frustrating.\r\n\r\nHedy aims to bridge this gap with a programming language that is gradual, using different language levels. In level 1, there is hardly any syntax at all; printing is done with: print hello! At every level, new syntax and concepts are added, so learners do not have to master everything at once. Hedy builds up to a subset of Python including conditions, loops, variables and lists.\r\n\r\nTo make learning as accessible as possible, Hedy allows for the use of localized keywords, f.e in Spanish:\r\n\r\nimprimir Hello!\r\n\r\nThis talk will discuss the pedagogy of Hedy as well as its technical aspects, since a set of changing and localized complex grammars poses several interesting challenges for parsing, and a small language offers a lot of potential from improved error messages.", "startsAt": "2023-10-04T14:40:00", "endsAt": "2023-10-04T15:30:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "b47c3560-95dc-43ed-b956-855af7e313d6", "name": "Mark Giesen" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 } ] }, { "slotStart": "15:30:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "1251ca06-4fda-4407-9be3-9aff27550c9f", "title": "20 min break", "description": null, "startsAt": "2023-10-04T15:30:00", "endsAt": "2023-10-04T15:50:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "15:50:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "459148", "title": "Making a Difference by Making Sense", "description": "In the early 1970s, professor Niklas Luhmann was given a monumental task: To formulate nothing less than a comprehensive sociological theory of society - as a whole, and for all of its major functional subsystems, such as the law, mass media, arts, etc. - within 30 years. \r\nLeaning on prior systems theories, he developed a unique take on what makes human society special: Not psychology, not individual humans, but what's in between them - communication! And that this communication has a dual form; it makes a difference by making sense: It carries within itself both the information of what is part of the system (included) and what is not (excluded), thereby defining and reinforcing the system boundary. \r\nOver the course of 15 years, Luhmann developed this framework into the \"Theory of Social Systems\", a revolutionary way of understanding the fabric and operations of how these systems appear, stabilize, evolve and differentiate, and of the structural couplings that tie them to their environment. It would help him to finish his work in time, and publish \"The Society of Society\" in 1997, a year before he died.\r\n25 years after Luhmann's death, we as a community have established our own ways to analyze, model and support the socio-technical systems of modern society, outside of the realm of sociology. But our ways still align remarkably with his work: In the way we use language to find system (domain!) boundaries. In how we use maps and adapters to manifest structural coupling between different contexts. In how teams and organizations are doomed to recreate the structure of their communication. And in how a system that is not used and evolved will fade, and cease to exist.\r\nIf \"culture is the ultimate context\" (Avraham Poupko), then society is the ultimate system. And the domains we observe and model are the residue of (sub)system operations. \r\nLet's explore what that means.\r\n \r\n", "startsAt": "2023-10-04T15:50:00", "endsAt": "2023-10-04T16:40:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "e75b7ec8-9d5e-494e-9047-c84094414e45", "name": "Tobias Goeschel" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "461471", "title": "Riding the elevator: DDD in the penthouse", "description": "In his book \"The Software Architect Elevator\" Gregor Hohpe uses the analogy of an elevator in a high building for the daily work which software architects should be doing: They are supposed to talk to folks who build and maintain stuff in the engine room but also make sure that the managment which is residing on the penthouse floors understand and gain interest in what is happening in the engine room.\r\n\r\nIn my talk I will build upon Gregors ideas and show you how you can leverage ideas from Domain Driven Design in this daunting communication tasks. But rest assured: I will not only present the obvious strategic Domain Drivend Design elements like core / supporting / generic subdomains here. We will go deeper and explore links to other initiatives in an org like DevOps, Agile and / org Design Thinking as well which are of interest for the leadership of an organization.\r\n\r\nWe as a community should get better at this topic because Domain Driven Design needs a healthy, blame free and safe environment in order to flourish and this environment needs to be established and lived by the leadership folks. \r\n\r\nPS: The talk idea and usage of Gregors elevator analogy have been approved by Gregor", "startsAt": "2023-10-04T15:50:00", "endsAt": "2023-10-04T16:40:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "c41a4363-aedb-42e0-8495-86be6c23107d", "name": "Michael Plöd" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 }, { "id": 34041, "name": "Room 3", "session": { "id": "483920", "title": "Let's unFIX organisations! How to use patterns to design your own agile framework.", "description": "Imagine a card set to playfully explore organisational design. A card set which can be used like Lego bricks, to build an individual agile framework serving the needs of your organisation. With unFIX this becomes reality! \r\nLet's discover together the new work from Jurgen Appelo (author \"Management 3.0\") and his unFIX team around organisational patterns to create workplaces for continuous innovation and better human experience.", "startsAt": "2023-10-04T15:50:00", "endsAt": "2023-10-04T17:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "acd98ad8-ebf2-4211-9762-38f88777b8e4", "name": "Tina Dreisicke" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 2 } ] }, { "slotStart": "16:40:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "4783dfa5-a300-43bb-8bc1-ebb4ecbeb7bb", "title": "20 min break", "description": null, "startsAt": "2023-10-04T16:40:00", "endsAt": "2023-10-04T17:00:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "c75589e0-c62c-4405-9ba1-423d6d240905", "title": "20 min break", "description": null, "startsAt": "2023-10-04T16:40:00", "endsAt": "2023-10-04T17:00:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 1 } ] }, { "slotStart": "17:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "472958", "title": "Human centred system design", "description": "IT is driven by STEM culture and its technical imperative, enabling the creation of technically advanced products. The issue though is that software development is inherently a sociotechnical enterprise. And the social aspects of it are often undervalued, even overlooked. We write software with people for people and sustainable solutions for both us and the users can only be reached by jointly optimise the technical and the social.\r\n\r\nIn this talk we will explore an approach from social sciences called Open Systems Theory. By looking at the milestones that led to this conceptual framework, like replacing the machine view the world, discovering group dynamics, realising that individuals only grow in groups, defining people as open purposeful systems, democratisation of work, discovering the genotypical organisational design principles, and understanding how critical participative design is to lasting and sustainable solutions. \r\n\r\nThe goal is to show that this approach will not only helps us create a learning organisation where people thrive and technology operates closer to its potential, but also one that performs better in an increasingly complex and competitive environment.", "startsAt": "2023-10-04T17:00:00", "endsAt": "2023-10-04T17:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "40a5fba3-0c7b-487c-9dc9-9d836a8ca999", "name": "Trond Hjorteland" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "471486", "title": "Journey to implement DDD into an organization", "description": "Top-down organizational journey to implement DDD, during the talk we will look at different decisions levels like, structural, technical, process and persons, because a change needs the enforcement of the organization to happen", "startsAt": "2023-10-04T17:00:00", "endsAt": "2023-10-04T17:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "57ac7058-1fcf-4d9a-802c-73b297e824b0", "name": "Javiera Laso" }, { "id": "846d57fa-0c0a-463c-97c8-31fb9fec084a", "name": "Octavio Valenzuela" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 } ] }, { "slotStart": "18:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "932e078e-2a70-4a44-8569-0d54c6d9dbe7", "title": "Evening reception until midnight", "description": "We will be socialising until midnight at the venue. Hannes 'Ceasar' Lowette will be your host for the night and guide you through the rites of passage from powerpoint karaoke in ancient rome to the costume contest. Unwind, relax and don't feed the lions!", "startsAt": "2023-10-04T18:00:00", "endsAt": "2023-10-04T18:50:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] } ] }, { "date": "2023-10-05T00:00:00", "isDefault": false, "rooms": [ { "id": 34039, "name": "Room 1", "sessions": [ { "id": "512431", "title": "Bounded Contexts: Manage the Understandability of Your Systems", "description": "From Parnas' paper in the 1970's to microservices in the 2010's, we've always used modularisation as a way to manage complexity in software. And yet, we still end up with big balls of mud. Technical separation alone isn’t enough. We’ve also tried separating into business domains, but it turns out that’s not enough either: software wants to be deeply interconnected, spanning different domains, and doesn’t respect those boundaries. \r\n\r\nBounded Contexts provide an alternative to splitting on domains or on technical modules. We can separate by looking at the semantics. The domain models that underlie our systems, the language that is being used, and the meanings of the terms. We can draw “understandability boundaries”: separations that look at how concepts in our system are understood together (or can be understood autonomously). If we organise the teams along the same lines, then team members will need to understand fewer concepts to be productive. Teams will need less coordination with other teams. Having better semantic boundaries lowers the cognitive load.\r\n\r\nDoing this kind of work is not free. But in the 20 years since the concept was introduced in Domain-Driven Design, we’ve developed patterns and heuristics to guide us.", "startsAt": "2023-10-05T09:00:00", "endsAt": "2023-10-05T09:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "e9368b72-175c-490b-9100-7cb5891fffdb", "name": "Mathias Verraes" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "ab0e96bd-3afc-4c72-82a2-476343a51f5c", "title": "20 min break", "description": null, "startsAt": "2023-10-05T09:50:00", "endsAt": "2023-10-05T10:10:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "458730", "title": "How a deeper software model enables breakthroughs in product development", "description": "Most products start with an initial software model, a model that is usually naive and superficial, based on shallow knowledge. Which makes sense, because you just started discovering and exploring that new product. So we typically start by identifying nouns and verbs and using these as the initial objects and methods to build in our code. While the initial model helps you start getting fast feedback for your product, once you get more feedback most of the time it isn’t a helpful model anymore. They usually don’t provide a rational expression of the primary concerns of the domain experts anymore as time progresses to build that product. Not having that expression can hold you back from making essential breakthroughs for your product, breakthroughs that can be the differentiation factor in the market. And even worse, implementing the model in code might not even support making these new breakthroughs.\r\n\r\nJoin us in this talk, where we present to you why we think it is crucial for the core model of your product to be continuously refactored towards a deeper model. We begin with a short introduction and the origin of Domain-Driven Design and model-driven design. Then we will explain the concepts of deep modelling, and why tactical patterns with a Supple design are essential to doing deep modelling. We will dive into a concrete example, worked out with the model exploration whirlpool and collaborative modelling practices like EventStorming, Example Mapping, and Responsibility mapping based on CRC cards. Finally, we dive into the code and show how we can get breakthroughs by continuously refactoring to deeper insights with a supple design getting a deep model.\r\n", "startsAt": "2023-10-05T10:10:00", "endsAt": "2023-10-05T11:00:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "cc81eb7f-48a8-41cf-ad56-2119ea13bf2f", "name": "Kenny (Baas) Schwegler" }, { "id": "34a0749a-b971-4220-b17b-f2b8b49123f9", "name": "Bruno Boucard" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "762562c2-5756-4b17-a249-c3984e7a246e", "title": "20 min break", "description": null, "startsAt": "2023-10-05T11:00:00", "endsAt": "2023-10-05T11:20:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "458396", "title": "Shifting from Projects to Feedback-Based Product Development: Practical Tips and Insights", "description": "As software continues to dominate the business landscape, there is a growing need for better digital products built with a feedback-based approach. While many organizations think they are agile, interviewing customers and preparing design mockups for weeks, followed by a backlog with the whole plan, for example, is still waterfall development. Most people involved in product development are unaware of how having a project or a product mindset influences the digital solution. They usually blame the developers when the software becomes slow, hard to maintain and error-prone, but the developers can't solve the root cause of these problems.\r\n\r\nDuring the talk, we will focus on identifying signs that your product development process is still waterfall-ish and the best practices for adopting a feedback-based approach. We will delve into how to decide what to build next and how much of it, define milestones, and determine when they are reached, to name a few examples. By doing so, you will leave better equipped to build digital products that are more responsive to customer needs, reduce the risk of failure, and promote innovation.", "startsAt": "2023-10-05T11:20:00", "endsAt": "2023-10-05T12:10:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "7f98b912-2211-47f4-920a-f15c01ca91bd", "name": "Krisztina Hirth" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "b2756163-7bfd-43e8-8729-e6786b2a6b35", "title": "20 min break", "description": null, "startsAt": "2023-10-05T12:10:00", "endsAt": "2023-10-05T12:30:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "458325", "title": "Work Produce People - The Far Reaching Effects of Organisational Design", "description": "Since the industrial revolution, our work life has been dominated by personal aspiration and power. Bureaucracy as organizational design has become so entrenched that few people see other options. We believe that autocratic command and control is necessary, even in industries like IT that rely heavily on perpetual design and collaboration skills.\r\n\r\nThe way we organize ourselves at work has far reaching consequences for our society. What happens at work cannot be contained behind the office doors, it influences our entire social field – work produce people. Understanding the social aspects of work can help us understand why some methods succeed and why others, despite our continued faith in them, just don't work.\r\n\r\nIn this talk, we will explore how maladaptive the industrial-era bureaucracy is for work today. We will see that a participative organisation, consisting of self-managing teams, is the only organisational structure proven to enable learning, collaboration, empowerment, trust and belonging. A jointly-optimised socio-technical system is true democracy of work.", "startsAt": "2023-10-05T12:30:00", "endsAt": "2023-10-05T13:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "40a5fba3-0c7b-487c-9dc9-9d836a8ca999", "name": "Trond Hjorteland" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "93fa3804-8f26-4d40-8cba-1bebafe19ba4", "title": "Lunch", "description": null, "startsAt": "2023-10-05T13:20:00", "endsAt": "2023-10-05T14:20:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "471639", "title": "The invisible elephant in the room", "description": "We've been talking about diversity and inclusion in our industry for some time now and most of us have at least a general idea of the issues at stake. But we sometimes forget about one of the aspects of diversity : disability. Not disability at a whole though, I'd say there has been quite an interest about accessibility and how to make our products better for our disabled users. But we almost never talk about disability in our industry. \r\n\r\nMany of us tech workers have disabilities and/or chronic illnesses that impact our daily lives. Yet, most of the tech industry can't seem to see us. It's always \"on friday we go running\" or \"we play soccer as a team\" or \"our team building week will make us do many physical stuff !\"... And disabled people get left behind. And it's even worst when our disabilities are invisible, as our coworkers and managers have even more issues to empathize with what we are living (the little bits we actually share about it). \r\n\r\nSo today I'd like to take some of your time to talk about the invisible elephant in the room : disability and how so many of our work culture makes the environment toxic for disabled workers. ", "startsAt": "2023-10-05T14:20:00", "endsAt": "2023-10-05T15:10:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "591a4990-fea5-49aa-8373-8e7850831bb8", "name": "Magali Milbergue" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "804be597-082f-44eb-8c3a-9767409e64dc", "title": "20 min break", "description": null, "startsAt": "2023-10-05T15:10:00", "endsAt": "2023-10-05T15:30:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "461951", "title": "When Customers don't share a language: Modelling Deep Dive", "description": "In 2015 we launched an innovative new product into the Australian Fintech landscape - a healthcare & disability insurance claiming platform to simplify life for support providers, recipients and insurers.\r\n\r\nIt was intended that a heterogeneous group of support providers and insurers would engage with the platform - from doctors to physiotherapists to disability support workers on one side, and private insurers & state or federal government departments on the other.\r\n\r\nAlthough the high level process for each of these groups was similar, the extant rules, terminology and UX scenarios varied.\r\n\r\nIn this talk, we'll do a deep dive of the modelling journey we went on, starting with aligning the model with our first customer, evolving it with our second, and radically reinventing it with our third.\r\n\r\nWe'll explore how the context map evolved from being aligned with user channels to being aligned with insurer subdomains and how we balanced the tradeoffs between specificity and genericness in the tactical pattern implementation within core domain contexts.", "startsAt": "2023-10-05T15:30:00", "endsAt": "2023-10-05T16:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "7ad6fd74-58ec-4fbd-a785-4d635ac41d89", "name": "Chris Simon" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "482257", "title": "The Ultimate Road Trip: A Hero's Journey Through Digital Product Development", "description": "Join us as we recount our journey, navigating the challenging terrain of digital product development in a 150-year-old German logistics enterprise. We will reveal the trials and tribulations we faced while attempting to replace our legacy transport management system. Hindered by a lack of digital product development expertise, we struggled with delays, disheartened employees, and a product far from deployment. Despite employing cutting-edge software architecture, our efforts seemed futile and we recognized the need for a transformational shift.\r\n\r\nThrough collaboration, learning, user experience, and a strategic focus on outcome-driven metrics, we steered closer to success. The journey is ongoing, but worth telling. We will discuss valuable lessons from our experiences, share our successes, failures, ongoing challenges, highlighting what lies ahead.\r\n\r\nWhether you're spearheading a digital transformation effort, developing digital products, or working in UX or product management, this talk is designed with you in mind. Join us for \"The Ultimate Road Trip\" and learn from our mistakes and insights.\r\n", "startsAt": "2023-10-05T16:30:00", "endsAt": "2023-10-05T17:20:00", "isServiceSession": false, "isPlenumSession": true, "speakers": [ { "id": "3ac30acb-8c05-461a-bff5-212bc52dbe70", "name": "Roman Sachse" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "cd9e840a-ca00-4a7b-a674-4119ada1eb02", "title": "Closing ceremony", "description": null, "startsAt": "2023-10-05T17:20:00", "endsAt": "2023-10-05T17:30:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false } ], "hasOnlyPlenumSessions": false }, { "id": 34040, "name": "Room 2", "sessions": [ { "id": "475092", "title": "No-code does not mean no-model", "description": "**TL, DR;** Embrace no-code to explore more models and throw most of those models away. You will quickly discover what works, and what matters, in the business process that you are automating. If it matters enough, you can extract it into a high-fidelity design in code.\r\n\r\nMany software projects still consume considerable resources, and take a long time before anything material is put in the hands of the end-user. At a smaller scale this happens with teams that have the ambition to adopt Domain-Driven Design principles but that lack the expertise and experience in how to approach the design process. There is a spectrum of mistakes. On one hand there is the lack of producing a meaningful and shared model that is able to unify the conflicts and handle the complexity that the messy world will serve the system. On the other end of that spectrum there is analysis paralysis: a model that never sees the light of day, because there is always a new case it cannot handle. If the team doesn't produce a meaningful model, or if it fails to put that model in front of experts early on, then the team robs itself of precious feedback. \"Judge models by their usefulness\" is a mantra that is difficult to live by, if the model isn't being used...\r\n\r\nDespite warnings, teams design big architectures early on, to support even bigger ambitions of the organization they work for, but they forget that it's not the architecture that the end-user cares about. With every bit of structure that is added early on, the team reduces the degrees of freedom to evolve the system at a later point in time. In order to support long-lasting design that is attuned to the environment, teams should set architectural principles that allow for a helpful structure to emerge, regardless of the platform. \r\n\r\n> **No code** has entered the chat...\r\n\r\nFor a while now, no-code vendors have been telling organizations that they shouldn't be limited by expensive software engineers to build systems that are useful. No-code aims to commoditize the software production process. Commodification of technology leads to value if it removes a limitation, but successful adoption only works if the rules and policies that initially helped us overcome the limitation are replaced as well. Practices such as DevOps have to be adopted in order to reap the benefits of the commodification of compute and storage in the cloud. In order to benefit from serverless, system components need to be decoupled through message-driven designs. In order to benefit from no-code, people have to organize around the software production process in a different way. \r\n\r\nWithin software engineering communities no-code has been dismissed as a fad, saying the need for writing code will never go away because the needs of most software systems are too complex to capture in a visual design environment. This viewpoint ignores the argument that software engineers act as a gatekeeper, a limitation for the stakeholder to get what they want. It is reductionist to say that no-code means no-code. No-code is as much about no-code, as wireless is about the absence of wires, or serverless is about the absence of servers. No-code means less boilerplate. And no-code does NOT mean no-model. \r\n\r\nThe inability to deliver meaningful results in a reasonable amount of time is never out of bad intent, it's the consequence of rigidity in the system of work. If there is no room for experiments, for error, for trying again, then we shouldn't be surprised if people attempt moonshots. But if we can reduce the cost of experiments, then we should be able to iterate more, learn faster, and as a consequence produce more value. \r\n\r\nLet's explore how no-code is able to remove the time to market of our ideas to explore new models. Join this session to uncover which rules, policies, and practices around modeling and design need to be replaced in order to reap the benefits that no-code has to offer. \r\n", "startsAt": "2023-10-05T09:00:00", "endsAt": "2023-10-05T09:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "71c7fe9d-126c-4d51-8a80-f7f2c673025a", "name": "Marijn Huizendveld" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "45fe83b3-e142-4231-8b47-000d6a17b6a0", "title": "20 min break", "description": null, "startsAt": "2023-10-05T09:50:00", "endsAt": "2023-10-05T10:10:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "461509", "title": "Pragmatic Approach to Architecture Metrics", "description": "A question we have all heard is: “How do you measure success?” Those metrics can look different for different industries or professions, but they are rooted in hard measurable outcomes: larger revenue for a bank, bigger market share for an automaker, reduced readmission rate for a hospital chain. Those numbers are easy to put on a chart in an executive presentation. But what about software architecture? Measuring success of software architecture is difficult because software architecture is all about long-term effects, positive or negative. Software architecture metrics are hard to define and even harder to evaluate objectively. As soon as a metric becomes a goal, it ceases to be a good metric (think “number of lines of code”). And we know all too well that software architecture is subject to frequent changes - no other industry moves as fast. However, we still need to be able to set goal posts, measure outcomes and present them to executives - in a practical way.\r\n\r\nAs Eliyahu Goldratt famously said, “Tell me how you measure me, and I will tell you how I will behave”. Focusing on low-level metrics can do more harm than good. A metric’s value becomes the end goal, rather than achieving the desired business outcomes. To fix this, let’s reverse the process. We are going to start by defining the business outcomes we want to achieve. The outcomes we are going to focus on are the ability to run a cost-effective system and ability to evolve it quickly and easily. Foundational to those objectives is the capacity to manage the complexity of the system. In this talk, we are going to explore several simple and pragmatic approaches to architectural metrics that support the required business outcomes.", "startsAt": "2023-10-05T10:10:00", "endsAt": "2023-10-05T11:00:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "05900f33-0d08-411a-8f8a-0ba18b8d21c7", "name": "Vlad Khononov" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "458752", "title": "Soulful Socio-Technical Architecture", "description": "In my opinion, a modern architecture vision cannot just be technical.\r\nIt has to consider the social dynamics involved in rapid learning teams, in particular when applying technical wisdom to domain understanding.\r\nIn this talk, I will present my view of organizations as socio-technical systems, with considerations on design and architecture heuristics.\r\nA journey from the bits of the codebase to the soul of our users, passing by the \"complexity in the heart of Software\" and its understanding by development teams.", "startsAt": "2023-10-05T11:20:00", "endsAt": "2023-10-05T12:10:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "914f7e50-ec99-440d-b4ab-c603ffeefdc6", "name": "Marco Consolaro" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "cf52f4ae-0871-4c00-9174-b82220e3eb81", "title": "20 min break", "description": null, "startsAt": "2023-10-05T12:10:00", "endsAt": "2023-10-05T12:30:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "461727", "title": "Shrinking transactional Boundaries: Domain-Driven Design for High Traffic Scenarios", "description": "Learn how to use Domain-Driven Design to handle high traffic scenarios by shrinking transactional boundaries. In this talk, we'll discuss what transactional boundaries are, how to identify them, and practical strategies for reducing them by examining how domains would work without computers. Whether you're an architect or an engineer, you'll gain valuable insights into building scalable and performant systems.", "startsAt": "2023-10-05T12:30:00", "endsAt": "2023-10-05T13:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "d593c31d-8d18-4689-a533-9241f70538bb", "name": "Robert Baelde" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "471399", "title": "What is stopping us? A legacy code question", "description": "This is about Legacy code. About how software becomes complex and hard to maintain over time. We all know of code bases like that, but do we understand what is stopping our teams from improving the code?\r\n\r\nIn my work on many systems over a 4 decade-long career, I’ve found that very often, there are blockers that are actively getting in the way. Finding the blockers includes addressing low trust working environments and the fear of making mistakes, traveling deep into the architecture of the code (with the benefit of hindsight), and looking at the infrastructure, tools and skills available to the team.\r\n\r\nThis talk will focus on systemic issues in Legacy systems, and how reframing the problem with a Systems Thinking lens can show us how the systems are getting in the way of letting good people do good work.\r\n\r\nWe will look at strategies for dealing with system issues, and try to face the truth of why, over time, all code bases tend towards the unmaintainable big ball of mud.\r\n\r\nI always believe that developers want to do a good job, and if they’re being ground down and unable to fix the code, we should look for reasons beyond blaming the developers.", "startsAt": "2023-10-05T14:20:00", "endsAt": "2023-10-05T15:10:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "eafe1c3c-b81b-4d33-94b8-f9142100f734", "name": "Lorraine Steyn" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "66deea10-8b51-4607-961e-307f887a7206", "title": "20 min break", "description": null, "startsAt": "2023-10-05T15:10:00", "endsAt": "2023-10-05T15:30:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "473784", "title": "Architecting Apollo: Systems Design Lessons from the Golden Age of Spaceflight", "description": "The earliest crewed spaceflights, including the Mercury, Gemini, and Apollo programs, were some of the earliest instances of software being responsible for life-or-death decisions. While various aspects of the software and systems design could be considered outdated by modern standards, many of the core principles and design choices are directly relevant to the systems we build today.\r\n\r\nThis talk dives into several of the disasters and near-fatal accidents of early crewed spaceflight, including Gemini 8 and Apollo 11, and focuses on the system design choices that either led to or averted catastrophe. Topics include fail-open vs. fail-closed design, recoverable software, process prioritization, levels of autonomy, and designing for human intervention.", "startsAt": "2023-10-05T15:30:00", "endsAt": "2023-10-05T16:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "501d43b6-ac49-4ce3-910c-be20051db595", "name": "Kyle Kotowick" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true } ], "hasOnlyPlenumSessions": false }, { "id": 34041, "name": "Room 3", "sessions": [ { "id": "473251", "title": "Creating magical moments - Collaborative Modeling meets Liberating Structures", "description": "Collaborative Modeling and Liberating Structures share many similarities like fostering a shared understanding in groups and real collaboration by including and unleashing everyone. In this hands-on lab, I will show you how you can improve your next Collaborative Modeling workshop with the surprising power of Liberating Structures.\r\n\r\nLiberating Structures are a set easy-to-learn microstructures that offer real participation for all people involved. In contrast to conventional structures like presentations or open discussions they offer the right amount of structure to ensure target-oriented interactions while leaving enough space for innovative ideas to spark.\u2028\u2028\r\n\r\nDuring this highly interactive workshop we will practice several Liberating Structures and reflect on how and why they work. We will compare them with the well-known conventional structures by examining the five design elements (structuring invitation, space and material, distribution of participation, group configuration, sequence of steps and timing) that define all microstructures.\r\n\r\n\u2028\u2028We will take a deeper look at the similarities of Liberating Structures and Collaborative Modeling and see how Liberating Structures can support certain aspects of Collaborative Modeling. \r\n\r\nLiberating Structures and Collaborative Modeling form a perfect match in a facilitator’s repertoire and in the end every participant will have at least one implementable idea that will help improve his/her future Collaborative Modeling workshops.", "startsAt": "2023-10-05T09:00:00", "endsAt": "2023-10-05T11:00:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "091e80f2-706f-4da2-826a-fdd63c1b71dc", "name": "Martin Günther" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "456970", "title": "Growing Pains: Scaling and Re-architecting Systems Under Fire", "description": "When our tiny startup was acquired by a giant corporate we tried to understand all the possible implications on our engineering organization. We thought the giant scale would catch up with us at some point, but like everything in tech that's at high velocity, it came much sooner than planned. We quickly understood that our infant system built for our first phases was starting to break down under million user scale.\r\n\r\nWe needed to re-architect... and under fire! With the sudden influx of production clients we couldn't disappoint.\r\n\r\nBut that wasn’t all! We needed to do so while pivoting our app to be user facing for the first time.\r\n\r\nIn this talk, we’ll discuss tackling a whole new set of challenges for a small fish suddenly thrown into a huge ocean - including architecture breakers, scaling up and re-building ourselves with a reliable, scalable, user friendly AND facing system.", "startsAt": "2023-10-05T11:20:00", "endsAt": "2023-10-05T13:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "94b2b615-7a4a-4a7d-9eb8-383a220860f6", "name": "Shelly Shmurack" }, { "id": "8816f18a-6bb3-473d-8f24-037d1f34a7b7", "name": "Yara Mutlak" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, { "id": "472137", "title": "Tell the Domain Story of the Future with Functional Programming", "description": "Domain Stories are great for understanding the domain and its requirements. However, on the way to working software, you still need to create models. How can we turn the Domain Story into a model that mirrors the domain, yields deep insights, sparks joy using it, and lasts long? You can use DDD to model close to the domain, but the resulting models are often brittle in the face of changes. Henning (Domain Storytelling representative) and Mike (functional programming envoy) show you (together with their pal Barry the banker) how to combine Domain Storytelling with techniques from functional programming - abstraction, algebra, combinator models - to evolve supple domain models that are ready for the requirements of the present as well as those of the future.\r\n", "startsAt": "2023-10-05T14:20:00", "endsAt": "2023-10-05T16:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "ce44099d-db16-4f49-9a02-ba1537f69560", "name": "Mike Sperber" }, { "id": "de44a1c1-8728-4063-b3d0-c0b3e7e87c4f", "name": "Henning Schwentner" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true } ], "hasOnlyPlenumSessions": false } ], "timeSlots": [ { "slotStart": "09:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "512431", "title": "Bounded Contexts: Manage the Understandability of Your Systems", "description": "From Parnas' paper in the 1970's to microservices in the 2010's, we've always used modularisation as a way to manage complexity in software. And yet, we still end up with big balls of mud. Technical separation alone isn’t enough. We’ve also tried separating into business domains, but it turns out that’s not enough either: software wants to be deeply interconnected, spanning different domains, and doesn’t respect those boundaries. \r\n\r\nBounded Contexts provide an alternative to splitting on domains or on technical modules. We can separate by looking at the semantics. The domain models that underlie our systems, the language that is being used, and the meanings of the terms. We can draw “understandability boundaries”: separations that look at how concepts in our system are understood together (or can be understood autonomously). If we organise the teams along the same lines, then team members will need to understand fewer concepts to be productive. Teams will need less coordination with other teams. Having better semantic boundaries lowers the cognitive load.\r\n\r\nDoing this kind of work is not free. But in the 20 years since the concept was introduced in Domain-Driven Design, we’ve developed patterns and heuristics to guide us.", "startsAt": "2023-10-05T09:00:00", "endsAt": "2023-10-05T09:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "e9368b72-175c-490b-9100-7cb5891fffdb", "name": "Mathias Verraes" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "475092", "title": "No-code does not mean no-model", "description": "**TL, DR;** Embrace no-code to explore more models and throw most of those models away. You will quickly discover what works, and what matters, in the business process that you are automating. If it matters enough, you can extract it into a high-fidelity design in code.\r\n\r\nMany software projects still consume considerable resources, and take a long time before anything material is put in the hands of the end-user. At a smaller scale this happens with teams that have the ambition to adopt Domain-Driven Design principles but that lack the expertise and experience in how to approach the design process. There is a spectrum of mistakes. On one hand there is the lack of producing a meaningful and shared model that is able to unify the conflicts and handle the complexity that the messy world will serve the system. On the other end of that spectrum there is analysis paralysis: a model that never sees the light of day, because there is always a new case it cannot handle. If the team doesn't produce a meaningful model, or if it fails to put that model in front of experts early on, then the team robs itself of precious feedback. \"Judge models by their usefulness\" is a mantra that is difficult to live by, if the model isn't being used...\r\n\r\nDespite warnings, teams design big architectures early on, to support even bigger ambitions of the organization they work for, but they forget that it's not the architecture that the end-user cares about. With every bit of structure that is added early on, the team reduces the degrees of freedom to evolve the system at a later point in time. In order to support long-lasting design that is attuned to the environment, teams should set architectural principles that allow for a helpful structure to emerge, regardless of the platform. \r\n\r\n> **No code** has entered the chat...\r\n\r\nFor a while now, no-code vendors have been telling organizations that they shouldn't be limited by expensive software engineers to build systems that are useful. No-code aims to commoditize the software production process. Commodification of technology leads to value if it removes a limitation, but successful adoption only works if the rules and policies that initially helped us overcome the limitation are replaced as well. Practices such as DevOps have to be adopted in order to reap the benefits of the commodification of compute and storage in the cloud. In order to benefit from serverless, system components need to be decoupled through message-driven designs. In order to benefit from no-code, people have to organize around the software production process in a different way. \r\n\r\nWithin software engineering communities no-code has been dismissed as a fad, saying the need for writing code will never go away because the needs of most software systems are too complex to capture in a visual design environment. This viewpoint ignores the argument that software engineers act as a gatekeeper, a limitation for the stakeholder to get what they want. It is reductionist to say that no-code means no-code. No-code is as much about no-code, as wireless is about the absence of wires, or serverless is about the absence of servers. No-code means less boilerplate. And no-code does NOT mean no-model. \r\n\r\nThe inability to deliver meaningful results in a reasonable amount of time is never out of bad intent, it's the consequence of rigidity in the system of work. If there is no room for experiments, for error, for trying again, then we shouldn't be surprised if people attempt moonshots. But if we can reduce the cost of experiments, then we should be able to iterate more, learn faster, and as a consequence produce more value. \r\n\r\nLet's explore how no-code is able to remove the time to market of our ideas to explore new models. Join this session to uncover which rules, policies, and practices around modeling and design need to be replaced in order to reap the benefits that no-code has to offer. \r\n", "startsAt": "2023-10-05T09:00:00", "endsAt": "2023-10-05T09:50:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "71c7fe9d-126c-4d51-8a80-f7f2c673025a", "name": "Marijn Huizendveld" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 }, { "id": 34041, "name": "Room 3", "session": { "id": "473251", "title": "Creating magical moments - Collaborative Modeling meets Liberating Structures", "description": "Collaborative Modeling and Liberating Structures share many similarities like fostering a shared understanding in groups and real collaboration by including and unleashing everyone. In this hands-on lab, I will show you how you can improve your next Collaborative Modeling workshop with the surprising power of Liberating Structures.\r\n\r\nLiberating Structures are a set easy-to-learn microstructures that offer real participation for all people involved. In contrast to conventional structures like presentations or open discussions they offer the right amount of structure to ensure target-oriented interactions while leaving enough space for innovative ideas to spark.\u2028\u2028\r\n\r\nDuring this highly interactive workshop we will practice several Liberating Structures and reflect on how and why they work. We will compare them with the well-known conventional structures by examining the five design elements (structuring invitation, space and material, distribution of participation, group configuration, sequence of steps and timing) that define all microstructures.\r\n\r\n\u2028\u2028We will take a deeper look at the similarities of Liberating Structures and Collaborative Modeling and see how Liberating Structures can support certain aspects of Collaborative Modeling. \r\n\r\nLiberating Structures and Collaborative Modeling form a perfect match in a facilitator’s repertoire and in the end every participant will have at least one implementable idea that will help improve his/her future Collaborative Modeling workshops.", "startsAt": "2023-10-05T09:00:00", "endsAt": "2023-10-05T11:00:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "091e80f2-706f-4da2-826a-fdd63c1b71dc", "name": "Martin Günther" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 2 } ] }, { "slotStart": "09:50:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "ab0e96bd-3afc-4c72-82a2-476343a51f5c", "title": "20 min break", "description": null, "startsAt": "2023-10-05T09:50:00", "endsAt": "2023-10-05T10:10:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "45fe83b3-e142-4231-8b47-000d6a17b6a0", "title": "20 min break", "description": null, "startsAt": "2023-10-05T09:50:00", "endsAt": "2023-10-05T10:10:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 1 } ] }, { "slotStart": "10:10:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "458730", "title": "How a deeper software model enables breakthroughs in product development", "description": "Most products start with an initial software model, a model that is usually naive and superficial, based on shallow knowledge. Which makes sense, because you just started discovering and exploring that new product. So we typically start by identifying nouns and verbs and using these as the initial objects and methods to build in our code. While the initial model helps you start getting fast feedback for your product, once you get more feedback most of the time it isn’t a helpful model anymore. They usually don’t provide a rational expression of the primary concerns of the domain experts anymore as time progresses to build that product. Not having that expression can hold you back from making essential breakthroughs for your product, breakthroughs that can be the differentiation factor in the market. And even worse, implementing the model in code might not even support making these new breakthroughs.\r\n\r\nJoin us in this talk, where we present to you why we think it is crucial for the core model of your product to be continuously refactored towards a deeper model. We begin with a short introduction and the origin of Domain-Driven Design and model-driven design. Then we will explain the concepts of deep modelling, and why tactical patterns with a Supple design are essential to doing deep modelling. We will dive into a concrete example, worked out with the model exploration whirlpool and collaborative modelling practices like EventStorming, Example Mapping, and Responsibility mapping based on CRC cards. Finally, we dive into the code and show how we can get breakthroughs by continuously refactoring to deeper insights with a supple design getting a deep model.\r\n", "startsAt": "2023-10-05T10:10:00", "endsAt": "2023-10-05T11:00:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "cc81eb7f-48a8-41cf-ad56-2119ea13bf2f", "name": "Kenny (Baas) Schwegler" }, { "id": "34a0749a-b971-4220-b17b-f2b8b49123f9", "name": "Bruno Boucard" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "461509", "title": "Pragmatic Approach to Architecture Metrics", "description": "A question we have all heard is: “How do you measure success?” Those metrics can look different for different industries or professions, but they are rooted in hard measurable outcomes: larger revenue for a bank, bigger market share for an automaker, reduced readmission rate for a hospital chain. Those numbers are easy to put on a chart in an executive presentation. But what about software architecture? Measuring success of software architecture is difficult because software architecture is all about long-term effects, positive or negative. Software architecture metrics are hard to define and even harder to evaluate objectively. As soon as a metric becomes a goal, it ceases to be a good metric (think “number of lines of code”). And we know all too well that software architecture is subject to frequent changes - no other industry moves as fast. However, we still need to be able to set goal posts, measure outcomes and present them to executives - in a practical way.\r\n\r\nAs Eliyahu Goldratt famously said, “Tell me how you measure me, and I will tell you how I will behave”. Focusing on low-level metrics can do more harm than good. A metric’s value becomes the end goal, rather than achieving the desired business outcomes. To fix this, let’s reverse the process. We are going to start by defining the business outcomes we want to achieve. The outcomes we are going to focus on are the ability to run a cost-effective system and ability to evolve it quickly and easily. Foundational to those objectives is the capacity to manage the complexity of the system. In this talk, we are going to explore several simple and pragmatic approaches to architectural metrics that support the required business outcomes.", "startsAt": "2023-10-05T10:10:00", "endsAt": "2023-10-05T11:00:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "05900f33-0d08-411a-8f8a-0ba18b8d21c7", "name": "Vlad Khononov" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 } ] }, { "slotStart": "11:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "762562c2-5756-4b17-a249-c3984e7a246e", "title": "20 min break", "description": null, "startsAt": "2023-10-05T11:00:00", "endsAt": "2023-10-05T11:20:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "11:20:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "458396", "title": "Shifting from Projects to Feedback-Based Product Development: Practical Tips and Insights", "description": "As software continues to dominate the business landscape, there is a growing need for better digital products built with a feedback-based approach. While many organizations think they are agile, interviewing customers and preparing design mockups for weeks, followed by a backlog with the whole plan, for example, is still waterfall development. Most people involved in product development are unaware of how having a project or a product mindset influences the digital solution. They usually blame the developers when the software becomes slow, hard to maintain and error-prone, but the developers can't solve the root cause of these problems.\r\n\r\nDuring the talk, we will focus on identifying signs that your product development process is still waterfall-ish and the best practices for adopting a feedback-based approach. We will delve into how to decide what to build next and how much of it, define milestones, and determine when they are reached, to name a few examples. By doing so, you will leave better equipped to build digital products that are more responsive to customer needs, reduce the risk of failure, and promote innovation.", "startsAt": "2023-10-05T11:20:00", "endsAt": "2023-10-05T12:10:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "7f98b912-2211-47f4-920a-f15c01ca91bd", "name": "Krisztina Hirth" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "458752", "title": "Soulful Socio-Technical Architecture", "description": "In my opinion, a modern architecture vision cannot just be technical.\r\nIt has to consider the social dynamics involved in rapid learning teams, in particular when applying technical wisdom to domain understanding.\r\nIn this talk, I will present my view of organizations as socio-technical systems, with considerations on design and architecture heuristics.\r\nA journey from the bits of the codebase to the soul of our users, passing by the \"complexity in the heart of Software\" and its understanding by development teams.", "startsAt": "2023-10-05T11:20:00", "endsAt": "2023-10-05T12:10:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "914f7e50-ec99-440d-b4ab-c603ffeefdc6", "name": "Marco Consolaro" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 }, { "id": 34041, "name": "Room 3", "session": { "id": "456970", "title": "Growing Pains: Scaling and Re-architecting Systems Under Fire", "description": "When our tiny startup was acquired by a giant corporate we tried to understand all the possible implications on our engineering organization. We thought the giant scale would catch up with us at some point, but like everything in tech that's at high velocity, it came much sooner than planned. We quickly understood that our infant system built for our first phases was starting to break down under million user scale.\r\n\r\nWe needed to re-architect... and under fire! With the sudden influx of production clients we couldn't disappoint.\r\n\r\nBut that wasn’t all! We needed to do so while pivoting our app to be user facing for the first time.\r\n\r\nIn this talk, we’ll discuss tackling a whole new set of challenges for a small fish suddenly thrown into a huge ocean - including architecture breakers, scaling up and re-building ourselves with a reliable, scalable, user friendly AND facing system.", "startsAt": "2023-10-05T11:20:00", "endsAt": "2023-10-05T13:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "94b2b615-7a4a-4a7d-9eb8-383a220860f6", "name": "Shelly Shmurack" }, { "id": "8816f18a-6bb3-473d-8f24-037d1f34a7b7", "name": "Yara Mutlak" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 2 } ] }, { "slotStart": "12:10:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "b2756163-7bfd-43e8-8729-e6786b2a6b35", "title": "20 min break", "description": null, "startsAt": "2023-10-05T12:10:00", "endsAt": "2023-10-05T12:30:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "cf52f4ae-0871-4c00-9174-b82220e3eb81", "title": "20 min break", "description": null, "startsAt": "2023-10-05T12:10:00", "endsAt": "2023-10-05T12:30:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 1 } ] }, { "slotStart": "12:30:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "458325", "title": "Work Produce People - The Far Reaching Effects of Organisational Design", "description": "Since the industrial revolution, our work life has been dominated by personal aspiration and power. Bureaucracy as organizational design has become so entrenched that few people see other options. We believe that autocratic command and control is necessary, even in industries like IT that rely heavily on perpetual design and collaboration skills.\r\n\r\nThe way we organize ourselves at work has far reaching consequences for our society. What happens at work cannot be contained behind the office doors, it influences our entire social field – work produce people. Understanding the social aspects of work can help us understand why some methods succeed and why others, despite our continued faith in them, just don't work.\r\n\r\nIn this talk, we will explore how maladaptive the industrial-era bureaucracy is for work today. We will see that a participative organisation, consisting of self-managing teams, is the only organisational structure proven to enable learning, collaboration, empowerment, trust and belonging. A jointly-optimised socio-technical system is true democracy of work.", "startsAt": "2023-10-05T12:30:00", "endsAt": "2023-10-05T13:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "40a5fba3-0c7b-487c-9dc9-9d836a8ca999", "name": "Trond Hjorteland" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "461727", "title": "Shrinking transactional Boundaries: Domain-Driven Design for High Traffic Scenarios", "description": "Learn how to use Domain-Driven Design to handle high traffic scenarios by shrinking transactional boundaries. In this talk, we'll discuss what transactional boundaries are, how to identify them, and practical strategies for reducing them by examining how domains would work without computers. Whether you're an architect or an engineer, you'll gain valuable insights into building scalable and performant systems.", "startsAt": "2023-10-05T12:30:00", "endsAt": "2023-10-05T13:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "d593c31d-8d18-4689-a533-9241f70538bb", "name": "Robert Baelde" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 } ] }, { "slotStart": "13:20:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "93fa3804-8f26-4d40-8cba-1bebafe19ba4", "title": "Lunch", "description": null, "startsAt": "2023-10-05T13:20:00", "endsAt": "2023-10-05T14:20:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "14:20:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "471639", "title": "The invisible elephant in the room", "description": "We've been talking about diversity and inclusion in our industry for some time now and most of us have at least a general idea of the issues at stake. But we sometimes forget about one of the aspects of diversity : disability. Not disability at a whole though, I'd say there has been quite an interest about accessibility and how to make our products better for our disabled users. But we almost never talk about disability in our industry. \r\n\r\nMany of us tech workers have disabilities and/or chronic illnesses that impact our daily lives. Yet, most of the tech industry can't seem to see us. It's always \"on friday we go running\" or \"we play soccer as a team\" or \"our team building week will make us do many physical stuff !\"... And disabled people get left behind. And it's even worst when our disabilities are invisible, as our coworkers and managers have even more issues to empathize with what we are living (the little bits we actually share about it). \r\n\r\nSo today I'd like to take some of your time to talk about the invisible elephant in the room : disability and how so many of our work culture makes the environment toxic for disabled workers. ", "startsAt": "2023-10-05T14:20:00", "endsAt": "2023-10-05T15:10:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "591a4990-fea5-49aa-8373-8e7850831bb8", "name": "Magali Milbergue" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "471399", "title": "What is stopping us? A legacy code question", "description": "This is about Legacy code. About how software becomes complex and hard to maintain over time. We all know of code bases like that, but do we understand what is stopping our teams from improving the code?\r\n\r\nIn my work on many systems over a 4 decade-long career, I’ve found that very often, there are blockers that are actively getting in the way. Finding the blockers includes addressing low trust working environments and the fear of making mistakes, traveling deep into the architecture of the code (with the benefit of hindsight), and looking at the infrastructure, tools and skills available to the team.\r\n\r\nThis talk will focus on systemic issues in Legacy systems, and how reframing the problem with a Systems Thinking lens can show us how the systems are getting in the way of letting good people do good work.\r\n\r\nWe will look at strategies for dealing with system issues, and try to face the truth of why, over time, all code bases tend towards the unmaintainable big ball of mud.\r\n\r\nI always believe that developers want to do a good job, and if they’re being ground down and unable to fix the code, we should look for reasons beyond blaming the developers.", "startsAt": "2023-10-05T14:20:00", "endsAt": "2023-10-05T15:10:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "eafe1c3c-b81b-4d33-94b8-f9142100f734", "name": "Lorraine Steyn" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 }, { "id": 34041, "name": "Room 3", "session": { "id": "472137", "title": "Tell the Domain Story of the Future with Functional Programming", "description": "Domain Stories are great for understanding the domain and its requirements. However, on the way to working software, you still need to create models. How can we turn the Domain Story into a model that mirrors the domain, yields deep insights, sparks joy using it, and lasts long? You can use DDD to model close to the domain, but the resulting models are often brittle in the face of changes. Henning (Domain Storytelling representative) and Mike (functional programming envoy) show you (together with their pal Barry the banker) how to combine Domain Storytelling with techniques from functional programming - abstraction, algebra, combinator models - to evolve supple domain models that are ready for the requirements of the present as well as those of the future.\r\n", "startsAt": "2023-10-05T14:20:00", "endsAt": "2023-10-05T16:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "ce44099d-db16-4f49-9a02-ba1537f69560", "name": "Mike Sperber" }, { "id": "de44a1c1-8728-4063-b3d0-c0b3e7e87c4f", "name": "Henning Schwentner" } ], "categories": [], "roomId": 34041, "room": "Room 3", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 2 } ] }, { "slotStart": "15:10:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "804be597-082f-44eb-8c3a-9767409e64dc", "title": "20 min break", "description": null, "startsAt": "2023-10-05T15:10:00", "endsAt": "2023-10-05T15:30:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "66deea10-8b51-4607-961e-307f887a7206", "title": "20 min break", "description": null, "startsAt": "2023-10-05T15:10:00", "endsAt": "2023-10-05T15:30:00", "isServiceSession": true, "isPlenumSession": false, "speakers": [], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 1 } ] }, { "slotStart": "15:30:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "461951", "title": "When Customers don't share a language: Modelling Deep Dive", "description": "In 2015 we launched an innovative new product into the Australian Fintech landscape - a healthcare & disability insurance claiming platform to simplify life for support providers, recipients and insurers.\r\n\r\nIt was intended that a heterogeneous group of support providers and insurers would engage with the platform - from doctors to physiotherapists to disability support workers on one side, and private insurers & state or federal government departments on the other.\r\n\r\nAlthough the high level process for each of these groups was similar, the extant rules, terminology and UX scenarios varied.\r\n\r\nIn this talk, we'll do a deep dive of the modelling journey we went on, starting with aligning the model with our first customer, evolving it with our second, and radically reinventing it with our third.\r\n\r\nWe'll explore how the context map evolved from being aligned with user channels to being aligned with insurer subdomains and how we balanced the tradeoffs between specificity and genericness in the tactical pattern implementation within core domain contexts.", "startsAt": "2023-10-05T15:30:00", "endsAt": "2023-10-05T16:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "7ad6fd74-58ec-4fbd-a785-4d635ac41d89", "name": "Chris Simon" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 }, { "id": 34040, "name": "Room 2", "session": { "id": "473784", "title": "Architecting Apollo: Systems Design Lessons from the Golden Age of Spaceflight", "description": "The earliest crewed spaceflights, including the Mercury, Gemini, and Apollo programs, were some of the earliest instances of software being responsible for life-or-death decisions. While various aspects of the software and systems design could be considered outdated by modern standards, many of the core principles and design choices are directly relevant to the systems we build today.\r\n\r\nThis talk dives into several of the disasters and near-fatal accidents of early crewed spaceflight, including Gemini 8 and Apollo 11, and focuses on the system design choices that either led to or averted catastrophe. Topics include fail-open vs. fail-closed design, recoverable software, process prioritization, levels of autonomy, and designing for human intervention.", "startsAt": "2023-10-05T15:30:00", "endsAt": "2023-10-05T16:20:00", "isServiceSession": false, "isPlenumSession": false, "speakers": [ { "id": "501d43b6-ac49-4ce3-910c-be20051db595", "name": "Kyle Kotowick" } ], "categories": [], "roomId": 34040, "room": "Room 2", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 1 } ] }, { "slotStart": "16:30:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "482257", "title": "The Ultimate Road Trip: A Hero's Journey Through Digital Product Development", "description": "Join us as we recount our journey, navigating the challenging terrain of digital product development in a 150-year-old German logistics enterprise. We will reveal the trials and tribulations we faced while attempting to replace our legacy transport management system. Hindered by a lack of digital product development expertise, we struggled with delays, disheartened employees, and a product far from deployment. Despite employing cutting-edge software architecture, our efforts seemed futile and we recognized the need for a transformational shift.\r\n\r\nThrough collaboration, learning, user experience, and a strategic focus on outcome-driven metrics, we steered closer to success. The journey is ongoing, but worth telling. We will discuss valuable lessons from our experiences, share our successes, failures, ongoing challenges, highlighting what lies ahead.\r\n\r\nWhether you're spearheading a digital transformation effort, developing digital products, or working in UX or product management, this talk is designed with you in mind. Join us for \"The Ultimate Road Trip\" and learn from our mistakes and insights.\r\n", "startsAt": "2023-10-05T16:30:00", "endsAt": "2023-10-05T17:20:00", "isServiceSession": false, "isPlenumSession": true, "speakers": [ { "id": "3ac30acb-8c05-461a-bff5-212bc52dbe70", "name": "Roman Sachse" } ], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": "Accepted", "isInformed": true, "isConfirmed": true }, "index": 0 } ] }, { "slotStart": "17:20:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "cd9e840a-ca00-4a7b-a674-4119ada1eb02", "title": "Closing ceremony", "description": null, "startsAt": "2023-10-05T17:20:00", "endsAt": "2023-10-05T17:30:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] } ] }, { "date": "2023-10-06T00:00:00", "isDefault": false, "rooms": [ { "id": 34039, "name": "Room 1", "sessions": [ { "id": "f6d6f305-8ca2-4a3f-84b3-488e8b91c6eb", "title": "Marketplace", "description": "We will introduce newcomers and old friends to the Open Space format to ensure a full day of collaborative learning. \nYou will set your own agenda based on questions, ideas and methods that you have gathered throughout the conference. \n\nThere are no more speakers and attendees, we all come together to create a safe space for intense learning and deep practise. \nThere is no smarter beeing on this planet than a collaboratively learning community, come and be part of it!", "startsAt": "2023-10-06T09:00:00", "endsAt": "2023-10-06T09:45:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "3f6e3e5d-05ab-441d-b94e-c2f5f4b2eb04", "title": "Coffee", "description": null, "startsAt": "2023-10-06T09:45:00", "endsAt": "2023-10-06T10:00:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "495c5434-da0c-4d78-8e28-90bdf6c791ed", "title": "Morning Sessions", "description": "You have set the agenda for the morning yourselfes during the introduction.\n\nWe now have 6 Rooms, houndrets of meters of paperrolls, endless sticky notes and coffee for you to make your learning journey the best it can be.\n\nCoding, collaborative modelling, small dialogs, presentations or group discussions... Whatever will happen is the best thing that could have happend!", "startsAt": "2023-10-06T10:00:00", "endsAt": "2023-10-06T13:00:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "428946b1-7519-4ec9-8d80-75cf3d1f8d9d", "title": "Lunch", "description": null, "startsAt": "2023-10-06T13:00:00", "endsAt": "2023-10-06T13:45:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "ec341978-9a80-4824-b335-e0197d18d3bf", "title": "Afternoon Sessions", "description": "By now you should know what happens here ;)", "startsAt": "2023-10-06T13:45:00", "endsAt": "2023-10-06T15:15:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "bb624f73-6d74-405c-8ef9-948708f444c5", "title": "Coffee", "description": null, "startsAt": "2023-10-06T15:15:00", "endsAt": "2023-10-06T15:30:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "3066dcd5-9aef-4fe9-8059-a0fd2a0f94fc", "title": "Afternoon Sessions", "description": null, "startsAt": "2023-10-06T15:30:00", "endsAt": "2023-10-06T17:00:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, { "id": "ad16ffd0-8c2c-4ec0-8921-1009da110e6d", "title": "Retrospective and Goodbye", "description": null, "startsAt": "2023-10-06T17:00:00", "endsAt": "2023-10-06T18:00:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false } ], "hasOnlyPlenumSessions": true } ], "timeSlots": [ { "slotStart": "09:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "f6d6f305-8ca2-4a3f-84b3-488e8b91c6eb", "title": "Marketplace", "description": "We will introduce newcomers and old friends to the Open Space format to ensure a full day of collaborative learning. \nYou will set your own agenda based on questions, ideas and methods that you have gathered throughout the conference. \n\nThere are no more speakers and attendees, we all come together to create a safe space for intense learning and deep practise. \nThere is no smarter beeing on this planet than a collaboratively learning community, come and be part of it!", "startsAt": "2023-10-06T09:00:00", "endsAt": "2023-10-06T09:45:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "09:45:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "3f6e3e5d-05ab-441d-b94e-c2f5f4b2eb04", "title": "Coffee", "description": null, "startsAt": "2023-10-06T09:45:00", "endsAt": "2023-10-06T10:00:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "10:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "495c5434-da0c-4d78-8e28-90bdf6c791ed", "title": "Morning Sessions", "description": "You have set the agenda for the morning yourselfes during the introduction.\n\nWe now have 6 Rooms, houndrets of meters of paperrolls, endless sticky notes and coffee for you to make your learning journey the best it can be.\n\nCoding, collaborative modelling, small dialogs, presentations or group discussions... Whatever will happen is the best thing that could have happend!", "startsAt": "2023-10-06T10:00:00", "endsAt": "2023-10-06T13:00:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "13:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "428946b1-7519-4ec9-8d80-75cf3d1f8d9d", "title": "Lunch", "description": null, "startsAt": "2023-10-06T13:00:00", "endsAt": "2023-10-06T13:45:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "13:45:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "ec341978-9a80-4824-b335-e0197d18d3bf", "title": "Afternoon Sessions", "description": "By now you should know what happens here ;)", "startsAt": "2023-10-06T13:45:00", "endsAt": "2023-10-06T15:15:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "15:15:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "bb624f73-6d74-405c-8ef9-948708f444c5", "title": "Coffee", "description": null, "startsAt": "2023-10-06T15:15:00", "endsAt": "2023-10-06T15:30:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "15:30:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "3066dcd5-9aef-4fe9-8059-a0fd2a0f94fc", "title": "Afternoon Sessions", "description": null, "startsAt": "2023-10-06T15:30:00", "endsAt": "2023-10-06T17:00:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] }, { "slotStart": "17:00:00", "rooms": [ { "id": 34039, "name": "Room 1", "session": { "id": "ad16ffd0-8c2c-4ec0-8921-1009da110e6d", "title": "Retrospective and Goodbye", "description": null, "startsAt": "2023-10-06T17:00:00", "endsAt": "2023-10-06T18:00:00", "isServiceSession": true, "isPlenumSession": true, "speakers": [], "categories": [], "roomId": 34039, "room": "Room 1", "liveUrl": null, "recordingUrl": null, "status": null, "isInformed": false, "isConfirmed": false }, "index": 0 } ] } ] } ]