Skip to content

Instantly share code, notes, and snippets.

@idan
Created March 21, 2022 06:36
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save idan/97a6a4204d0f7e6949e0dea561fe0218 to your computer and use it in GitHub Desktop.
Save idan/97a6a4204d0f7e6949e0dea561fe0218 to your computer and use it in GitHub Desktop.
Next Planning

Next Planning

FigJam: https://www.figma.com/file/ERabwh2yCmH1G6Y7aS9VVs/Next-Semester-Planning-Mar22?node-id=0%3A1

Intro (5-10 minutes)

  • 🚨 DON'T FORGET TO HIT RECORD! 🚨
  • Ann-Mary: a few words about planning process, what OCEO expects in terms of artifact, so people have context for why we are doing this
  • Oege: kick things off with an intro.

Important to clarify for everyone:

  • We aren't finishing this meeting and firing off a doc with commitments to LT. There is time after this meeting to think a little and talk a little before we make an artifact.
  • We aren't handcuffed to anything here.
  • The main point of the exercise is for the growing Next to communicate about what we're excited to pursue.
  • "Excitement" is a proxy signal for things we think are within our grasp and could be strategic/impactful.

Phase 1: Review & Vote (5 minutes)

Everyone had a busy week last week. Everyone take five minutes to review the board.

  • Stick +1 stickers on topics or themes that you think are exciting/most worth pursuing
  • Stick a your-face sticker on topics or themes that you personally want to champion.

Phase 2:

When this phase is done, moderator should look over the board and take the top four-five topics for discussion. There will not be time for more in this session. If we're really not getting to everything, we can schedule a followup.

For each topic:

  • Set a seven minute timer
  • Is there an obvious champion? Faces on the card, or the author of the card. Or just ask who wants to start the discussion.
  • Try to surface and discuss:
    • Who benefits from this existing?
    • How would this change GitHub?
    • What would it take to get it done? Resources, time, etc
    • Do we have the skills in-house to pull it off? If not, who do we need?

And have a notetaker capture these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment