Complex software projects are often late, have quality problems and don't deliver all that was promised. Often such problems are the result of an inadequate or inappropriate software architecture.

Software architecture reviews are a tool that help reveal architectural risks and strengths as well as uncover unidentified issues that need to be addressed. Sometimes the biggest risks are technical ones. And other times, the biggest risk is that too much attention has been placed on the technical architecture to the exclusion of other essential factors.

This talk reflects on lessons learned from preparing for, presenting, and conducting architecture reviews. I'll discuss what to avoid, what information to seek, and how to effectively resolve issues.