Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 12
Next »
Attendees
Discussion items NEED TO FINISH SETTING THIS AGENDA
| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
---|
1 | Checkin/quick updates/anything from slack or email | | 5 | All | When will the decision be made on whether the IT co-chairs accept the position? (It will spawn some work of adding them to the appropriate communication channels) Would it be useful to share the Monday series with Alma training summary message with IT to see if it’s missing anything? (I want to be mindful of their bandwidth) Is the first module User Management email going out next week on Monday? When will the Confluence site be ready with the new Alma training? (Vanguard training ended on 9/28)
| | |
2 | PM check in | | 20 | All | | | |
3 | TH4All | Decide how to break up the PM presentation at the TH4All. | 10 | | | | |
4 | Training, IC, PPC, SSM | Is anything blocked or behind schedule? What deliverables are coming in the next week? Any decisions, consultations or approvals needed in the next week? Do you need anything?
| 0 | All | | | |
5 | SILS All Chairs meeting (recurring) Note-taking: Facilitating: Monitoring chat: All Track attendance:
Post to SILS Chairs slack channel on Monday before meeting: If no agenda items or pressing issues by EOD Monday, we’ll cancel the Wednesday meeting. | Topics for next meeting: Nov 4 | 0 | All | | | |
6 | Parking Lot | | | | Share ExL recording links on Confluence? (would need to get permission from ExL and others) Consider a buddy system for local campus staff (particularly for post-go-live training and other work), pairing a new campus with an existing Alma campus for the local implementation teams. Match by size (student count): Davis, Irvine, Riverside, Santa Barbara, Santa Cruz. Identify risks of not having a buddy system. Post this idea on the Coordinator. Identify times when a buddy is needed, benefits/risks. Premortem checkins - Hold for a future meeting Timeline planning (extend beyond go-live), identify critical path & intense work periods Adrian & Todd are working on integrations communication work Coordinators group: Start with a one-time introduction meeting for Coordinators with IC and PPC; IT co-chairs are in flux right now. Intent is not to have a recurring meeting. Ask ICs and PPC co-chairs: What do you see coming up that will need to be coordinated? decisions?
| | |
7 | | | 5 | All | Any actions or decisions missed? | | |
8 | | Total | 50/50 | | | | |