Most of us have been working with some kind of legacy systems with lots of technical debt. How do we improve the codebase without The Big Rewrite and avoid creating yet another spaghetti monster? That’s what this workshop is about.

In this workshop, we will work together on a legacy system. We will approach the problem by creating a new, clean, and truly object-oriented model with modularity, cohesion, and testability in mind. We will introduce the model into the existing application in a secure manner, leaving ourselves an option to withdraw changes at any point in time. Fully automated tests will make sure that both models produce consistent results. EventStorming will help us set priorities right and understand the business impact of our changes.

Finally, we’ll get a solid, clean, and object-oriented code aligned with the company's goals and agile software development best practices.

During this workshop we will be working with a C4 model. If you don’t know it, do not worry, it’s simple enough to master in 15 minutes. This workshop is technology agnostic, but we will focus on the backend architecture and services.

Surprising as it is, this workshop can also help Product Owners and Managers to communicate with their teams. At least that’s the experience we’ve had so far.

NEW in 2020: How should one handle vague/unclear/huge projects? How to get into individual brainstorming mode and think unthinkable?

NEW in 2020: Distinguishing between good and bad procrastination and the practical session of group de-procrastination.

Many companies grow ad-hoc. Others blindly copy the “Spotify Model” of team design. Not surprisingly, with every developer added, they face a significant decline in performance.

Every system has an architecture, whether accidental or intentional, and regardless of whether it was put in place by a nominated architect or whether it emerged from the decisions and discussions of a team. All too often the focus of what is often described as architecture is centred around a specific set of platform technologies, which forms only one part of the set of concerns an architecture should. And all too often architecture is seen as a separate concern from development process, whereas the two are intertwined — what you build is influenced by how you build it, and vice versa.

This course looks at the relationship between Agile processes and good architecture, taking in development process models, architectural styles, requirements techniques, sufficient modelling techniques, design patterns and testing practices. This course includes a number of practical exercises so that attendees can see how the different activities fit together.

Software Craftsmanship is at the heart of this course. Throughout, you will learn about the Software Craftsmanship attitude to development and how to apply it to your workplace.