Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move monthly team meetings from Monday to Wednesday #237

Closed
2 of 4 tasks
choldgraf opened this issue Sep 6, 2021 · 8 comments · Fixed by #246
Closed
2 of 4 tasks

Move monthly team meetings from Monday to Wednesday #237

choldgraf opened this issue Sep 6, 2021 · 8 comments · Fixed by #246
Labels
Task Actions that don't involve changing our code or docs.

Comments

@choldgraf
Copy link
Member

choldgraf commented Sep 6, 2021

Description

We should move our team meetings off of either Mondays or Fridays, and onto Tue/Wed/Thu. We should pick one of these days for our monthly team meetings.

Value / benefit

By avoiding Mon/Fri, we'll be less likely to lose people because of holidays or vacation, and we'll all more easily be able to have flexible weekend working schedules :-)

Implementation details

We should plan around some other important meetings as well:

Other meetings to consider:

  • Weekly sprint planning meeting: Tuesdays
  • Monthly steering council meetings: Tuesdays
  • Jupyter Community meeting: Tuesdays
  • Turing Way Collaboration Cafes: Wednesdays
  • Berkeley tech strategy meeting: Thursdays

Another thing to consider is how this meeting fits in with our weekly "sprint planning" meeting. It feels natural to me that the monthly meeting comes towards the end of a sprint, rather than at the beginning of a new one. This more naturally creates space for reflection and discussion rather than thinking about tactical issues. We should decide if we want to follow the same pattern in moving the meeting time.

Tasks to complete

  • Arrive at a time for meeting planning to work
  • Update Google Calendars for future meeting changes
  • Prep a PR to update our team meeting practices
  • On Wednesday the 29th begin new process for team meetings

Decision

We'll follow the plan in this comment: #237 (comment)

Updates

No response

@choldgraf choldgraf added needs:decision Task Actions that don't involve changing our code or docs. labels Sep 6, 2021
@choldgraf
Copy link
Member Author

choldgraf commented Sep 6, 2021

How does the @2i2c-org/tech-team feel about this proposal:

  • Move Sprint planning to Wednesdays (so Sprints are now Wed -> Wed) off-cycle with Turing Collaboration cafes (is it possible for us to move it in time so that this works @sgibson91 ?)
  • Move monthly team meetings to Tuesdays (off-cycle with the Jupyter community meetings and the Steering Council meeting)

@sgibson91
Copy link
Member

  • Move Sprint planning to Wednesdays (so Sprints are now Wed -> Wed) off-cycle with Turing Collaboration cafes (is it possible for us to move it in time so that this works @sgibson91 ?)

Collab Cafés run 15:00-17:00 Europe/London time on the first and third Wednesdays of the month

HackMD: https://hackmd.io/@turingway/collaboration-cafe
Calendar of all Turing Way events: https://calendar.google.com/calendar?cid=dGhldHVyaW5nd2F5QGdtYWlsLmNvbQ

@damianavila
Copy link
Contributor

Move Sprint planning to Wednesdays (so Sprints are now Wed -> Wed) off-cycle with Turing Collaboration cafes

👍 to the idea of having it on Wed.

Collab Cafés run 15:00-17:00 Europe/London time on the first and third Wednesdays of the month

What about every Wed 17-18 London time? @yuvipanda, is that too late for you? Other's thoughts?

Move monthly team meetings to Tuesdays (off-cycle with the Jupyter community meetings and the Steering Council meeting)

👍 as well

@sgibson91
Copy link
Member

What about every Wed 17-18 London time?

Once we move to fortnightly sprints (which I think is happening at the end of the month?), we can keep the current time slot so long as we stick to the 2nd and 4th weeks of the month as we'll be off-cycle with the Turing Way.

@choldgraf
Copy link
Member Author

choldgraf commented Sep 7, 2021

A proposal:

How about this then:

Starting Wed, September 29th:

  • Sprint Planning
    • On Wednesdays at 7:30am California time / 15:30 London / 16:30 CET / 8pm India.
    • Every 2 weeks. If we start on the last week of September, that should put us off-cycle with the Turing Way meetings.
  • Team Meetings
    • On Tuesdays at 7:30AM California time / 15:30 London / 16:30 CET / 8pm India.
    • Every month. Should happen on the same week that a sprint cycle is ending, the next would be on October 12th.

So on Wednesday the 29th we'll have our sprint planning meeting, and the next will be 2 weeks later.

I think that would put us off-cycle with Jupyter community calls and Turing collaboration cafes

If nobody objects, then I'll write up a PR to update our team policies.

@yuvipanda
Copy link
Member

Sounds good to me!

@choldgraf
Copy link
Member Author

OK I think that we have a time that works! I've updated the top comment to reflect our latest plan. For this sprint I'll make a PR that updates our team meeting practices, but can leave it as a draft until the week of the 29th when we can begin these new practices ✨

@choldgraf choldgraf self-assigned this Sep 8, 2021
@consideRatio
Copy link
Member

Sounds good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Actions that don't involve changing our code or docs.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants