It is relativility easy to see an architecture error when the project is over. X gave us security problems, or Y gave us a lot of extra work. These are caught in the retrospectives, but it would be nice to catch them earlier.

We are planning on carrying out architecture reviews before the coding starts.

One way is just to get the architect to present the project and see if we can find flaws in the design. 

Does anyone have a more structured approach, maybe with a "Have you thought of" or "How are you going to do" check list.

I was thinking of something like:

* Security
* Logging
* Data Access
* Deployment
* Upgrading