Architectural Retrospectives differ from Architectural Reviews by focusing not on evaluating and improving the architecture itself, but on examining and improving how the team went about creating the architecture.
One challenging thing about retrospectives is to not spend too much time talking about the decisions themselves. The specific decisions are not the focus of a retrospective.
Teams must also be careful not to turn retrospectives into 'blame sessions'. Instead, they need to look for biases that may be impairing their ability to make good decisions.
An oft-cited definition of insanity is doing the same thing and expecting different results, but that's exactly what teams who never examine their way of working do.
#architectural-retrospectives #software-architecture #decision-making #team-dynamics #continuous-improvement
Collection
[
|
...
]