Skip to content
This repository was archived by the owner on Feb 8, 2023. It is now read-only.
This repository was archived by the owner on Feb 8, 2023. It is now read-only.

2019 Q3 Planning (and Q2 OKR Scoring) #995

@momack2

Description

@momack2

Hello friends and @ipfs/wg-captains!

The end of the Quarter is past and with it, time for us to score Q2 OKRs and finalize our plans for Q3! Our draft of top-level project priorities for Q3 has already driven the team to restructure into problem-oriented task forces to organize our work for Q3. Now for writing it down!

@daviddias has done a great job explaining how this happens in the past and drafted our Notes on OKR Planning, which is a great primer on how and why we use OKRs.

The TLDR is:

  1. Update scores in the IPFS Q2 OKRs sheet - everyone should fill in the rows that they own
    • End-Q Actual - How much progress you made on this KR
    • Notes on grading - An update on why you gave it this score (if not obvious)
  2. Create a PR against your group's OKR doc (creating a new doc if needed) -- https://github.com/ipfs/team-mgmt/tree/master/OKR -- to invite team members and the community to discuss the most important work for the coming quarter. See this past example to give you an idea (OKRs - 2019 Q1 JS Core WG #799)
  3. Once the OKRs are ready, push them to the IPFS 2019 Q3 OKR Spreadsheet

If you are new to this whole process, check in with your Working Group colleagues and go through the issue that covers how we did it for 2019 Q1 for context. Please post all your remaining questions so that we make sure to get them answered and improve our docs in the process ✨

End of Q2 Scoring Checklist:
(despite our reshuffle into fewer core WGs, we are still finishing out the quarter with our current OKR sheets, so this list is larger than it will be next quarter. If I've missed any, please chime in to correct!)

Q3 OKR Drafting Checklist:

If anyone has questions, please post them here :)

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions