Alberto Brandolini

Alberto Brandolini can model every business domain, given enough space, a paper roll and an unlimited source of colored sticky notes (with a larger stock of orange ones). His contributions to the community include EventStorming, Model Storming and, more notably, the Bullshit Asymmetry Principle.

Alberto Brandolini is an IT Professional that gets bored doing things in the same old way. This led him into unexplored areas of Domain-Driven Design, Lean and Agile Software Development, learning and change management, where he likes to bring apparent chaotic fuzziness and a comic-like visual touch. An active consultant in software product development, he also run his company Avanscoperta.

He’s frequently invited as a speaker in many conferences in Italy (where he’s based) and around Europe.

Talk

Transactions Redefined

Abstract coming soon.

Two day pre-conference workshop, Jan 31 - Feb 1 2017

EventStorming Master Class

EventStorming is a workshop format that promotes collaboration between different disciplines in order to sove business problems in the most effective way.

In this two days format we’ll experience the different formats, working around real business problems. We’ll take into account the different perspectives (including the facilitator) in a process that spans large scale discovery, to leverage collaborative design. We’ll experience the how, and we’ll discuss the why.

Agenda

Day 1

EventStorming as a discovery tool.

• Quick kick-off: where are we and where we want to go.
• Real world Big Picture EventStorming, mastering complexity and unknwons in large scale modelling.
• Managing conflicts, higlighting risk, and the problems really worth solving. The facilitator’s toolbox revealed.
• Improving our process exploring motivations of different actors.
• The Change agent’s perspective: why it’s going to be hard even when improvement is obvious, and how to deal with stalemates.
• Everything’s connected: lean & Kanban, complexity and organization limits.
• Working with startups vs. working with established companies.
• EventStorming as a platform for problem solving.
• ModelStorming: modelling everything without a clue (and yet deliver).

Day 2

Using EventStorming to design a system.

• Design-Level EventStorming: leveraging collaborative modelling to sketck bullet-proof model quickly.
• A different perspective on software design: the picture that explains everything. Make policies explicts. Discover aggregates. Design around the bottleneck. Blending User Experience Design and Service design into software design.
• Triggering bullet-proof design with visible state. The transaction illusion.
• From sticky notes to working software. When to go for a sophisticated architecture,