It's that time of the Quarter again ✨ - 2019 Q1 Planning 🎉

[daviddias]

Helloo everyone!!!

The end of the Quarter is quickly approaching and with it, it is time for us to do the OKR Planning Dance for 2019 Q1 🕺🏽💃🏽!

I've gone in great length explaining how this happens in the past and I took notes from that thread and incorporated them on our OKR Notes.

The tl;dr;/TODO list/Summary you have to have in mind is:

• Score your 2018 Q4 OKRs with End of the Quarter Scores
• If you are a Working Group Captain
  • Create a PR against your Working Group doc -- https://github.com/ipfs/team-mgmt/tree/master/OKR -- to get the conversation started. See this past example to give you an idea 2018 Q4 OKRs Planning js-ipfs#1566 (note that PR was done on the js-ipfs repo, but since then we moved all the OKR docs to team-mgmt, here https://github.com/ipfs/team-mgmt/tree/master/OKR)
  • Invite the Working Group members and the community to contribute to the discussion.
  • Rely on your fresh minted Working Group Roadmap to seed the conversation https://github.com/ipfs/roadmap/pulls
• Kick off an Async Retrospective for your Working Group following the Template
• Once the OKRs are ready, push them to the IPFS 2019 Q1 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 2018 Q4, it will provide you a great deal of context. Nevertheless, post all your questions so that we make sure to get them answered and improve our docs in the process ✨

[daviddias]

Open OKR Planning PRs:

• Development and Maintenance:
  • JS Core Team
  • Go Core Team
  • Cluster
  • GUI
  • Infrastructure
• Efforts to Support Specific Uses:
  • Integration with Web Browsers
  • Dynamic Data and Capabilities
  • Decentralized Data Stewardship
  • Local Offline Collaboration
• Community
• Project WG

[daviddias]

Also, has it is now traditional, there will be an Open Call to introduce OKRs to everyone led by @steverichmond on Dec 19, 5pm UTC

The agenda looks like this (sorting was done to make it timezone friendly):

Zoom URL: https://protocol.zoom.us/my/steverichmond

[daviddias]

@ipfs/working-group-captains

[daviddias]

Cluster, GUI, Infrastructure, Integration with Web Browsers, Dynamic Data and Capabilities, Decentralized Data Stewardship and Local Offline Collaboration, we are missing your PRs/Open Planning Discussion points.

[momack2]

We have one for Local Offline Collab here: ipfs/local-offline-collab#5, but also created the reference file here: #803

[daviddias]

Two kind reminders:

• Use this Open OKR Planning as an opportunity to propagate requests, asks, check in with other Working Groups Plans.
• Draft OKRs presentations are on Dec 19th. It is ok if you then have to update them after, but they should be a close representation of the work that is planned Q1 2019.

[daviddias]

Hi everyone again!

Today I've a "protip" to share with you all. To avoid the trap of overloading your OKRs spreadsheets, consider checking in on how much time you have actually available during the quarter an plan for 60% of that only.

Q1 roughly looks like this

Nevertheless, that is the maximum available. You should take out the days you are going to spend at conferences, hack weeks, research retreats, etc and only then calculate your 60%. Here is an example:

• 13 weeks in the quarter - 65 days (assuming 5 day work week)
• Take out the first 2 days (NYE and Jan 1) - 63
• Now if you happen to have planned 15 days of Vacation + Hack Weeks + conferencing, etc. Then you have left 48 days.
• 48 days in a 8 hour work day is 384 hours
• 60% of that is 230.4 hours

In this example, the OKRs should only contemplate work you could do in 230.4 hours. And yes, it is incredibly hard to estimate how much time a task does, but we often fall into the trap of planning 3x to 5x the work we could possibly do in the time we have available, so this exercise is a good tool to help us prioritize and drop stuff right before the Quarter starts.

See my calculation here -- #793 (comment)