...
Item | Desired Outcome | Time | Who | Notes | Decisions | Actions | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Checkin/quick updates/anything from slack or email
| 0 | All | Reminder to check off your “done” tasks from the task report. | |||||||||
2 | SILS Service Manager (recurring) | Report on progress | 1525 | Caitlin | FYI- Systemwide Work Planning - plan for the work CDL / systemwide groups will do to support the SILS
| 3
| |||||||
3 | SILS All Chairs meeting (recurring)
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: Sep 23 | 10 | All |
| ||||||||
4 | SILS project blog (recurring) | Is the blog necessary? | 10 | All | Let’s make on a decision on this
| ||||||||
5 | Basecamp | Revisit our policy on limiting Basecamp as we enter the full implementation phase; document our reasons. Immediate next steps this week:
| 100 | All | Q: Would adding more members of your team to BC be beneficial? PPC: Yes. It would be great to have the option to add people if we want/need to. Q: Will adding more people to Basecamp dilute its utility for the core user groups like PPC? PPC: No Q: Will adding more people to Basecamp create too much work in answering questions and troubleshooting problems about Basecamp? PPC: A bit like the previous question; no Q: Limit to only cohort? Include local implementation team members who are not in the cohort? Allow ICs and others chairs to determine who on the local teams should be included? PPC: We should empower people to have access. IC’s should add local team members. It is important that everyone in BC follows procedures and knows what to do with the answers. Q: Should access begin immediately to allow new users to get used to Basecamp before Implementation begins or wait until Implementation phase launches on Nov 5? PPC: Groups should have access asap, for local members defer to what ICs believe is best. Q: What’s the best way to share best practices and what happens if users do not follow them? PPC: Chairs are responsible for ensuring that their group members are aware of best practices and rules of the road. ICs are responsible for ensuring that anyone from their local team(s) is aware of those documents. We are all professionals and expect that people will do the right thing. Reminders if they do not. | 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: Sep 23 | 10 | All |
| |||
5 | SILS project blog (recurring) | Is the blog necessary? | 10 | All | Let’s make on a decision on this
| 6 | Alma Training (recurring) | Update on progress | 0 | Neil | |||
7 | (Ops Leads) Ongoing checkin |
| 0 | All | |||||||||
8 | Op Leads feedback on shared gov | Continue work on https://docs.google.com/document/d/1EmIgNjK79ig4wXFEwpbxoblik2dMmmqH8701xhBi5jA/edit# What’s the best way to add to this document? On our own or together? | 0 | Time-permitting | |||||||||
9 | Communicating about integrations work | Determine approach and who’s involved https://docs.google.com/document/d/1ZU4-h19rqUCBNX-4NS0DI25Is-6ZBI4_hDKB_Kpu_CM/edit# | 0 | Time-permitting, not urgent | |||||||||
10 | SILS Town Hall meeting (recurring) | 3rd Tuesdays | 0 | Com Leads | |||||||||
11 | Parking Lot |
| |||||||||||
12 | Wrap up | 5 | All | Any actions or decisions missed? | |||||||||
13 | Total | 50/50 |
...