Agenda
Roll Call (by timezone - East to West)
Scribe Shout-out
Announcements
Business Architecture and the Process of Change
Piet Niederhausen and Jenni Laughlin, University of Washington
Roll Call
Announcements
- Itana events
https://spaces.at.internet2.edu/display/itana/Events- Itana Fall FTF at Educause-24 Registered
- Itana one hour session
- MESA Presentation
- API Working Group
- 2nd Thursday API call. October 13th is next call. Round table of what is going on at each campus.
- Three people leading including Ashish
- Link shared for Itana wiki
- Steering group candidates
- 8 candidates so far
- Will discuss and decide in the next two weeks
- Need case studies for people coming to the Face-To-Face
- Check wiki or email to determine if next meeting is a go because it is just before the Educause Itana Face-to-Face
Business Architecture and Process Change
By Piet Niederhausen and Jenni Laughlin, University of Washington
- Business Architecture, by Piet Niederhausen and Jenni Laughlin, University of Washington
- New capability for them - 1-2 years in the making
- See slides
https://spaces.at.internet2.edu/download/attachments/1517/2016-10-07%20Intro%20to%20Business%20Architecture%20for%20Itana.pdf?api=v2 - UW - Large public school with 16 colleges and schools and a Med Center
- Enterprise Architecture in central IT but Jenni is a federated partner to EA
- “The ultimate goal is to actively manage change rather than letting change manage the University."
- Business Architecture: Facilitating change through common language and alignment
- Industry piece on describing the Business Architecture (technology agnostic)
- It is about pulling together a shared understanding of the spaces we work in
- Private sector looks different in decision-making and complexity
- Figuring out how to think about change in our organizations
- Business architecture needs a federated model and needs to pull in those who are practicing across the institution whether they call it that or not.
- EA practice supports this in different ways. Proposing a model on the slide.
- EA promotes the practice of Business Architecture.
- Challenge: the institution works in different ways across different areas
- Good change process relies on mature organizations
- Much of the work over the last years is cross-functional
- Finding shared goals
- Sustaining them over time
- Is neutrality an important component - yes but there is also benefit to have a technical perspective.
- There is somewhat of a barrier initiating these conversations from the IT Organization but that can be overcome with good, well conceived participation and building trust
- This moves the IT organization towards a campus partner
- A four boxer demonstrating IT’s response across two axises - Change Complexity (high to low) x Customer Readiness (high to low)
- Reflection on similarity to Cyefin Framework
https://en.wikipedia.org/wiki/Cynefin_Framework - More and more we are facing change in high complexity low readiness situations
- Part of the work is getting the tools in place to build a shared language and tools to have literacy and strong foundations to work together
- List of gaps that Business Architects fill
- Case Studies
- Space information about facilities
- Build a shared sense of purpose
- Show the decencies on each others information
- Collect all the related efforts under way to maintain current state
- Vin Diagram on the village problem - people, process, technology
- Pivot on evolving a village
- Make it real by building a future state
- Future state vision depicts a lot of work over a lot of time
- Recommendation high-level motivating view
- Questions-How do you approach working with the different teams and getting them to work in a federated model?
- One coffee at a time
- Putting together senior sponsor and stakeholder groups
- How did you get inserted into the opportunity to work with stakeholders?
- Worked on various test-balloons on different initiatives, bring those to her senior leaders, then move out, one stepping-stone at a time
- Leverage existing relationships and keep building your network