Architectures in general can and should be assessed for several reasons including regulatory requirements. This is true for software architectures as well, especially for software in highly regulated industries such as Finance, Healthcare, Government, etc... As we adopt Lean principles and practices, what are the implications on architecture assessments? Is a particular Lean principle more important than other in the context of software architecture assessment? For example the Lean principle of eliminating waste from processes. How can a software architecture be assessed for waste? Surely, identifying and eliminating waste from software architectures is more optimal scenario than eliminating waste from implemented systems.
Similarly, other Lean principles such as automating essential non value-add elements can also be used as measures for assessing software architectures from a Lean perspective. A set of software architecture assessment guidelines, based on Lean principles as assessment measures is needed. Adoption of architecture driven software development will not yield good results for Lean projects unless software architectures are assessed and certified as "Lean Architecture".
I am planning on creating guidelines for "Software Architecture Assessments Using Lean Principles"