2018-12-14 Call Note

Agenda

1. Roll Call (by timezone - East to West)
2. Scribe Shout-out - It's easy to scribe: How To Scribe Itana Calls Guide
3. Agenda Bash
4. Topic: Capturing Architectural Posture : a Metrics-based Approach - Brendan Bellina (UCLA) | Download PDF | Download PowerPoint Slidedeck |
   
5. Itana Org Updates
   
   1. Working Group Updates
      
      1. New2EA Working Group
      2. API Working Group
      3. Business Architecture Working Group
      4. EA Maturity Model Working Group
   2. Book Club - Reading "How to Measure Anything"
   3. Steering Committee Update

Attendees

(insert screen shot of the Adobe Connect list of attendees or type)

Announcements - Itana News, Working Group Report out

Capturing Architectural Posture : a Metrics-based Approach

UCLA – by the numbers

Budget $7.5b, but less than 7% of revenue.

Culture of distributed systems and responsibilities.

Herd of cats, no strong central dictate of what people can do.

Brand is important, so risk management is important value of architecture.

IT doesn't tell other departments what to do,.

IT is a microcosm of U: a bunch of units that function somewhat independently.

If IT says we are doing something, others will watch and see if its something worth pursuing.

"Symphonic"

ITAC facilitated by president

U-wide BoK: campus by campus decision whether to adopt artifacts.

Office of President drafts outcomes and departments decide whether to adopt.

Need for certain types of technology agreements e.g. Payroll.

ITAC also has begun to look for best practices that aren't necessary for system implementations.

No central function that can override individual campuses.

Timeline:

• 2012 IT architecture directed unit
• 2016 IT architecture relaunched
  • no more architecture reviews
  • restrict R&D
  • restrict collaboration outside UCLA
  • new governance with fewer directors but more campus participation
  • establish collaborative groups with architectural aids e.g. models to get to value as quick as possible
  • rotate leadership quarterly
• 2017 workshop
  • outside consultants to define roadmap
  • 2018 state of enterprise architecture (diagram)

Decision to demonstrate value with metrics.

How often are artifacts viewed, reviewed, used ..

The "valuation decline" (see slide)

• Potentiality limiters: Lack of political support, getting positions posted, lack of trust between architecture and IT teams ....
• Capability limiters: Not having right skills, consistent direction (due to change of leadership).
• Influence limiters: Not enough outreach, no public materials or people don't know where they are, lack of presence on campus

Are there metrics we should have about the things we should be doing?