Presentation is loading. Please wait.

Presentation is loading. Please wait.

3/31/2017 6:37 PM © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.

Similar presentations


Presentation on theme: "3/31/2017 6:37 PM © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered."— Presentation transcript:

1 3/31/2017 6:37 PM © 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. 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.

2 Practical Architecture: Aligning Business Strategy with IT Vision
Tech·Ed  North America 2009 3/31/2017 6:37 PM Practical Architecture: Aligning Business Strategy with IT Vision Franco Rothner Solution Specialist Microsoft SA Session Code: ARC301 © 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. 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.

3 Agenda Why architect The process of architecture
Identifying the right people - toolsets Aligning and Delivering Architecture - Frameworks and models Organizational Insight - Understanding your organization Do’s and Dont’s

4 Definition - Architect
Architecture is a business in which technical knowledge, management, and an understanding of business are as important as design. the developer of the structure of a computer system or program The enterprise architect handles business-related software decisions that frequently can involve multiple software systems within an organization, spanning several projects teams, and often at more than one site. The architect makes high-level design choices much more often than low-level choices. In addition, the architect may sometimes dictate technical standards, including coding standards, tools, or platforms, so as to advance business goals rather than to place arbitrary restrictions on the choices of developers.

5 Why do I need an Architect
The Winchester House -

6 No architectural Blueprint Exists
Winchester House Facts 38 Years of Construction 147 Builders 0 Architects 160 Rooms 40 Bedrooms 6 Kitchens 2 Basements 950 Doors Cost $5,5million Winchester House Facts 65 Doors to blank walls 13 Abandoned Staircases 24 Skylights in the floor No architectural Blueprint Exists

7 Interpretation of the Objective
Tuscany - Business Tuscany - IT

8 Evolution of Enterprise Architecture
EA = TA Reduce IT cost and enhance operations EA = EWITA Enhance Value Management EA = BA + EWITA Enhance Business/IT Alignment Value Scope

9 Challenges Business CIO Operations CFO I know what my business does...
How long is it going to take? Why do you want to change it, we have been doing things like this for years and it works Show me how this will effect the bottom line... Isn’t that an IT role... Let me decide on what is the right direction... What you are proposing is impossible... How did you get to that number? Surely the process is optimised... How must I know, I was in finance before this job.... You want to get rid of Unix? Let me worry about the budgets... We cannot do this improve this any further... You want to pay him what???!!!! The mainframe will always be here...

10 The Process of Architecture

11 Architecting Process Design Requirements Design Analysis
Conscious effort to create something that is both functional and aesthetically pleasing All architecture is design. Not all design is architecture.

12 Design all things by considering them in their larger contexts
Architectural Levels Design all things by considering them in their larger contexts 1 Financial Services 2 Retail Banking Industry Enterprise in an industry System in an Enterprise Component in a system Object in a component 1 3 Procurement 4 2 Identity Management 3 5 User 4 5 Put the large rocks in the place first

13 Resource Availability
Architecture focus Business Projects Architecture New / New Process Priority Data/Information Resource Availability Budget Application Existing Technology New Additional IT Projects

14 Objectives of an Architect
Creating the right Architecture Vision and strategy Required architecture and priorities Specifications and standards Using the architecture Governance and alignment Scorecards and measurement Architecture Adoption through deployment Governance and feedback Value calculation and ratification

15 The role of an architect
Business IT Organization Mission Providing Banking Services to unbanked South Africa Provide people, process and technology solutions to enable banking the unbanked in South Africa Providing banking services to 40% of all unbanked South Africans over the next 10 years by providing affordable banking in the medium most suited. Architect, Plan, Design and Build the systems to cater for 12 million users within the next 10 years with system availability of 90% Organization Vision Provide access to the unbanked South African market through delivery of low cost banking services through retail bank branches, ATM and cellular phone channels. Systems for branch and cellular phone banking will be delivered in the Plan, Build Run Model and will ensure 90% availability through appropriate HA and DR policies Operating Model

16 Mapping IT To Business Business IT IT How?
1. Improve customer satisfaction by 15% in next 12 months by reducing customer wait time in branches. Ensure branch systems service level SLA at 90% over the next 12 months Remove single points of application failure. Remove single points of hardware failure. Address network SLA and guarantee 95% availability 2. Grow cell phone banking from to users in 18 months. Ensure cell phone banking functionality is available Is application multi platform? Ease of use of application? Reliability of the application? 3. Improve the turnaround time for customer loan applications from 12 hours to 1 hour. Straight through electronic processing of application will reduce processing time Workflow scanned documents with electronic application. Understand approval process and messaging requirements 4 Reduce Operational Cost Reduce infrastructure, operational and licensing cost. Virtualize Consolidate Optimise

17 Accountability and delivery
CIO Scorecard Reduce Cost CTO Scorecard Reduce Cost Architecture Reduce Cost Deploy/Build Operations Reduce Cost Reduce Cost

18 Roles and Responsibilities of Architect
The RACI model is a powerful tool utilized to define roles and responsibilities. In general, you match up roles and responsibilities with processes. The tool is extremely useful when rolling out a new change management program, or just uncovering the processes that make your organization function and identifying the participation in those processes R Responsible – owns the project/problem. A To whom “R” is Accountable who must sign off (approve) on the work before it is effective. C To be Consulted – has information and/or capability necessary to complete the work. I To be Informed – must be notified of the results but need not be consulted. T - Time Activity Responsible Accountable Consulted Informed By when Finalize strategic middleware providers HOD – Technology Architecture CTO Operations Support Development Security CIO COO Partner Manager 1 June 2010

19 Delivering Architecture - Frameworks and models

20 Frameworks The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture which provides a comprehensive approach to the design, planning, implementation, and governance of an enterprise information architecture. The architecture is typically modelled at four levels or domains; Business, Application, Data, Technology. A set of foundation architectures are provided to enable the architecture team to envision the current and future state of the architecture The Zachman Framework is a framework for enterprise architecture, which provides a formal and highly structured way of viewing and defining an enterprise

21 Governance Model

22 Identifying the right people - toolsets

23 Responsibilities of the Architect
Perception Technical Solving interesting technical problems Using different design patters Choosing technology Non Technical Related Work Reality Non Technical Related Work Surviving the politics and hidden agendas Ensuring buy in and participation Foster support and agreement Technical

24 Who Does What Best? Requirements Design Analysis Business Analyst
Developer IT Professional . Architect Requirements Analysis Design

25 Skills and Attributes - Roles
Architect Roadmap and Planning Design Deploy Maintain High Med Low C L P C L P C L P C L P C L P

26 Individual Competencies
Business Organizational politics Strategy Process and tactical approach Timing Personal Leadership Communication Perseverance Ethics EQ IQ Technical Technology Strategy Technology MBA – MCA Infrastructure Technology Detail/MCA

27 Identifying Architectural candidates
Myers-Briggs (MBTI Indicator) The Myers-Briggs Type Indicator (MBTI) assessment is a psychometric questionnaire designed to measure psychological preferences in how people perceive the world and make decisions. Fundamental to the Myers-Briggs Type Indicator is the theory of psychological type as originally developed by C. G. Jung. Jung proposed the existence of two dichotomous pairs of cognitive functions: The "rational" (judging) functions: thinking and feeling The "irrational" (perceiving) functions: sensing and intuition The 4 Dichotomies Extraversion Introversion Sensing iNtuition Thinking Feeling Judging Perceiving

28 Architect Profiles Why is it so difficult to find?
What should I be looking for?

29 Organizational Insight - Understanding the one you are in

30 Organizational Structure – friend or foe
IT as a cost centre IT as a necessary evil Strategic Partner CEO CFO COO CIO CTO Architecture IT Operations Development CEO CFO COO CIO CTO Architecture IT Operations Development Enable Business Reduce Cost SLA Uptime CEO CFO CIO CTO Architecture IT Operations Development COO

31 Practical Architecture Tips

32 Do’s and Don’ts Communication is paramount.
Executive and Business buy in for architecture is a necessity. Governance structure is important – Prescriptive vs. Participative Keep it relevant and delivery focussed. Get involved up front. Measure, Measure and Measure. Something does not exist until it is documented.... Effective lobbying saves a lot of time Understand your audience. Hire the right people for the right jobs. Be tough, bit not ignorant. Become the trusted advisor of the CEO and CIO. Don’t forget the legacy

33 In conclusion What is Architecture Why we architect
The process of architecture and how we align business objectives Identifying the right people Looking at architectural toolsets Understood organizational structure Covered some high level do’s and don’ts

34 question & answer

35 10 pairs of MP3 sunglasses to be won
Required Slide 10 pairs of MP3 sunglasses to be won Complete a session evaluation and enter to win!

36 Resources Required Slide Speakers, www.microsoft.com/teched
TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings from Tech-Ed website. These will only be available after the event. Resources Tech·Ed Africa 2009 sessions will be made available for download the week after the event from: International Content & Community Microsoft Certification & Training Resources Resources for IT Professionals Resources for Developers

37 Required Slide 3/31/2017 6:37 PM © 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. 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. © 2007 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. 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.


Download ppt "3/31/2017 6:37 PM © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered."

Similar presentations


Ads by Google