We make decisions all the time in software - our architectures are the sum of them; both conscious and unconscious. Yet we have so little awareness about what decisions are and how we decide. This is not only the source of great friction and waste, it is leading to terrible outcomes for our software.
In this talk I’ll describe what architectural decisions are, and the different ways that we approach them (individually and collectively) making clear the pros and cons of each. I’ll then compare them all, describing the ideal characteristics of a decision-process for modern software development.
As a consequence of this talk not only will you be able to decide better as an individual, you will also be able to diagnose failings in your group decision processes and resolve them.
A Tech Principal at Thoughtworks, Andrew specializes in domain-driven design, org design, software and systems architecture, agile delivery, build tools and automation.Andrew is also an author and trainer for O’Reilly. They’ve written one book about facilitating software architecture and one chapter about implementing the Accelerate/DORA four key metrics. They also run regular online training sess...