The Role Of The Architect In Turbulent Times


Published on

Presentation delivered at Microsoft Architect Cafe in August 2009; by Miha Kralj

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The Role Of The Architect In Turbulent Times

  1. 1.
  2. 2. The role of the Architectin Turbulent Times<br />MihaKralj<br />Sr. Architect<br />Microsoft Corporation<br />Session Code: ARC207 <br />
  3. 3. Architecture Impetus<br />You can’t build a sky rise the way you build a dog house…<br />Booch, SD’99<br />Architectural leadership always comes from the least expected direction…<br />Unknown<br />Architecture??? We are in recession,who needs architecture now!<br />CIO of undisclosed company<br />
  4. 4. Architecture is the translation of intent into technology<br />Architecture: Raison d&apos;être<br />Technology<br />Business<br />
  5. 5. Architecture is the translation of intent into technology<br />Architecture: Raison d&apos;être<br />Technology<br />Business<br />Aesthetics<br />
  6. 6. Architecture is the translation of intent into technology<br />Architecture: Raison d&apos;être<br />Technology<br />Business<br />Aesthetics:Judgment of sentiments and taste<br />Aesthetics<br />
  7. 7. Architecture: Raison d&apos;être<br />Business desires the right<br />Function<br />Technology<br />Business<br />Aesthetics<br />
  8. 8. Architecture: Raison d&apos;être<br />Technology seeks the rightStructure<br />Business desires the right<br />Function<br />Technology<br />Business<br />Aesthetics<br />
  9. 9. Architecture: Raison d&apos;être<br />Technology seeks the rightStructure<br />Business desires the right<br />Function<br />Technology<br />Business<br />Aesthetics requires the rightAppearance<br />Aesthetics<br />
  10. 10. Architecting process<br />Design<br />Requirements<br />Analysis<br />Design<br />Conscious effort to create something that is both functional and aesthetically pleasing<br />All architecture is design.<br />Not all design is architecture.<br />
  11. 11. Who Does What Best?<br />Business Analyst<br />DeveloperIT Professional .<br />Architect<br />Design<br />Requirements<br />Analysis<br />
  12. 12. Architectural Levels<br />Design all things by considering them in their larger contexts<br />An enterprise in an industry<br />A system in an enterprise<br />A component in a system<br />An object in a component<br />Put the large rocks in the place first<br />
  13. 13. Scope of Architectural Decisions<br />Architecture is the set of decisions that cannot be delegated without compromising overall system objectives<br />product family architecture decisions<br />decisions optimized over the whole, making tradeoffs and compromises across the products for the overall good of the whole<br />product architecture<br />decisions<br />Product family scope<br />Product B scope<br />Product A scope<br />Component scope<br />decisions made here are tuned to product A<br />
  14. 14. Enterprise Architecture - Definition<br />Enterprise Architecture<br />Addresses Enterprise objectives:<br />Encompasses:<br />Application Architecture<br />Consistency, Integration, Interoperability, Security<br />Infrastructure Architecture<br />Flexibility to make, buy or outsource IT solutions<br />Information Architecture<br />Reuse across applications, solutions and product families<br />Business Architecture<br />EA has Enterprise-wide scope and crossesintra-organizational boundaries<br />
  15. 15. Value<br />EA = BA + EWITA<br />Enhance Business/IT Alignment<br />EA = EWITA Enhance Value Management<br />EA = TA<br />Reduce IT cost and enhance operations<br />Scope<br />Evolution of Enterprise Architecture<br />
  16. 16. Goal of an Architect<br />Get the Architecture Right<br />Right Direction: Architectural Vision and Strategy<br />Right Focus: Architectural Requirements and Prioritization<br />Right Solution: Architecture Specification<br />Get the Architecture Used Right<br />Get the Architecture used (at all)<br />
  17. 17. Architect responsibilities<br />What it really is:<br />What you think the job is:<br />Technical work<br />Solving interesting problems<br />Technical work<br />Touchy-feely stuff<br />Applying design patterns<br />Organizational politics<br />Technology choices, system design<br />Getting participation<br />Building consensus<br />Non-technical work<br />
  18. 18. The Main Activities of an Architect<br />What an Architect really does?<br />Think, Analyze<br />Present, Meet, Teach, Discuss<br />Listen, Talk, Walk around<br />Test, Integrate<br />Design, Brainstorm, Explain<br />Write, Consolidate, Browse<br />Assist with risks, WBS, schedule<br />Read, Review<br />How do you explicitly measure success of these tasks?<br />GerritMuller, “The Role and Task of the System Architect”,<br />
  19. 19. Architect Competencies<br />Technical Competencies<br />Business<br />Competencies<br />Personal Competencies<br />Leadership<br />Technology in Breadth<br />Organizational Dynamics<br />Communication<br />Strategy<br />Technology in Depth<br />Process and Tactics<br />
  20. 20. Split of the Role in the Hard Times<br />Business Analyst<br />Project Manager<br />Strategy Advisor<br />Development Lead<br />Testing Lead<br />Operations Lead<br />Technical Competencies<br />Business<br />Competencies<br />Personal Competencies<br />Leadership<br />Technology in Breadth<br />Organizational Dynamics<br />Communication<br />Strategy<br />Technology in Depth<br />Process and Tactics<br />
  21. 21. Split of the Role by Domain Focus<br />EA<br />Solution Architecture<br />(Infrastructure, Information)<br />Technical Architecture<br />(Software, Application, System)<br />
  22. 22. Split of the Role by Domain Focus<br />Business Analyst<br />Project Manager<br />Strategy Advisor<br />EA<br />Solution Architecture<br />(Infrastructure, Information)<br />Development Lead<br />Testing Lead<br />Operations Lead<br />Technical Architecture<br />(Software, Application, System)<br />
  23. 23. Shifting the Focus<br />Diminishing Old Priorities<br />New Projects – due to the overwhelming amount of internal optimization new projects are few and far apart. <br />Large-scale SOA projects – With widespread failures of large SOA projects architects are reconsidering their approach to SOA<br />Web 2.0 projects – The experiments on if this technology paradigm is viable is deemed non mission-critical.<br />Server consolidation – the lifetimes of servers is extended thus reducing the amount of consolidation projects<br />
  24. 24. Shifting the Focus<br />Emerging New Priorities<br />Optimization of current portfolio– How to leverage Company’s assets in a struggling economy (do more with less)<br />Cost Reducing Programs – Programs that look at cost reductions are becoming a major property for architects <br />Mergers and Acquisitions (M&A)– Many pre- and post-M&A projects will occur during the recession time<br />Compliance– New regulations will emerge to control all aspects of how IT operates <br />Value Add Customer-facing projects – Furthering the reach of the company past traditional methods to add to the value chain<br />
  25. 25. Four Key Architectural Imperatives<br />What to do in the times of uncertainty<br />Align – Find direct links to business imperatives.<br />Optimize– Do more with what you have<br />Externalize – Move IT assets outside of the IT operating environment, if they do not add value<br />Consolidate – Reduce unnecessary redundancies<br />
  26. 26. Align the Architecture<br />Assessments<br />Key Metrics<br />Repeatable and consistent assessments should drive how decisions are made, and they must illustrate how architectural trade-offs occurred. <br />Instead of defining IT-specific metrics, architecture organizations need to operate more like a business. By doing so, they need not only to demonstrate their effectiveness, but also to quantify it.<br />Define the assessment metrics for all aspects of your work <br />Redefine how you are measured and evaluated<br />
  27. 27. Link the Architecture <br />Architecture Management<br />Requirements Management<br />Architecture management should link into the standard processes, such as application portfolio management and Project Management Office processes.<br />Capturing functional and nonfunctional requirements in reusable ways will help align architectures to the business and drive both the functionality and the architecture.<br />Prove the value of architecture through PMO<br />Align with business with the right requirements capturing process<br />
  28. 28. Optimize the Architecture<br />ALM Management<br />Portfolio Management<br />ALM improvements can include process optimizations to streamline efforts, new tools to automate and accelerate application development, and key information-gathering points to support architecture efforts and quantify business value.<br /> Reviewing the IT portfolio of applications will allow architects to either inventory existing systems or review the systems that have been cataloged.<br />How can you improve the ALM tools, process or skills?<br />What Solutions bring the most value and return?<br />
  29. 29. Optimize your Tools and Solutions<br />Optimizing Solutions<br />Development tooling<br />With a wave of new innovations in social computing, context-aware architectures, cloud-based architectures, and SaaS, there are ways to introduce lower risk, cost, and support for your company.<br /> Optimizing the tooling that is used in the actual development and architectural planning is essential for companies. In times of slowed project work, it is optimal to retool.<br />Find the low-cost refactoring ideas and approaches.<br />Are you using the right tools for the architecting process?<br />
  30. 30. Consolidate your IT Assets<br />IT Services<br />IT Infrastructure<br />Collaboration, VOIP, e-mail, business intelligence, portals, system monitoring, and project-management systems are all IT services that can be streamlined by creation of standards or consolidation of multiple vendors.<br /> The hardware backbone of an enterprise often is the first to be consolidated with virtualization solutions. While it is easy to virtualize, there is careful planning needed, as it could lead to the same problem that we have with server sprawl.<br />What redundant IT Services can you find and consolidate?<br />What infrastructure elements are ready for virtualization?<br />
  31. 31. Consolidate your IT Assets<br />Process Management<br />Solution Architectures<br />Process management can be a valuable exercise to consolidate disconnected and redundant processes. This streamlines your architectural efforts by providing repeatable and predictable measurements.<br />Companies often find redundancies in solutions across LOBs or functional areas. Consolidating solutions will be key to lowering costs and complexity within the organization.<br />What processes are fat, long and unnecessary?<br />How much cost-reduction can you bring with consolidation?<br />
  32. 32. Invent New Usage of Current Technology<br />Use technology NOT as originally intended<br />Redefine where the applied cutting edge really is<br />Go beyond prescribed scenarios and personas<br />Are you using technology the same way as your competition?<br />Improve Customer Experiences<br />Experience is more important than functionality<br />If you don’t improve the experience, someone else will!<br />Eliminate negative, tedious or hard-to-understand parts<br />How do you get dissatisfied users to talk before they walk?<br />
  33. 33. Render Your Own Cash Cow Obsolete<br />Is there a single product/service that generates the majority of income?<br />Create new Cash Cows out of Stars and Question marks (BCG)<br />Anyone’s Cash Cow can be (and will be) stolen<br />How do you reposition your own current Cash Cow?<br />Learn to Fail Fast<br />Plan ahead and get the advantage of unavoidable future<br />Don’t refuse to accept failure; Invest in the next success<br />If horse is dead, GET OFF!<br />Is your product, service or engagement slowly failing?<br />
  34. 34. Systematically Look Into the Future<br />Focus on the NEW big picture<br />Look for trends, patterns and new disruptors<br />Technological changes can redefine the entire industries<br />What changes can you identify that might yield an opportunity?<br />Solve Predictable Future Problems Today<br />Shift from Crisis Management to Opportunity Management<br />Most of Future Issues are predictable and avoidable<br />Anticipate, Plan and Pre-empt<br />What problems can you eliminate before they happen?<br />
  35. 35. Co-create the Future with your Customers<br />Reward and stimulate customer innovation<br />Foster collaborative research and creation<br />Customers will help you design future products with THEM in mind<br />Do customers send you their innovate ideas to implement?<br />Create Strategic Alliances<br />Cooperation and Competition are merging (Coopetition)<br />Alliances are partnerships of equal players<br />Strategic alliances tend to create advantages for all<br />Which alliance would benefit your ecosystem?<br />
  36. 36. question & answer<br />
  37. 37. Required Slide<br />Speakers, <br />TechEd 2009 is not producing <br />a DVD. Please announce that <br />attendees can access session <br />recordings at TechEd Online. <br /><br />Sessions On-Demand & Community<br /><br />Microsoft Certification & Training Resources<br /><br />Resources for IT Professionals<br /><br />Resources for Developers<br /><br />Microsoft Certification and Training Resources<br />Resources<br />
  38. 38. Required Slide<br />Complete an evaluation on CommNet and enter to win!<br />
  39. 39. Required Slide<br />© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.<br />The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.