Versions Compared

Old Version 1

changes.mady.by.user King

Saved on

compared with

New Version Current

changes.mady.by.user jeff kennedy (auckland.ac.nz)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Agenda

(copy and paste from email or from Adobe Connect screen)

Attendees

  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: New to EA - Top Questions Q&A Session
  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

Dana Miller
Chris Eagle
Betsy Draper
JJ DuChateau
Beth Schafer
Alberta Mendoza
Ashish Pandit
Chris Berg
Jim Phelps
Brian DeMuelle
Trigby Perea
Rupert Berk
Nathaniel Poon
Majeed Abu-Qulbain
Lonnie (Manitoba)
Glenwood Thomas
Chanaka Kannangara
Michael DiCrescio
John Mullins 

4 additional dial-in numbers.(insert screen shot of the Adobe Connect list of attendees or type)

Announcements - Itana News, Working Group Report out

...

  1. API Working Group
    1. Last month session
    2. This month panel discussion on 1/24 about data modeling and how APIs fit into a data integration ecosystem
  2. Business Architecture Working Group
    1. Next Friday Betsy doing presentation on 
  3. EA Maturity Model Working Group
    1. Post your profile and EA Practice Reviews
  4. Book Club next meeting January 18, welcome to join
  5. Steering Committee, Susan Grajek from Educause stepping down and Betsy Reinitz from Educause joining.

Topic: New to EA - Top Questions Q&A Session

  1. There was a very strong response to the idea of New2EA
  2. We sent a survey around and there was a great response to that
  3. Those who have EA, how did you get started.
    1. Yale
    2. Manitoba
    3. Illinois State started in response to duplicative services, various reorganizations, and ERP developed a richer perspective around EA. Now resetting to get stronger.
    4. When the leadership changed, these organizations lost influence in their organizations.
  4. Starting from bottom up
    1. At UW Madison the practice started by influencing technologists and builds and working their way up the stack to more but
    2. At University of Washington a working group developed capabilities and influenced the organization from there
    3. U. Kansas started in a group and when up
    4. Ashish - Initially started EASG steering group. This group recommended and EA practice. A blended model of ground up and top down.
    5. Brian DeMuelle-As part of the ERP has about 7 EAs that will scale back after developing ERP future state.
  5. These are two different patterns.
  6. Those new to EA, what would you like to know more specifically.
    1. Glen, we are about to start a practice starting it from IT. We have some challenges. We expect we may have started it the wrong way. Is that wrong.
      1. Nathaniel from Emory. Our's starts from IT and we are really struggling to measure success.
      2. These practices almost always start out of central IT in higher education because of their central position in the organization
      3. This is fine but there is more to do
      4. IT has been historically looking for ways to optimize their processes
      5. And, much of the business thinking is pretty fragmented
      6. A great topic is how does a new EA practice get footing in the business
        1. Jim always looked to get one credible person in the business saying how great it was to work with EA - a champion
      7.  AT ISU I am working from years of being in the organizations a working to pull together the architectures of people who are already there
  7. Use the Itana Wiki to profile your practice so that you can track it over time.
    1. Enterprise Architecture Maturity Model
    2. Practice Profiles & Practice Reviews
  8. The EA Value Topic
    1. As much as we read about the value of measurement the value is really about how the organization views how you are working with them. At some point you can construct measurement.
    2. Jim seconds that. Also being asked to be part of conversations and part of working through problems is a measure of value.
    3. Leaders using artifacts that you prepared in conversing with others.
    4. Stakeholder analysis helps you track your relationship engagement and advancement
    5. Thinking about assessing whether you are doing the right think may be as worthwhile to a measure of the units value.
    6. Nobody on this call has the Rosetta Stone on how to do this. You have lot's of company.
    7. If you are going to do an ROI or metric, make sure it is something that you control.
    8. Some of the value of EA gets reduced when there is a high level of churn in EA over time. If you are not able to drive the cycle of EA because of the organizational structure there are challenges.
    9. You can target which of these capabilities you can engage in and bring value on those areas. You can develop the EA touch points down the line of the organization.
    10.  Betsy. As Enterprise Architects one needs to be somewhat of an opportunist and do what you can, whenever you can, with whatever resources you have available.
    11. Being creative to get people doing more things architectural.
  9. Tools and practices
    1. Check out what's available on the Itana Wiki.
  10. Organizing the work
    1. Piet described how the Itana Working Groups Work
    2. Itana Steering will support the Working Group
    3. There are very interesting deliverables that could come out 
    4. Reach out to the steering group and raise your hand again if interested in leading