Laws for Project Architects


1. Thou shalt never forget that your day is 80% communication and 20% technology 2. Thou shalt strive to create a learning culture 3. Thou shalt never default to silver bullets or magic 4. Thou shalt strive to find and understand your limitations 5. Thou shalt always be ahead of the project and know the risks and challenges before they arrive 6. Thou shalt make consistent and balanced decisions throughout the project 7. Thou shall always revisit the architecture axiom - Clear and consistent responsibilities powers all great architectures 8. Thou shalt lead by example 9. Thou shalt sit and work together with the team - Thou art an integrated part of the team 10. Thou shalt be hands on		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.

|

| |