Impact Mapping Workshop en de

"Impact mapping is a lightweight, collaborative planning technique for teams that want to make a big impact with software products. It is based on user interaction design, outcome-driven planning and mind mapping. Impact maps help delivery teams and stakeholders visualise roadmaps, explain how deliverables connect to user needs and communicate how user outcomes relate to higher-level organisational goals." (source: https://www.impactmapping.org/)

Impact Mapping is a unique technique (described in a book by Gojko Adzic) which enables every organisation or team facing a new problem, a new challenge to not only find unexpected ideas but also to make sure that these ideas address those challenges instead of fulfilling other interests.
By following the steps, Impact Mapping helps find ways to experiment, innovate, and compare possible ideas by focusing on the outcome rather than the output. It gives the group the means to verify the progress the whole time - to fail fast or stop investing because they have reached their goal.

In this workshop, we will discuss and map a fictive problem. At the end of the workshop, you will know how the technique works and when to use it, how much fun such Impact Mapping can be and how creative people are when the only constraint is time :)

There are no prerequisites but curiosity and the willingness to collaborate. All information interesting to read before are on https://miro.com/app/board/uXjVMHAxTg4=/

Max nr of attendees: ~20, depending on the room size
Room: space for modelling (walls or long tables), stickies, sharpies

Impact Mapping Workshop (DE) en de

„Impact Mapping ist eine einfache, kollaborative Planungstechnik für Teams, die mit Softwareprodukten eine große Wirkung erzielen wollen. Es basiert auf dem Design von Benutzerinteraktionen, ergebnisorientierter Planung und Mind Mapping. Impact Maps helfen Entwicklungsteams und Stakeholdern, Roadmaps zu visualisieren, sie erklären wie die Ergebnisse mit den Bedürfnissen der Benutzer in Verbindung stehen und kommunizieren, wie die Ergebnisse der Benutzer mit übergeordneten Unternehmenszielen zusammenhängen." (Quelle: https://www.impactmapping.org/)

Impact Mapping ist eine einzigartige Technik (beschrieben von Gojko Adzic in einem seiner Bücher), die Organisationen oder Teams nutzen sollten, die vor einem neuen Problem, einer neuen Herausforderung stehen. Die Technik ermöglicht die am besten passenden Ideen zu finden, anstelle von den üblichen "wir haben es schon immer so gemacht". Durch die vorgegebenen Schritten stellt sie sicher, dass man sich immer auf den Mehrwert fokussiert (warum sie zum Beispiel sehr hilfreich ist, wenn man mit OKRs arbeitet).

In diesem Workshop werden wir ein fiktives Problem analysieren und abbilden. Am Ende des Workshops wird es klar sein, wie die Technik funktioniert und wann sie angewendet werden soll. Ihr werdet auch miterleben, wie viel Spaß kollaborative Arbeit machen kann, wenn wir unsere Kreativität gepaart mit unseren sonstigen Erfahrungen ausleben :)

Für die Teilnahme gibt es keine besondere Voraussetzungen, außer Wissbegierde, unternehmerisches, strategisches Denken und die Freude an Zusammenarbeit.

Max Teilnehmer: ~20 (anhängig von Raumgröße)

Benötigt werden:
- ein großer Raum um in Gruppen diskutieren zu können, ohne die anderen zu stören,
- mindestens 2 Meter für Post-It's geeignete Fläche für jede Gruppe
- 4 unterschiedliche Post-It's, Stifte

Shifting from Projects to Feedback-Based Product Development en

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 for the next six months, 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, and the developers blame product managers and designers for continuously "changing the requirements".

This talk will show that it does not need to be like this. Product development is a very creative industry with significant challenges and great rewards. Instead of seeing only problems, stress and frustration, you will hear how, even in software companies working as contractors, it is possible to enjoy the work by focusing on the really important things. We have everything we need to create better products but we need to refocus on the original goal: enabling the users to solve their job.
During the talk, we will learn how can we use known methods, techniques and 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. You will leave the session better equipped to build digital products that are more responsive to customer needs, reduce the risk of failure, promote innovation and offer fulfilment to those building them.

From The Problem To Software - a Walkthrough en

"It is not the domain experts knowledge that goes in production, it is the assumption of the developers that goes into production" This famous quote from Alberto Brandolini is unfortunately true but it also points to the right direction: we need to bring the domain knowledge into our software.
Krisztina will show you how this can be done in the day to day business, she will share her experience including the list of techniques needed to succeed in having real Domain-driven development.
This won't be a slide show, challenges, questions are welcome!

https://miro.com/app/board/o9J_lOogidA=/

DDD Methods for Day to Day Problem Solving en

(This is a hands-on lab with limited capacity)

"It is not the domain experts knowledge that goes into production; it is the assumption of the developers that goes into production". This famous quote from Alberto Brandolini is very accurate, and it points in the right direction: we need to bring domain knowledge into our decisions and our software to offer the best solution in the given context.

One of the reasons why software solutions become messy and hard to maintain is that we tend to jump to solutions before really understanding the problem. They may work out for now, but how do we ensure that they will fit in the future? This is where the paradigm of Domain-driven Design can help us out: DDD gives us the option to change our model when the business is changing. The workshop is not only for engineers but for everyone involved in product development.

In these two hours, we will dissect a business problem and experience how to solve it by using various techniques and tools in the day-to-day business. We will learn how to ensure that our decisions and implementations are driven by the Domain, which pitfalls to avoid and which principles to follow. After the workshop, every participant should have a good idea of how to start using the techniques and tools at work.

Level: advanced
Max attendees: 20 in one room