Page Comparison

Com Leads

Update on EUOS

10

• Most work will be closer to go live.

• Naming the website is one issue where an end-user name is needed sooner than later.

• Communication with other groups on decisions, info. sharing - how is it going? Do they need someone to help liaise? Possibly. This is a similar situation to what happened with PPC and FGs early on – they needed to work out consultation paths and how to keep each other informed of decisions and consultations, etc.

• After they get the end-user name, is there any other work that concerns them? No.

• Graphic designer - more details are needed about the amount of work, frequency, etc. to solicit a volunteer designer. This could take some time. They should It would be good for EUOS to finish their request.

Checkin/quick updates/anything from slack or email

• Don’t forget to check the Task report for your outstanding tasks and check them off when done.

5

All

• Reminder to check task report

PM check in

30

All

• Get update from Neil on this: 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 channel. Identify times when a buddy is needed, benefits/risks. (First step from 10/1, Neil will draft a pros/cons/benefits/risks one-pager on the buddy system + what are those times when a buddy is needed. Focus on training. Neil is expecting to finish the work this work. Generalize it for use beyond Training. Adrian will work to generalize it.

Training, IC, PPC, SSM

1. Is anything blocked or behind schedule?

2. What deliverables are coming in the next week?

3. Any decisions, consultations or approvals needed in the next week? 

4. Do you need anything?

0

All

• IT is in good shape with organizing their meetings.

• IT is not interested in attending the ExLPM; they could do it but would prefer to have a PM do it. They don’t need a PM at meetings; want a PM at Steering meeting and liaising with other groups and understanding the larger timeline. Caitlin will attend ExLPM meetings until she leaves.

• IT will make a Confluence page about certification.

• No questions for this round have been submitted yet. Not concerned yet since these are the lighter topics in the beginning. Dominique followed up with UCM and UCD Law and they are in good shape.

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 18

• https://uc-sils.atlassian.net/wiki/spaces/SC/pages/edit-v2/587366612

0

All

• Confirming ICs are invited to SILS Chairs meetings as “optional”. And, the new co-chairs of IT were added to the recurring invite (Brian & Katie).

Parking Lot

• Premortem checkins - Hold for a future meeting

• Adrian & Todd are working on integrations communication work (no progress; on to do list)

• Coordinators group:

  • Start with a one-time introduction meeting for Coordinators with IC and PPC. Is IT needed? 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?

5

All

Any actions or decisions missed?

Total

50/50