Confirmed users
1,567
edits
Compatibility/Meetings/2018-03-20: Difference between revisions
Jump to navigation
Jump to search
→Q2 OKRs planning (miketaylr): fixing link and markup
m (date change) |
(→Q2 OKRs planning (miketaylr): fixing link and markup) |
||
| Line 6: | Line 6: | ||
=== Q2 OKRs planning (miketaylr) === | === Q2 OKRs planning (miketaylr) === | ||
'''Let's start this now so we're ready to hit the ground running for Q2. Step 1. check out proposed Objectives https://github.com/mozilla/webcompat-team-okrs/projects/1 Step 2. use the following form to suggest KRs for them, or suggest new OKRs entirely | '''Let's start this now so we're ready to hit the ground running for Q2.''' | ||
* Step 1. check out proposed Objectives https://github.com/mozilla/webcompat-team-okrs/projects/1 | |||
* Step 2. use the following [https://docs.google.com/forms/d/e/1FAIpQLSf5LQtOeq_WmTo-5HaYuI89-iKLJ3OVf7jpDIhpSSlclFPLDA/viewform form to suggest KRs for them], or suggest new OKRs entirely. | |||
* '''karl''': tried to access the form, but it's not accessible. | * '''karl''': tried to access the form, but it's not accessible. | ||
* '''mike''': I want to work asynchronously on this. So I will just introduced it today. Let's try to use Github to manage OKRs this quarter. As an example of what this would look like: https://github.com/mozilla/activity-stream-okrs/projects/6. For each KR we create an issue. Each KR has an owner, that can give a status update (but doesn't have to do all the work for that KR). Will give confidence in % points which should be easier to understand. Once items are in backlog / pending / done we can move them across to the appropriate column. You will need to be in the Mozilla Github org, there's a mana page for this Mike will send an email about it. | * '''mike''': I want to work asynchronously on this. So I will just introduced it today. Let's try to use Github to manage OKRs this quarter. As an example of what this would look like: https://github.com/mozilla/activity-stream-okrs/projects/6. For each KR we create an issue. Each KR has an owner, that can give a status update (but doesn't have to do all the work for that KR). Will give confidence in % points which should be easier to understand. Once items are in backlog / pending / done we can move them across to the appropriate column. You will need to be in the Mozilla Github org, there's a mana page for this Mike will send an email about it. | ||
| Line 16: | Line 18: | ||
* '''mike''': No. Also as a reminder key results should be something you can assign a value to completion / or measure success | * '''mike''': No. Also as a reminder key results should be something you can assign a value to completion / or measure success | ||
* '''karl''': in the Google doc it says 2 to 5, what does that mean? | * '''karl''': in the Google doc it says 2 to 5, what does that mean? | ||
* '''mike''': each Objective should have 2 to 5 Key Results that make it up. | * '''mike''': each Objective should have 2 to 5 Key Results that make it up. | ||
=== webcompat.com release plan (ola) === | === webcompat.com release plan (ola) === | ||