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

Define Q4 2018 OKRs for In Web Browsers & GUI Efforts #110

Closed
lidel opened this issue Sep 10, 2018 · 5 comments
Closed

Define Q4 2018 OKRs for In Web Browsers & GUI Efforts #110

lidel opened this issue Sep 10, 2018 · 5 comments
Assignees

Comments

@lidel
Copy link
Member

lidel commented Sep 10, 2018

Q4 Planning is almost here.

First, let's do Q3 Retrospective:

We should have OKRs frozen before Q4 planning calls (Sept 24-28).
Still time, but we should start thinking about OKRs for Q4.

Let's start with async brainstorming in https://hackmd.io/hWRiAeruRnq9nWN2iw8gug

  • think what excites you: got a pet browser-related OKRs for Q4?
    • are our objectives the same, or do we want to reformulate them?
    • what KRs are an ongoing effort and need to be copied from Q3?
    • what to add?

Just put/comment things there, and we will have an outline for Q4 kick-off meeting next week which will produce first draft of OKRs.

cc ipfs/team-mgmt#698

@lidel
Copy link
Member Author

lidel commented Sep 17, 2018

We will have a call on Wednesday to discuss Q4 OKRs and produce initial draft for both WGs.
Before that call, let's do async retrospective of Q3:

If this is your first retrospective, a good summary of the process is at ipfs/team-mgmt#698:

Async Retrospective of the Quarter

Running an Async Retrospective will give everyone in the team to clearly communicate what was achieved and not achieved in the quarter. It will also give the opportunity to signal things that can be improved and these can go from communication, structure, launch of features or anything that a team member finds important for the team to know.

These retrospectives enable us to check in with ourselves and prepare the following quarter better taking into consideration everything happened in the past. It also gives our future selves a way to check in with the past and see how far we have progressed.

You can see a great example of one of these with the JS Core Dev Q2 Retrospective. The whole team got to voice and learn from everyone else perspective.

@lidel
Copy link
Member Author

lidel commented Sep 24, 2018

Initial OKR drafts landed in public spreadsheets and are ready for feedback

@lidel
Copy link
Member Author

lidel commented Sep 26, 2018

Please check the above spreadsheets and let us know if you want to become an Owner of something specific.

(I've put myself in remaining OKRs for WB WG, but if anyone is excited and want to help with something specific or even be an owner of a KR, I will be happy to give it back)

@lidel
Copy link
Member Author

lidel commented Oct 3, 2018

Any last thoughts, comments or updates, before we make OKRs for Q4 official? :)

@lidel
Copy link
Member Author

lidel commented Oct 29, 2018

@lidel lidel closed this as completed Oct 29, 2018
@ghost ghost removed the status/in-progress In progress label Oct 29, 2018
@ghost ghost unassigned kyledrake Mar 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants