1. Architecture Who Cares?

2. Architecture The fundamental organization of a system, embodied in 1) its components, 2) their relationships to each other and to the environment, and 3) the principles governing its design and evolution. (from ANSI/IEEE 1471-2000)

3. Architect Establishes the basic structure of the system, defining the essential core design features and elements that provide the framework for all that follows. (Wikipedia)

4. “What do you do?” “I’m a (fill-in-the-blank) architect.” Enterprise Architect, Infrastructure Architect, Business Architect, Network Architect, Solutions Architect, Sanitation Architect, blah, blah, blah, …

5. Business Architecture The documents and diagrams that describe the architectural structure of that business.

6. Business Architect Develops the documents and diagrams which play a key role in shaping and fostering the continuous viability of the business (improvement, transformation, innovation) Acts as a change agent for the process. NOTE: Business needs should drive technology decisions (not the other way around).

7. Skills Deep business domain knowledge Broad technology knowledge Cross-functional process experience Methodology skills Transformation talents Problem Solver Effective communicator Good people skills

8. Sometimes, stakeholders don’t really understand what they need …

9. Sometimes, engineers underestimate the stakeholders ability to understand …

10. No silver bullet Not just 1 right business model diagram or template. Portfolio of models and documents that speak to different audiences to address their issues and opportunities.

11. Some documents Diagrams Requirements Process Flows Roadmaps Priority Matrixes Current state vs. Future state Cost / Benefit Bid sheet …

12. BYU Triangle Business Solutions TechnologyData

13. Current State vs. Future State

16. Cost/Benefit

18. A few more thoughts PAGs Understand your constraints “Come now, we are men of action” Good Strategy Bad Strategy by Richard Rumelt Bite-size Chunks