Draft 2018 Q1 Engineering OKRs
It's time to draft 2018 Q1 OKRs! Here is what I would like you all to think about:
- Chip away at the bug backlog (like we did in Q4)
- Chip away at testing gaps (like we did in Q4)
- Merge some amount of community contributions
- Delivery of 100% of feature commits on-time (think about how we measure this)
- Add your own team-specific KR's
I (@edjdev) will take care of the hiring KRs and make sure the plan is correct. Sid requested no hiring KRs going forward.
See our OKR page for procedure and formatting. Please assign the MR for your sub-issue to me for feedback and eventual merge by Friday, December 22, 2017
| Team | Leader | Sub-issue |
|---|---|---|
| Security | @kathyw | #1824 (closed) |
| Quality | @bjgopinath | #1826 (closed) |
| Backend | @stanhu | #1827 (closed) |
| Frontend | @timzallmann | #1828 (closed) |
| Support | @lbot | #1830 (closed) |
| UX Design | @sarrahvesselov | #1829 (closed) |
| Infrastructure | @edjdev | #1831 (closed) |
Please pull in your own managers, or team for collaboration as you see fit!
Edited by Eric Johnson