2020-05-12 Op Leads (PM) Meeting notes

PM co-chairs update

Bill Hackenberg is no longer with the SILS Project. We will meet with IC-Steering to discuss PM needs.

Reinventing the Operation Leads meeting, continued

• How do things get added to the agenda? Self-serve with ground rule in place for sufficient warning of pre-reads and notice to Op Leads slack channel, time estimate.

• Mini retrospective on the Ops Leads meetings at end of May: what’s working, not working, what have we learned to inform the next iteration?

10

Christine & Lena

Agreement to self-serve on adding agenda items to the agenda with a heads-up on the Op Leads channel that includes the topic and time involved.

Op Leads will review whether having 2 meetings is working. We will look at what works, what doesn’t, lessons learned and what needs to change (if anything).

(OP Leads) Step B (Liaison Members)

Awareness that liaison members on the Internal Training team would like the option to attend meetings

The request for an amendment to the current wording of the SILS phase 4 governance structure document is being brought to SILS working group on 5/14

5

Neil

• Confusion in wording of liaison description. It implies liaisons should not attend meetings at all. A request for an amendment to the language will go to WG on 5/14.

• Many liaisons are attending meetings. Internal Training liaisons are not attending meetings.

• Concern that Internal Training liaisons will not be current with materials if they are not attending meetings. Neil suggests Internal Training should not be a stepped representative group, but rather a full representative group.

• Internal training members are not responsible for doing the training but they determine which staff needs what training, ensure trainers are supported - reserving rooms, helping out.

• A key task will be to monitor decisions that come out of cohort in order to modify training materials as needed. One document is maintained for all campuses. However, campuses may add or change a workflow step locally in a supplemental document. this person will need to consult at their campus to know if policies/practice decisions will affect the training documentation.

• It’s fine to have liaisons for End User Outreach. We need full members for Internal Training.

• Christine Barone (Unlicensed) to invite Neil to Steering and WG to present on Internal Training.

(OP Leads) Training

Discuss the approach and recommended training for cohort groups

Training Overview (GDoc)

Cohort Training tracks (Gspreadsheet)

15

Neil

• Numerous asks for basic training for the Cohort on Alma and Primo to facilitate decision-making.

• Training tracks were the initial approach but more in-depth content is needed.

• Ask is to verify the additional training for their groups is needed.

• This current list is meant to be a library of basic videos in recommended viewing order.

• Groups can request additional topics they would like to learn about and TOC will find an appropriate video(s) for that group.

• How would Com Leads like the Basic Track training to be shared on Confluence? Put on Internal Training space.

• These are not the right level for SILS News – too detailed.

• Ben Alkaly (Unlicensed) or Adrian Petrisor to determine where to share Basic Tracks training link on Confluence.
• Neil Weingarten will create a page on Internal Training space that Ben Alkaly (Unlicensed) will link to

(Op Leads) Opening confluence

Decision page (includes communication plan) Opening Confluence

Understand pending work:

• FAQ, set deadline for first draft of content

• Remove test docs

• Any other content we need to create?

Awareness that Vacations/Out were deleted on Confluence and new pages created in G Shared Drive.

15

All

• Audience: vast majority of traffic will be UC libraries, particularly, the cohort

• Coms discussed the headers/categories they want on Confluence. They would like to use subpages to keep from scrolling.

• Add Training section

• Add FAQ section

• Caitlin suggested using filters and the decision rollup macro to show a subset of desired decisions (e.g., done)

The Communication Op Leads are empowered to decide on the final layout for the wiki.

Top level FAQs will be live by June 1. By today the decision as to which FAQs will be in the initial document will be decided.

• Ben Alkaly (Unlicensed) will discuss with Adrian feedback from today’s meeting on headers/categories for Confluence landing page
• Ben Alkaly (Unlicensed) and Adrian Petrisor will select which items will be in the FAQ version that is ready for June 1

(Ops Leads) Local campus implementation teams/contacts

https://docs.google.com/spreadsheets/d/1IGEn-g0op7J4GQzNCkzAmaCu6rTlfa8YUQe15o9q5GY/edit#gid=0

Have we fully defined the problem we are trying to solve?

How is communication disseminated from project to local groups? Do we need to track contacts?

Problem statement: we need to know who to contact at campuses in different cases. It would be helpful to have a document of who’s doing what. No single point person in Phase 4.

• IC = implementation coordinator for local group

• DOC = appointing new SILS members

• Communications person?

Table for now

(PM) Ongoing checkin

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?

10

All

(COM) SILS News Communications Phase 4 Editorial Calendar

Awareness of upcoming communications and anything needed

• date needed for Training videos in SILS News

Parking Lot

Total

60/60