Get the latest tech news

Architectural Retrospectives: The Key to Getting Better at Architecting

The purpose of an architectural retrospective is to use experience to help the development team improve their architecting skills and their way of working as they make architectural decisions. This is different than traditional architecture reviews which are focused on improving the architecture.

Designing a software architecture is no exception: if you never stop to examine how you make decisions, your results may reflect systemic biases in your ways of looking at the problem. Retrospectives are a key element of many agile software development approaches for a good reason: they provide time and psychological space for the team to reflect on how it can improve its way of working. But architectural retros have great pay-offs: they can uncover unspoken assumptions and hidden biases that prevent the team from making better decisions.

Get the Android app