# 2024 Q1 review / Q2 planning meeting

Part I: Monday April 8, 9am - noon
Part II: Tuesday April 9, 11am - 2pm

Participants:

- Kristina
- Eric
- Chris
- Renata

## Homework

* Add all relevant work + hours from this quarter to [effort spreadsheet](https://docs.google.com/spreadsheets/d/19Nxa4HiCYmQ4oXa41XR7kBIpRoatxD-Efp0VBUpRLDk/edit#gid=0)
* "Jan - June CCT DS" tab
* Due Friday April 5!
* Update and Score previous quarter OKRs
* [2024 Q1 OKRs](https://docs.google.com/spreadsheets/d/1KW1EDg05XbH8mo2rCBtlXhSWtp2BSLKjv6vcLJUbowQ/edit#gid=844680069)
* Draft next quarter OKRs
* [2024 Q2 OKRs]()
* Review
* [notes from previous meeting](https://hackmd.io/iltgSPr2R1OuVC-tQV75eg)
* Link above includes homework
* Suggest topics [here](https://forms.gle/aSp2FYjEiicAVndSA) or below
* Create a presentation summarizing:
* Major accomplishments
* What went well, what didn't
* Plans for next quarter

## Agenda

Monday:
* 9:00 - 9:20: Pictionary! https://www.drawasaurus.org/
* 9:20 - 10:00: State of the group presentation
* 10:00 - 11:00 (break at 10:30): Individual presentations (~15min ea)
* [Kristina / group](https://docs.google.com/presentation/d/1E4vX5MDknk1QEuUbXTscA8yJibiz__4cDNTV0JDhxO8/edit#slide=id.g2ca29026f8f_0_429)
* [Eric](https://docs.google.com/presentation/d/1WAYff-Tn-gdsrFYL5gczovc4Jeq8JrHAGEDA7zyOMS8)
* [Renata](https://docs.google.com/presentation/d/1_EQnKYCdJx83GqfelLNQRWA2_Yh_jTrorhzDhCovypo/edit)
* [Chris](https://docs.google.com/presentation/d/1i-r_QH56CS5FZDljls_Ht2DLai_vPmXuBI5C-UcAJrw/edit?usp=drive_link)
* 11:00 - 11:45 (break at 11:15): discussion
* 11:45 - 12: Choose things for Tuesday's "hackathon" session
* Kristina: review and work on group procedures book
* Group branding template
* Bayesian learning group advertisement: https://docs.google.com/document/d/1kwtoOEXsrSipXPj0wGmqL0d_kYon6ln0ize56BAVZOw/edit
* Email to solicit lab groups to participate in beta testing of lab-level trainings? (+ a flyer)
* something about "community of practice"
* CALES only
* Chris: Draft blog post about Drone Day

Tuesday:
* 11:00 - 11:50: discussion
* 11:50 - 12:00: break
* 12:00 - 12:50: "hackathon", pomodoro style
* 12:50 - 1:00: break
* 1:00 - 2:00: discussion

## Notes

- Efficacy of extended consultations ("personal training")
- More prep?
- Not having much ownership over projects
- Jessica transition to UA DCC?
- Solicitation for labs that want to do peer code review
- Find some labs now to work with in the fall? (Or whenever their preferred time is)
- Advertise to CALES depts, people we've worked with already or who we know would be a good fit, ask Lia & Christian about specific labs
- Beta testing curriculum
- Group branding template
- Where to put this: Shiny apps, GitHub readmes, project websites, reports
- Components to include:
- Our group's website via tinyurl version (need to make this) & QR code
- Some text: "Developed in collaboration with the University of Arizona [CCT Data Science](https://datascience.cct.arizona.edu/) team"
- A logo / image?
- Examples of these
- Put templates in group procedures book
- Put these in past projects that don't have them
- One-on-one meetings
- 10 minutes for project status updates, then 20 minutes of structured questions
- Rotate through a list of questions / topics
- Proactive vs reactive
- Shared notes document with parking lot
- Decide on next steps for BLG
- Find someone to help run sessions? Or rotating leads? (People probably don't have enough bandwidth for this)
- Ask DSAs
- Julia
- Re-advertise (especially to stats classes?)
- Putting together list of relevant courses in CALES + instructors
- How is Toggl use going?
- Offboarding
- Removing access to platforms...which ones and when?
- Walk through process with Jessica
- Remove CCT DS and Jessica accounts from Toggl - deactivating accounts still retains name and hours, just can't filter by them or create new entries
- Are all of our group meetings useful and effective?
- Sprint planning - demos taking up a big chunk of time but also happening frequently, move to group processes?
- Standup
- Group processes
- Project hour
- We've stopped doing sprint retrospectives
- Tracking trends, such as lots of new issues or reduction in activity
- GitHub board hasn't developed insights further
- Could pull data from GH api but that would be a big chunk of work
- We aren't paying attention to points
- We need to follow sprint planning protocol more closely
- We should bring back sprint retrospective, replace that standup calendar event with a retro one
- Turned off the workflow for moving closed issues to complete category; need to start closing issues when we move them to done

## Discussion Topics / Parking Lot

- Workshop assessment improvements
- Identify pedagogy or collaboration training opportunities
- Professional development?
- Advertising ideas
- Incubator to some sort of ALVSCE platform?
- Dial the Dean (in the fall?)