Configure Zoom meetings for sprints

Open
#84 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Use the numbered Zoom and Outlook procedure in the issue as the starting point. Verify that the sprint meetings appear at the linked Zoom URL and that meeting emails use the intended names, then document the observed behavior, including any uncertainty about copied meeting assets.

Written by the indexing model from the issue text.

Description

What would you like to see added?

Quick summary of what Louis and I discussed just now about using one Zoom Meeting ID for multiple meetings, each with different names. Zoom will pick up on the differences (due to a deep integration between Zoom and Outlook, maybe?)

  1. Using Zoom, create a new meeting with no attendees. Time/day/recurrence/name doesn't matter yet, Zoom will pick up the changes later. All we need right now is a Zoom Meeting ID and link.

  2. The meeting should get added to your Outlook calendar (make sure it does).

  3. Duplicate or copy/paste the meeting in Outlook, then adjust the day/time/recurrence and name.

    • Sprint Planning

    • Check-in

    • Integration

    • Backlog refinement

    • Daily Standup (recur daily, pick the specific days that aren't covered by the other meetings)

      Need two copies of daily standup, one for the planning week, one for the integration week, because the days are different each week. But, you don't need to have 6 copies!

  4. For each meeting add the list of attendees. You can add them to the first meeting, then copy-paste that list to the others.

From here, Zoom will (eventually) pick up all your changes and reflect them at this URL: https://uab.zoom.us/meeting#/upcoming and in the installed application. It isn't clear what happens to the meeting asset emails, whether they reflect the correct name for each email (I believe they will, we will find out in two weeks).

Dominant language
Python
Stars
1
Forks
9
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from uabrc/devops-docs

All issues in uabrc/devops-docs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.