Rejuvenating Architecture Governance in a Redesigned Organization

1,015 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,015
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
55
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Rejuvenating Architecture Governance in a Redesigned Organization

  1. 1. January 28, 2013Rejuvenating Architecture GovernanceIn a Redesigned OrganizationIver Band and Graeme QueenThe 2010 Standard Insurance Company Newport Beach, California © Open Group Conference,
  2. 2. The Standard • Financial services company • Founded in 1906 • Our purpose: We help people achieve financial well-being and peace of mind. • Expertise: • Group Life & Disability Insurance • Individual Disability Insurance • Retirement Plans • Individual Annuities • Commercial Mortgages • Investment advice • Headquarters in Portland, Ore. • 3,100 Employees2 January 29, 2013 © 2010 Standard Insurance Company
  3. 3. Speaker Profile: Iver Band • Enterprise Architect based in Portland, Oregon • Infrastructure, application and business architecture • Architecture methods and governance • Previously at HP • Security and infrastructure • Vice Chair, Open Group Architecture ArchiMate Forum • Security research • TOGAF 9 Certified • IT and R&D management • ArchiMate 2 Certified • Middleware product • CISSP, CIP development • Mainframe systems programming • Before that • Mainframe and midrange application development3 January 29, 2013 © 2010 Standard Insurance Company
  4. 4. Speaker Profile: Graeme Queen • Director of Solution Delivery based in Portland, Oregon • Asset Management • Benefits and Onboarding • CRM and Contact Center • Ten years in IT management • Software engineering • Systems analysis • Architecture • Middleware • Applications • Before that • CRM software engineering4 January 29, 2013 © 2010 Standard Insurance Company
  5. 5. Purpose • Demonstrate a pragmatic approach to architecture governance focusing on solution architecture and technology standardization • Demonstrate the effectiveness of the ArchiMate language for developing and communicating IT business architectures5 January 29, 2013 © 2010 Standard Insurance Company
  6. 6. Our Focus: Architecture for the Business of IT To Enable TOGAF ADM Phases C, D & E6 January 29, 2013 © 2010 Standard Insurance Company
  7. 7. Agenda • Organizational Change • Architecture Governance • Motivation • Organization • Process • Information • Results and Lessons Learned • Open Discussion7 January 29, 2013 © 2010 Standard Insurance Company
  8. 8. Architecture Within 2008 IT Organization8 January 29, 2013 © 2010 Standard Insurance Company
  9. 9. Motivation for Organizational Change9 January 29, 2013 © 2010 Standard Insurance Company
  10. 10. Architecture Within Current (Since Q4 2011) IT Organization10 © 2010 Standard Insurance Company January 29, 2013
  11. 11. Early 2012 Assessments by Management and Senior Architects11 © 2010 Standard Insurance Company January 29, 2013
  12. 12. Imperatives for Architecture Governance12 © 2010 Standard Insurance Company January 29, 2013
  13. 13. Architecture Governance Principles13 © 2010 Standard Insurance Company January 29, 2013
  14. 14. Architecture Governance is a Collaborative Effort14 © 2010 Standard Insurance Company January 29, 2013
  15. 15. Architecture Review Team and Board Work Together to Review, Recommend and Ratify15 © 2010 Standard Insurance Company January 29, 2013
  16. 16. Collaboration Early on Makes the Architecture Review Process Go Smoothly16 © 2010 Standard Insurance Company January 29, 2013
  17. 17. Project Architecture Reviews Foster Transparency and Accountability17 © 2010 Standard Insurance Company January 29, 2013
  18. 18. Technology Positioning is the Current Priority for Formal Architecture Guidance18 © 2010 Standard Insurance Company January 29, 2013
  19. 19. Technology Positions Guide Use of Application, Data or Infrastructure Components19 © 2010 Standard Insurance Company January 29, 2013
  20. 20. Example Technology Position Supplier [Major IT vendor] Technology [Insurance data template] Version [Version number] Layer Infrastructure Technology Domains Data, Integration Business Domain Finance Lifecycle State Emerging Permitted Usage Data warehousing, staging, marshalling Prohibited Usage Projects unrelated to Finance20 © 2010 Standard Insurance Company January 29, 2013
  21. 21. Lifecycle States21 © 2010 Standard Insurance Company January 29, 2013
  22. 22. Architectural Exceptions Generated in Reviews Manage Risk, Permit Tradeoffs, and Foster Accountability22 © 2010 Standard Insurance Company January 29, 2013
  23. 23. Example Exception Project [Project Name] Title Modification of [Line-of-Business application] written in an [obsolete language version] to support an additional line of business Focus Architecture Category Non-Critical Owner [Solutions Director B Name] Review Date November 15, 2012 Approved Yes Close Date January 31, 2014 Statement [Application to be modified] is an [obsolete language] application in Contained status. Further enhancement [increases risk and technical debt] Status Update [Solutions Director B Name] to see if application replacement can be added to23 © 2010 Standard Insurance Company January 29, 2013 2013 roadmap.
  24. 24. Project Architecture Ratings Determine Whether An Architecture Is Ready for Implementation24 © 2010 Standard Insurance Company January 29, 2013
  25. 25. Results of Rejuvenated Architecture Governance • All new architectures go through the process • The design community has adopted similar practices for high-level design • Directors own exceptions • We have surfaced significant issues and resolved them through collaboration prior to formal review • Projects are not delayed by architectural issues • The unhealthy tension around architecture review has dissipated, and the organization uses the process more broadly25 © 2010 Standard Insurance Company January 29, 2013
  26. 26. Lessons Learned • Focus on making people and the business successful • Resolve issues through ad hoc collaboration whenever possible • However, formal collaboration sessions ensure all the right people are involved • Formal reviews should be like pre-flight checks • Low stress • Routine nearly all the time • But with the responsibility to surface problems that must be fixed before takeoff • Focus standards efforts on business need and unresolved questions • Many organizations have extensive technology portfolios but have timely questions only in limited areas26 © 2010 Standard Insurance Company January 29, 2013
  27. 27. References • ArchiMate 2.0 • http://theopengroup.org/archimate/downloads.htm • TOGAF 9.1 • http://pubs.opengroup.org/architecture/togaf9-doc/arch/ • Related Presentations: http://slideshare.net/iverband • Contact: iver.band@standard.com27 © 2010 Standard Insurance Company January 29, 2013
  28. 28. © 2010 Standard Insurance Company

×