Book Image

Agile Technical Practices Distilled

By : Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia
Book Image

Agile Technical Practices Distilled

By: Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia

Overview of this book

The number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, as well as most methodologies associated with it. You’ll begin by discovering how driver-navigator, chess clock, and other techniques used in the pair programming approach introduce discipline while writing code. You’ll then learn to safely change the design of your code using refactoring. While learning these techniques, you’ll also explore various best practices to write efficient tests. The concluding chapters of the book delve deep into the SOLID principles - the five design principles that you can use to make your software more understandable, flexible and maintainable. By the end of the book, you will have discovered new ideas for improving your software design skills, the relationship within your team, and the way your business works.
Table of Contents (31 chapters)
Free Chapter
Section 1
Section 2
Section 3
Section 4
Chapter 21
License: CyberDojo

Chapter 23

EventStorming by Alberto Brandolini

Everybody is a master in his own silo.

– Alberto Brandolini

We have seen that building a software system is an activity with the goal of automating the information flow to support a business’s value stream. This means that a software system should exist to support the business processes and should be shaped around them, be at their service, optimize them, and make them more effective.

It is definitely easier said than done for several reasons. One of the main reasons that we’ve repeatedly seen in past clients is the lack of a shared understanding of their value stream. Only a few select people have an idea (usually not up to date) of the whole high-level picture, while others are hermetically separated into departments where they can be productive with the minimum amount of knowledge possible.

This overview of EventStorming (and the diagrams) borrows from Alebrto Brandolini’s book...