OKRs should be directly linked to the company's strategy.
Key Results are (a) outcome based, or (b) output based.
Answers the question: "How, as a group, will we consider our company successful?"
- Product-specific
- Engineering-specific (quality, stability, speed and best practices)
- list three (or more) tasks
- list quantifiable ways (goals) to achieve these tasks
- track your progress
- Implement best-practices for the dev team to follow.
- Identify useful tools/techniques and integrate them into the team's workflow.
Goals:
- Contribute to dev team's velocity with a goal of improvement of (x)%.
- Launch Tokens feature on time, with minimal bugs.
Goals:
- Compose PR review guide and accompanying checklist.
- Create a Ruby Style Guide.
- Create a JavaScript Style Guide.
- Add Style Guide enforcement/reporting to the Wobbe repository.
- Host education sessions on relevant technology topics to level-up the team. (once a week)
Goals:
- Setup JS/Vue testing in Wobbe by end of Q2 (binary).
- Compose a testing guidelines document (e.g. - When to Unit Test vs. When to Integration test. Guidelines for writing tests.)
- Provide code review and feedback for 100% of Pull Requests (team).
- Remove and replace unmaintained libraries.
- Plan and execute migration of Wobbe to from Rails v3.2 to v4.0 by EOY.
Goals:
- Build side-project in Vue.js.
- Build feature in Vue.js in Wobbe.
- Execute one or more bugfixes in Wobbe's Angular code.
- Study and learn the nuances of MySQL as compared to other RDBMSes (e.g.- PostgreSQL)
- calculating success: (binary, percentage, story points)
- frequency of measurement: (monthly, quarterly, deadline date)
- Startup OKR Template
- Quora: Good OKRs for Engineers
- Agile Goal Setting
- OKRs for your Engineering Team
- Felipe Castro encourages establishing team-based OKRs, first. Then moving to individual based OKRs.