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 7
Next »
Attendees
Discussion items
| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
---|
1 | Checkin/quick updates/anything from slack or email | | 0 | All | | | |
2 | 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?
| 20 | All | | | |
3 | Coordinators Discussion & Project Communications | Do we need a meeting with this group to launch it and have a shared understanding of expectations, roles, tools available (timelines, etc.) | 10 | All | 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? Week of Oct 12-16
| | |
4 | 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: Oct 21 | 5 | All | RLFs (Lena to grab notes from IC Steering), see notes from IC meeting Sep 24 Proposal to discuss at SILS Chairs meeting. Lynne and Cathy to lead this discussion. Carlo and Tom as sponsors. Actions: Lynne, Tom, Carlo to organize a session on RLF questions (how do UCs want to display information? what do we want for depositing and requesting? what questions do we want to ask Ex Libris? Action: Lena will put RLF discussion on SILS Chairs next agenda (Oct 21). Tom, Carlo, Lynne, Cathy will facilitate the discussion.
| | |
5 | Parking Lot | | | | 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 (extend beyond go-live), identify critical path & intense work periods Adrian & Todd are working on integrations communication work
| | - Neil Weingarten First step, Neil will draft a pros/cons/benefits/risks one-pager on the buddy system + what are those times when a buddy is needed.
|
6 | Wrap up | | 5 | All | Any actions or decisions missed? | | |
7 | | Total | 40/50 | | | | |