Agenda

1. Roll Call (by timezone - East to West)
2. Scribe Shout-out 
3. Agenda Bash

4. Main Topic - Future of the SIS - Jim Phelps

5. Itana Org Updates (if any)
   
   1. Working Group Updates
      
      1. New2EA Working Group
      2. API Working Group
      3. Business Architecture Working Group
   2. Steering Committee Update
      1. Women in EA Working Group
      2. Face2Face 2020 - Boston - Leading Change as an Architect

Attendees

Announcements - Itana News, Working Group Report out

Topic Title (Future of the Student Information System)

Slide deck - https://docs.google.com/presentation/d/1dNF85RdRyOaXMHPlzL8KI2ON8x9apoF8T9TjGFy4JYE/edit#slide=id.p

• Context - HBR article: Strategy is a Wicked Problem
• Issues adding to the wickedness
  • Repository (all the data)
  • Student - role has changed
• Leave the Plumbing, Remodel the House (Carrie Shumaker, UMich-Dearborn)
  • Using the Pace layer (Gartner)
    • leave the data repository
    • use APIs
    • build out the student experience
  • SIS is more than a transactional system (e.g., Finance, HR, Payroll), you need to manage student relationships
  • IDM could be considered an ERP ... take a step back and consider what we need from an ERP
  • Can your smaller engines (systems) carry you as you rebuild your plumbing?
  • As the student environment evolves, the data is the student's and we are managing their data (from potentially many sources)
• Aligning the Student Experience
  • How do we avoid many system touches that negatively impact the student experience?
  • Shrink the SIS to the record level (layer 1)
  • Units would be forced to look at their business processes, clean up data problem, and data literacy
• Other thoughts
  • Innovation will occur among those who have a system view and recognize their (small/niche) role in the ecosystem
  • Think of the student as the boundary of many systems
• CHAT contents
  • Add in the multiple types programs - traditional, experience-based, non-term programs
  • ERP is a bit like a brontosaurus trying to make its way around downtown Chicago… it can blunder around, but it was never evolved for the environment it’s currently making its way around. Definitely a wicked problem.
  • Doesn't the innovation layer apply more to the teaching system?
  • On slide 16, I think of Student on this slide more as the whole domain.
  • And I do think of teaching & learning solutions as part of the Student domain … but terminology can vary.
  • To have a flexible system that allows changing requirements, varied student enrollment types, an API layered approach is definitely the way to go imho
  • I wonder if some of that is because vendors are retrofitting existing architectures. LIke Paul & Betsy said, they old house wasn't designed for this.
  • The underlying methodology here is based in Risdon, Orchestrating Experiences: https://www.amazon.com/Orchestrating-Experiences-Collaborative-Design-Complexity/dp/193382073X
  • I think the barebones way of looking at SIS will also positively impact any upgrade/patches for these systems.
  • Tools
    • I would add interactive whiteboard capabilities too.
    • I've seen some threads lately around whiteboarding... we should start an email thread
    • The topic came up with the last book report on "Back of the Napkin"
    • and by threads lately I meant to say Twitter threads

1. Itana Org Updates (if any)
   
   1. Working Group Updates
      
      1. New2EA Working Group - April 8
      2. API Working Group
      3. Business Architecture Working Group 
   2. Steering Committee Update
      1. Women in EA Working Group - April 23, 1 pm, Topic: Unconscious Bias
      2. Face2Face 2020 - Boston - Leading Change as an Architect