How do you get Value from Architecture? - PowerPoint PPT Presentation

how do you get value from architecture n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
How do you get Value from Architecture? PowerPoint Presentation
Download Presentation
How do you get Value from Architecture?

play fullscreen
1 / 32
How do you get Value from Architecture?
197 Views
Download Presentation
elia
Download Presentation

How do you get Value from Architecture?

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. How do you get Value from Architecture? Establishing an Architecture Practice: Real World Experiences

  2. http://jkbutcher.com Justin Butcher on being effective as an Architect in 2010

  3. au.linkedin.com/in/justinbutcher Justin Butcher on being effective as an Architect in 2010

  4. This presentation will explain: • Definitional Stuff • Doing better architecture • Building an architecture practice • Measuring architecture value in square millimeters. • Why women make better architects. • Why knowledge of technology can make you a bad architect. • The ISO Standard for architecture description. • How the blind men and the elephant explain architecture. • How my current team grew from 5 to 20 in 12 months. Justin Butcher on being effective as an Architect in 2010

  5. What is architecture? Justin Butcher on being effective as an Architect in 2010

  6. Justin Butcher on being effective as an Architect in 2010

  7. IEEE Definition of Architecture: • Architecture: The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution. Justin Butcher on being effective as an Architect in 2010

  8. ISO 42010 – a standard definition for architecture description (for software intensive systems). Justin Butcher on being effective as an Architect in 2010

  9. ISO Standard 42010 – Architecture Description An [Architecture Description] shall identify the stakeholders considered by the architect in formulating the architectural concept for the system. At a minimum, the stakeholders identified shall include the following: • Users of the system • Acquirers of the system • Developers of the system • Maintainers of the system Justin Butcher on being effective as an Architect in 2010

  10. ISO Standard 42010 – Architecture Description An AD shall identify the concerns considered by the architect in formulating the architectural concept for the system. At a minimum, the concerns identified should include the following: — The purpose or missions of the system — The appropriateness of the system for use in fulfilling its missions — The feasibility of constructing the system — The risks of system development and operation to users, acquirers, and developers of the system — Maintainability, deployability, and evolvability of the system Justin Butcher on being effective as an Architect in 2010

  11. How can architects provide compelling value in Canberra in 2010? Justin Butcher on being effective as an Architect in 2010

  12. Are you a true believer? Justin Butcher on being effective as an Architect in 2010

  13. Justin Butcher on being effective as an Architect in 2010

  14. More meetings, more email, what a waste of time, I can’t get any work done! Justin Butcher on being effective as an Architect in 2010

  15. Justin Butcher on being effective as an Architect in 2010

  16. I have spent several years so far and more to come looking at this and there seem to be several things that do distinguish better architects, and technical prowess is actually a negative for many. From my research, basically, there seems to be a set of experience that is necessary, including a range of roles and exposure to different aspects of business and development (in the wider sense not just SDLC) and at least 10 years/10,000 hours of deliberate practice/relevant activity. There also seems to be several personality traits that are critical such as being creative, resilient, open-minded and passionate (which isn’t a common grouping at all). 
Then there are competencies/capabilities, of which eight seem to matter. Number 1 is communication, communication, communication. After that business relationship, analysis, problem solving, situational politics, being visionary, conceptualisation, and being able to take the middle ground/translate between groups. 
I looked at other things and asked many architects what else mattered but nothing, except GMA (general mental aptitude) appears to really make a consistent difference. EQ (emotional intelligence) might but it is difficult to consistently measure and some of what I found is included within some EQ definitions. (Keith Frampton) Justin Butcher on being effective as an Architect in 2010

  17. 80% Communication Justin Butcher on being effective as an Architect in 2010

  18. Good communication won’t happen by itself • Edward Tufte Justin Butcher on being effective as an Architect in 2010

  19. Have your elevator pitch ready at all times! Justin Butcher on being effective as an Architect in 2010

  20. How do you measure success in architecture? Justin Butcher on being effective as an Architect in 2010

  21. Justin Butcher on being effective as an Architect in 2010

  22. Picture size Justin Butcher on being effective as an Architect in 2010

  23. Professionalism Justin Butcher on being effective as an Architect in 2010

  24. Dollars Justin Butcher on being effective as an Architect in 2010

  25. Risks and benefits Justin Butcher on being effective as an Architect in 2010

  26. EQ: emotional intelligence - the five domains: 1. Knowing your emotions. 2. Managing your own emotions. 3. Motivating yourself. 4. Recognising and understanding other people's emotions. 5. Managing relationships, ie., managing the emotions of others. Justin Butcher on being effective as an Architect in 2010

  27. Daniel Goleman on EQ versus IQ Justin Butcher on being effective as an Architect in 2010

  28. Target the trouble-makers Justin Butcher on being effective as an Architect in 2010

  29. Empathy: • 1. Full attention and listening • 2. Body language and movement in sync • 3. Having a good time Justin Butcher on being effective as an Architect in 2010

  30. Conway’s Law Justin Butcher on being effective as an Architect in 2010

  31. http://c2.com/cgi/wiki?PrematureOptimization http://en.wikipedia.org/wiki/Inner-platform_effect Justin Butcher on being effective as an Architect in 2010

  32. Goleman again… Justin Butcher on being effective as an Architect in 2010