Skip to content
Snippets Groups Projects
Commit c255b1b6 authored by Toon Claes's avatar Toon Claes
Browse files

Various OKR improvements 

Various changes:

- Some KRs for Geo added.
- Use blockquotes in Critical acclaim
- Advise to use format `Owner:` to define a Key Result that is
  countable per Owner (each Owner should have max 9 KRs)
parent 2de34071
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
README.md
+ 0
− 2
View file @ c255b1b6
@@ -116,8 +116,6 @@ To test out the site, you must run another Web server from the
This will start a Web server on port 8000 (you may omit the port number). You can preview the site
by pointing your browser to http://localhost:8000.
 
[gh-livereload]: https://github.com/middleman/middleman-livereload/issues/60
## Review Apps
 
Thanks to the [Review Apps], the `www-gitlab-com` project supports live reviewing
doc/development.md
+ 2
− 0
View file @ c255b1b6
@@ -50,3 +50,5 @@ export ENABLE_LIVERELOAD=1
>**Note:**
You need to logout and login in order for the changes to take effect. To
temporarily use the changes, run `source ~/.bashrc`.
[gh-livereload]: https://github.com/middleman/middleman-livereload/issues/60
source/okrs/index.html.md
+ 102
− 94
View file @ c255b1b6
@@ -39,7 +39,7 @@ Part of the individual performance review is the answer to: how much did this pe
We have no more than [five layers in our team structure](https://about.gitlab.com/team/structure/).
Because we go no further than the team level we end up with a maximum 4 layers of indentation on this page (this layer count excludes the three company/CEO objectives).
The match of one "nested" key result with the "parent" key result doesn't have to be perfect.
Every team should have at most 9 key results. To make counting easier only mention the team and people when they are the owner.
Every owner should have at most 9 key results. To make counting easier always mention the owner with a trailing colon, like `Owner:`.
The advantage of this format is that the OKRs of the whole company will fit on 3 pages, making it much easier to have an overview.
 
## Updating
@@ -79,13 +79,17 @@ It's important to score OKRs after the quarter ends to make sure we celebrate wh
 
## Critical acclaim
 
Spontaneous chat messages from team members after introducing this:
Spontaneous chat messages from team members after introducing this format:
 
- As the worlds biggest OKR critic, This is such a step in the right direction :heart: 10 million thumbs up
- I like it too, especially the fact that it is in one page, and that it stops at the team level.
- I like: stopping at the team level, clear reporting structure that isn't weekly, limiting KRs to 9 per team vs 3 per team and 3 per each IC.
- I've been working on a satirical blog post called called "HOT NEW MANAGEMENT TREND ALERT: RJGs: Really Just Goals" and this is basically that. :wink: Most of these are currently just KPIs but I won't say that too loudly :wink: It also embodies my point from that OKR hit piece: "As team lead, it’s your job to know your team, to keep them accountable to you, and themselves, and to be accountable for your department to the greater company. Other departments shouldn’t care about how you measure internal success or work as a team, as long as the larger agreed upon KPIs are aligned and being met."
- I always felt like OKRs really force every person to limit freedom to prioritize and limit flexibility. These ones fix that!
> As the worlds biggest OKR critic, This is such a step in the right direction :heart: 10 million thumbs up
> I like it too, especially the fact that it is in one page, and that it stops at the team level.
> I like: stopping at the team level, clear reporting structure that isn't weekly, limiting KRs to 9 per team vs 3 per team and 3 per each IC.
> I've been working on a satirical blog post called called "HOT NEW MANAGEMENT TREND ALERT: RJGs: Really Just Goals" and this is basically that. :wink: Most of these are currently just KPIs but I won't say that too loudly :wink: It also embodies my point from that OKR hit piece: "As team lead, it’s your job to know your team, to keep them accountable to you, and themselves, and to be accountable for your department to the greater company. Other departments shouldn’t care about how you measure internal success or work as a team, as long as the larger agreed upon KPIs are aligned and being met."
> I always felt like OKRs really force every person to limit freedom to prioritize and limit flexibility. These ones fix that!
 
## No hiring as an objective
 
@@ -97,112 +101,116 @@ These are the OKRs for 2018 Q1.
 
### Objective 1: Grow Incremental ACV according to plan
 
* CEO Revenue expansion to 200%
* CEO: Revenue expansion to 200%
* Sales: Identify success factors
* Sales: Do quarterly business reviews for all eligible customers
* CEO: Be at a sales efficiency of 1.0 or higher
* Marketing: know cost per SQO and customer for each of our campaigns
* CEO: Make sure that 70% of salespeople are at 70% of quota
* Marketing: make sure each SAL has 10 leads per month
* Marketing: Make sure each SAL has 10 leads per month
* Sales: 1 month boot-camp for sales people with rigorous testing
* Support
* 100% Premium and Ultimate SLA achievement
* Support: 100% Premium and Ultimate SLA achievement
 
### Objective 2: Popular next generation product
 
* CEO: GitLab.com ready for mission critical workloads
* VPE: move .com to GKE with Geo
* VPE: .com available 99.95% and monthly disaster recovery exercises
* VPE: .com speed index < 1.5s for all tested pages
* CEO On track to deliver all features of [complete DevOps](https://about.gitlab.com/2017/10/11/from-dev-to-devops/)
* VPE: ship faster than before
* Product: plan all features to be done by July 22
* [One codebase with /ee subdirectory](https://gitlab.com/gitlab-org/gitlab-ee/issues/2952)
* VPE: Move GitLab.com to GKE
* Geo: Make Geo performant to work at GitLab.com scale
* Build: TBD?
* Gitaly: TBD?
* CI/CD: TBD?
* VPE: GitLab.com available 99.95% and monthly disaster recovery exercises
* VPE: GitLab.com speed index < 1.5s for all tested pages
* CEO: On track to deliver all features of [complete DevOps](https://about.gitlab.com/2017/10/11/from-dev-to-devops/)
* VPE: Ship faster than before
* Product: Plan all features to be done by July 22
* VPE: [One codebase with /ee subdirectory](https://gitlab.com/gitlab-org/gitlab-ee/issues/2952)
* CEO: Make it popular
* Marketing: Get unique contributors per release to 100
* Marketing: Increase total users by 5% per month
* Marketing: Facilitate 100 ambassador events (meetups, presentations)
* Marketing: be a leader in all relevant analyst reports
* Marketing: Be a leader in all relevant analyst reports
* VPE: Use all of GitLab ourselves (monitoring, release management)
* UX
* [Complete design pattern library, setting usability standards and solutions for design, development, and product management to implement and follow.](https://gitlab.com/groups/gitlab-org/-/epics/29)
* [Complete comprehensive evaluation to identify and prioritize accessibility issues. Maintain backlog and push a minimum of 3 fixes to product per release.](https://gitlab.com/groups/gitlab-org/-/epics/31)
* [Conduct UX Research to identify and prioritize three usability problems affecting non-technical users and under-represented groups.](https://gitlab.com/groups/gitlab-org/-/epics/32)
* Maintain a prioritized UX issue backlog. Push a minimum of five UX Ready, UX Debt, or UX bug issues to product per release.
* UX: [Complete design pattern library, setting usability standards and solutions for design, development, and product management to implement and follow.](https://gitlab.com/groups/gitlab-org/-/epics/29)
* UX: [Complete comprehensive evaluation to identify and prioritize accessibility issues. Maintain backlog and push a minimum of 3 fixes to product per release.](https://gitlab.com/groups/gitlab-org/-/epics/31)
* UX: [Conduct UX Research to identify and prioritize three usability problems affecting non-technical users and under-represented groups.](https://gitlab.com/groups/gitlab-org/-/epics/32)
* UX: Maintain a prioritized UX issue backlog. Push a minimum of five UX Ready, UX Debt, or UX bug issues to product per release.
* Geo
* Reduce bug backlog to 0
* Bugs squashed in month _M_ &ge; bugs reported in month _M-1_
* Full project-standard unit test coverage for Geo functionality
* GitLab-QA tests cover all basic Geo functionality as described in GitLab EE documentation
* Deliver 100% of feature commits in 10.5, 10.6
* Geo: Make [Geo Disaster Recovery](https://gitlab.com/gitlab-org/gitlab-ee/issues/846) Generally Available
* Geo: Reduce bug backlog to 0
* Geo: Bugs squashed in month _M_ &ge; bugs reported in month _M-1_
* Geo: Full project-standard unit test coverage for Geo functionality
* Geo: GitLab-QA tests cover all basic Geo functionality as described in GitLab EE documentation
* Geo: Deliver 100% of feature commits in 10.5, 10.6
* Build
* Upgrade omnibus and internal omnibus-gitlab Chef
* Measure upgrade/installation time between two GitLab versions. Collect information on user installation methods.
* Establish a roadmap for automated vulnerability reporting of shipped libraries
* Cloud Native Helm charts in Alpha
* Ship 100% of committed deliverables issues each release
* Build: Upgrade omnibus and internal omnibus-gitlab Chef
* Build: Measure upgrade/installation time between two GitLab versions. Collect information on user installation methods.
* Build: Establish a roadmap for automated vulnerability reporting of shipped libraries
* Build: Cloud Native Helm charts in Alpha
* Build: Ship 100% of committed deliverables issues each release
* Platform
* Make sure all [Platform backend community contributions](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Community%20Contribution&label_name[]=Platform) are merged, closed, labeled “awaiting feedback”, or taken over by us an in active development
* Resolve or schedule all AP1, AP2, SP1, and SP2 issues
* Reduce Platform backend bug backlog by 50%
* Test backup/restore using GitLab QA
* Ship [first GraphQL endpoint](https://gitlab.com/gitlab-org/gitlab-ce/issues/34754)
* Ship 100% of committed deliverables issues each release
* Platform: Make sure all [Platform backend community contributions](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Community%20Contribution&label_name[]=Platform) are merged, closed, labeled “awaiting feedback”, or taken over by us an in active development
* Platform: Resolve or schedule all AP1, AP2, SP1, and SP2 issues
* Platform: Reduce Platform backend bug backlog by 50%
* Platform: Test backup/restore using GitLab QA
* Platform: Ship [first GraphQL endpoint](https://gitlab.com/gitlab-org/gitlab-ce/issues/34754)
* Platform: Ship 100% of committed deliverables issues each release
* Discussion
* Make sure all [Discussion backend community contributions](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Community%20Contribution&label_name[]=Discussion) are merged, closed, labeled “awaiting feedback”, or taken over by us and in active development
* Resolve or schedule all AP1, AP2, SP1, and SP2 issues
* Reduce Discussion backend bug backlog by 50%
* Ship Rails 5 migration
* Ship 100% of committed deliverables issues each release
* Discussion: Make sure all [Discussion backend community contributions](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Community%20Contribution&label_name[]=Discussion) are merged, closed, labeled “awaiting feedback”, or taken over by us and in active development
* Discussion: Resolve or schedule all AP1, AP2, SP1, and SP2 issues
* Discussion: Reduce Discussion backend bug backlog by 50%
* Discussion: Ship Rails 5 migration
* Discussion: Ship 100% of committed deliverables issues each release
* CI/CD
* Resolve or schedule all AP1, AP2, SP1, and at least 5 SP2 issues
* Scalability: Make all CI/CD related data to be stored on Object Storage
* Performance: Ensure that 95% of pipeline jobs are picked within the first 10s for projects currently not having any jobs running
* Cost: Move all CI infrastructure to GCP
* Quality: Test CI workflow with Runner by GitLab QA
* Ship 100% of committed deliverables issues each release
* CI/CD: Resolve or schedule all AP1, AP2, SP1, and at least 5 SP2 issues
* CI/CD: Scalability: Make all CI/CD related data to be stored on Object Storage
* CI/CD: Performance: Ensure that 95% of pipeline jobs are picked within the first 10s for projects currently not having any jobs running
* CI/CD: Cost: Move all CI infrastructure to GCP
* CI/CD: Quality: Test CI workflow with Runner by GitLab QA
* CI/CD: Ship 100% of committed deliverables issues each release
* Prometheus
* Bundle Alertmanager for proactive customer alerting notifications
* Prometheus deploy for customer apps feature
* Ship 10 new alerts for monitoring GitLab
* Instrument gitlab-shell
* Ship 100% of committed deliverables issues each release
* Prometheus: Bundle Alertmanager for proactive customer alerting notifications
* Prometheus: Prometheus deploy for customer apps feature
* Prometheus: Ship 10 new alerts for monitoring GitLab
* Prometheus: Instrument gitlab-shell
* Prometheus: Ship 100% of committed deliverables issues each release
* Security
* GDPR: Complete data breach notification policy and data mapping requirements
* FIPS 140-2: Research requirements and provide guidance to development team to implement
* SOC 2: Research requirements and build initial roadmap to achieve compliance
* Complete Remainder of 10 Risk Assessment Actions
* Automate metrics for vulnerability initiatives: HackerOne, external & internal assessments
* All parts of security active (AppSec-JR, Automation-JT, SecOps-KW/JT/JR, Abuse-KW/JT/JR, Compliance-KW)
* Security: GDPR: Complete data breach notification policy and data mapping requirements
* Security: FIPS 140-2: Research requirements and provide guidance to development team to implement
* Security: SOC 2: Research requirements and build initial roadmap to achieve compliance
* Security: Complete Remainder of 10 Risk Assessment Actions
* Security: Automate metrics for vulnerability initiatives: HackerOne, external & internal assessments
* Security: All parts of security active (AppSec-JR, Automation-JT, SecOps-KW/JT/JR, Abuse-KW/JT/JR, Compliance-KW)
* Database
* [Make it more difficult for database performance issues to occur](https://gitlab.com/gitlab-com/infrastructure/issues/3474)
* [Improve workflow / structure of the database team](https://gitlab.com/gitlab-com/infrastructure/issues/3475)
* [Improve database performance](https://gitlab.com/gitlab-com/infrastructure/issues/3476)
* Database: [Make it more difficult for database performance issues to occur](https://gitlab.com/gitlab-com/infrastructure/issues/3474)
* Database: [Improve workflow / structure of the database team](https://gitlab.com/gitlab-com/infrastructure/issues/3475)
* Database: [Improve database performance](https://gitlab.com/gitlab-com/infrastructure/issues/3476)
* Gitaly
* Deliver 100% of committed scope for GCP migration milestone #2 by Jan 15
* Deliver 100% of committed scope for GCP migration milestone #3 by Feb 15
* Deliver 100% of committed scope for GCP migration milestone #4 by Mar 15
* All migration points complete to Ready-for-Testing state by 7 February
* All endpoints complete to Opt-In state (including ones currently disabled due to n+1)
* Hit 1.0 (all endpoints complete to Opt-Out state)
* Gitaly: Deliver 100% of committed scope for GCP migration milestone [#2](https://gitlab.com/gitlab-com/migration/milestones/2) by Jan 15
* Gitaly: Deliver 100% of committed scope for GCP migration milestone #3 by Feb 15
* Gitaly: Deliver 100% of committed scope for GCP migration milestone #4 by Mar 15
* Gitaly: All migration points complete to Ready-for-Testing state by 7 February
* Gitaly: All endpoints complete to Opt-In state (including ones currently disabled due to n+1)
* Gitaly: Hit 1.0 (all endpoints complete to Opt-Out state)
* Quality
* Define the architecture of and produce an end-to-end prototype for a self-service metrics generator
* Quality: Define the architecture of and produce an end-to-end prototype for a self-service metrics generator
* Edge
* [De-duplicate at least 5 redundant (feature) tests](https://gitlab.com/gitlab-org/gitlab-ce/issues/39829)
* Improve at least the [5 longest spec files](https://redash.gitlab.com/queries/15) by at least 30%
* Investigate code with less than 60% tests coverage and add tests for at least the [5 most critical files](https://gitlab.com/gitlab-org/gitlab-ce/issues/19412)
* [Investigate encapsulating instance variables](https://gitlab.com/gitlab-org/gitlab-ce/issues/20045) about the current page in a class
* [Reduce duplication](https://gitlab.com/gitlab-org/gitlab-ce/issues/31574) in at least 5 forms
* Solve at least 3 [outstanding performance issues](https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=performance&milestone_title=No+Milestone)
* Complete the work to [make GitLab QA production-ready](https://gitlab.com/gitlab-org/gitlab-qa/issues/126)
* Define and schedule high-value issues for [improving the staging test environment](https://gitlab.com/gitlab-com/infrastructure/issues/3177)
* Write 3 tests related to creating and managing Issues
* Write 3 tests related to CI/CD
* Edge: [De-duplicate at least 5 redundant (feature) tests](https://gitlab.com/gitlab-org/gitlab-ce/issues/39829)
* Edge: Improve at least the [5 longest spec files](https://redash.gitlab.com/queries/15) by at least 30%
* Edge: Investigate code with less than 60% tests coverage and add tests for at least the [5 most critical files](https://gitlab.com/gitlab-org/gitlab-ce/issues/19412)
* Edge: [Investigate encapsulating instance variables](https://gitlab.com/gitlab-org/gitlab-ce/issues/20045) about the current page in a class
* Edge: [Reduce duplication](https://gitlab.com/gitlab-org/gitlab-ce/issues/31574) in at least 5 forms
* Edge: Solve at least 3 [outstanding performance issues](https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=performance&milestone_title=No+Milestone)
* Edge: Complete the work to [make GitLab QA production-ready](https://gitlab.com/gitlab-org/gitlab-qa/issues/126)
* Edge: Define and schedule high-value issues for [improving the staging test environment](https://gitlab.com/gitlab-com/infrastructure/issues/3177)
* Edge: Write 3 tests related to creating and managing Issues
* Edge: Write 3 tests related to CI/CD
* Frontend
* Write 120 unit tests to resolve test debt
* Crush 280 backlogged bugs
* Ship 100% of committed deliverables issues each release
* Make sure all [Frontend community contributions](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Community%20Contribution&label_name[]=frontend) are merged, closed, labeled “awaiting feedback”, or taken over by us an in active development
* Frontend: Write 120 unit tests to resolve test debt
* Frontend: Crush 280 backlogged bugs
* Frontend: Ship 100% of committed deliverables issues each release
* Frontend: Make sure all [Frontend community contributions](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Community%20Contribution&label_name[]=frontend) are merged, closed, labeled “awaiting feedback”, or taken over by us an in active development
 
### Objective 3: Great team
 
@@ -214,22 +222,22 @@ These are the OKRs for 2018 Q1.
* CEO: Keep the handbook up-to-date so we can scale further
* Handbook first (no presentations about evergreen content)
* Consolidate and standardize role descriptions
* VPE
* Consolidate and standardize job descriptions
* VPE: Consolidate and standardize job descriptions
* VPE: Plan 2018 Q2
* Launch 2018 Q2 department OKRs before EOQ1 2018
* Set 2018 Q2 hiring plan EOQ1 2018
* Implement issue taxonomy changes to improve prioritization
* Record an on-boarding video of how to do a local build and contribute to the GitLab handbook
* VPE: Implement issue taxonomy changes to improve prioritization
* VPE: Record an on-boarding video of how to do a local build and contribute to the GitLab handbook
* Backend
* Deliver two iterations toward aligning backend teams with the DevOps lifecycle
* Support
* Define HA Expertise and train 7 support engineers
* Define Kubernetes Expertise and train 7 support engineers
* Support: Define HA Expertise and train 7 support engineers
* Support: Define Kubernetes Expertise and train 7 support engineers
* UX
* [Deprecate outdated UX Guide and replace with design.gitlab.com to communicate current UX standards and solutions across teams.](https://gitlab.com/groups/gitlab-org/-/epics/30)
* [Write 3 public blog posts about GitLab UX and visual design case studies, best practices, anecdotes, or events](https://gitlab.com/groups/gitlab-org/-/epics/33)
* UX: [Deprecate outdated UX Guide and replace with design.gitlab.com to communicate current UX standards and solutions across teams.](https://gitlab.com/groups/gitlab-org/-/epics/30)
* UX: [Write 3 public blog posts about GitLab UX and visual design case studies, best practices, anecdotes, or events](https://gitlab.com/groups/gitlab-org/-/epics/33)
* Quality
* Document the context and background of release process improvements in the Handbook / Quality page
* Quality: Document the context and background of release process improvements in the Handbook / Quality page
 
## Archive
 
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment