Laws for Organization Architects


1. Thou shalt always revisit the architecture axiom - Clear and consistent responsibilities powers all great architectures 2. Thou shalt be kept accountable for all architectural decisions 3. Above all, do no harm 4. Thou shalt strive to build a learning organization and culture 5. Thou shalt make consistent and balanced decisions throughout the organization 6. Thou shalt never default to silver bullets or magic 7. Thou shalt support and maintain functional and business data building blocks and communicate these to projects 8. Thou shalt never micromanage project decisions		Architect categorization used here We use Organizational Architect to classify software architects which are responsible for the organizational context, i.e. across projects and products. These architects are commonly called Chief Architects, Enterprise Architects, Solution Architect, System Architects, Integration Architects or Infrastructure Architects. We use Project Architect to classify architects who work on a specific project and within a project scope. These architects are commonly called Solution architects, Software architects or Tech leads. We use Product Architect to classify architects who work on a specific product and whithin the product lifeline scope. Commonly used names for such architects are: Chief Product Architect, Product Architect, System Architect, Sub-system Architect, Build Architect or Tech leads.

|