Commit e088fe81 authored by Tommy Morgan's avatar Tommy Morgan

Merge branch 'rnienaber-geo-2018Q4-okr-doc' into 'master'

Geo Team 2018Q4 OKR's

See merge request !18068
parents a19c7e6a 1dc15ba8
Pipeline #43275201 passed with stages
in 13 minutes and 41 seconds
......@@ -81,8 +81,8 @@ title: "Calendar Year 2018 Q4 OKRs"
* Manage:
* Spend no more than 15 point of our [error budget]: 15/15 [#536](https://gitlab.com/gitlab-com/gl-infra/production/issues/536)
* Geo:
* Spend no more than 15 point of our [error budget]: 0/15
* Complete all issues in Phase 1 of the DR/HA plan working with the Production Team ()
* Spend no more than 15 point of our [error budget]: 15/15 [#5215](https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/5215) (100%)
* Complete all issues in Phase 1 of the DR/HA plan working with the Production Team : We supported the Production Team with all questions and issues raised. Work to enable Geo for DR on GitLab.com continues. (100%)
* Distribution:
* Spend no more than 15 point of our [error budget]: 0/15 => 100%
* [Automate library upgrades](https://gitlab.com/gitlab-org/distribution/team-tasks/issues/194) across distributed projects => 75%, completed work related to the omnibus-gitlab package but Helm Charts process still needs work.
......@@ -193,7 +193,7 @@ title: "Calendar Year 2018 Q4 OKRs"
* Team to deliver 10 topic-specific knowledge sharing sessions
(“201s”) by the end of Q4 (4 completed)
* Geo:
* At least one Geo team member to advance to Geo Maintainer ()
* At least one Geo team member to advance to Maintainer (0%) : Two engineers are in the group being trained to be maintainers.
* Distribution:
* Source 25 candidates (at least 5 by direct manager contact) by
October 15 and hire 2 developers: 25 sourced (100%), 1 hired (50%)
......@@ -359,11 +359,16 @@ title: "Calendar Year 2018 Q4 OKRs"
#### Geo
* GOOD
* ...
* Reinstated the monthly team call which was received well by the team.
* Cycle time on reviews (done on Geo work by the Geo team) has been reduced by concentrating on making sure that others are unblocked.
* The team felt that they accomplished a lot on items like bug fixing, refactoring, performance improvements and documentation.
* BAD
* ...
* Some issues were not as prepared as they could have been and as a result the issues included in the milestone changed a lot during a month.
* For some issues we were delayed in waiting for specialized reviewers. We know that there are improvements to the DB review process coming soon, and we look forward to these changes being in place.
* We struggled with an erroneous revert as part of the automatic CE->EE merging. It wasn’t immediately clear that the revert had happened.
* It was hard to know if some of the QA failures were due to our work or due to work on the QA framework itself. It is difficult and slow to figure out the difference
* TRY
* ...
* We need to spend more time in planning. We will introduce a process in 11.8 and see how this enables us to have more predictable deliverables in a milestone
#### Manage
......
Markdown is supported
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