Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
www-gitlab-com
www-gitlab-com
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,242
    • Issues 2,242
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,352
    • Merge requests 1,352
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.com
  • www-gitlab-comwww-gitlab-com
  • Issues
  • #7148

Closed
Open
Created Apr 14, 2020 by Christopher Lefelhocz@clefelhocz1Maintainer

FY21-Q2 Development Department OKRs

[Link to canonical OKR epic]

Objective (IACV): Improve IACV by delivering Gitaly HA and Increase MR Rate to demonstrate strong efficiency => 85.2%

  • Key Result: Gitaly + Praefect use strong consistency => 76%
  • Key Result: Raise MR rate from 11 to 13 => 110%, July largest month yet
  • Key Result: Geo: Achieve Disaster Recovery Viable Maturity => 69.5%

Objective (product): Improvements for better user Experience => 60.5%

  • Key Result: Apply suggestions on improving MR Experience => 80%
  • Key Result: File Tree SpeedIndex <1000 => 41%

Objective (team): Training and culture amp initiatives => 77.5%

  • Key Result: Update training pages for EMs and ICs => 60%
  • Key Result: Implement at least one Culture Amp action item - update career engineering matrix and enforce => 95%

Retrospection

Good

  • MR Rate: July was our largest month yet at 14.4
  • MR Rate: Several teams mentioned they feel they are hitting their stride
  • Gitaly: We delivered as planned the MVC 🎉
  • Geo: Great collaboration between PM and Eng in calibrating the key project of bringing DR to Viable. The Geo team made great progress in Q2.
  • MR Experience: We made significant progress especially towards bigger MR use cases
  • MR Experience: Even across teams (that are not even Dev)
  • MR Experience: Good collaboration on bringing a topic up and then handling it in another team
  • Speed: This was the actual target of the KR but we also improved a lot of numbers especially total load time and first paint across all web vitals
  • Speed: We made a huge push towards more performance based work
  • Speed: Long standing items were finally done
  • Speed: New concepts for loading data + JS
  • Speed: A lot of big initiatives were started or got a big focus (Fontawesome removal, image resizing, Page Specific CSS, Unused CSS,jQuery removal)
  • Speed: New tooling to support it CSS Statistics + GDK Sitespeed runs Couple of improvements that have global impact
  • Speed: Google has not flagged any of our routes as bad performance for desktop anymore since beginning of July
  • Training: Achieved 50% of EMs taking DIB training in one month (1 day of full training)
  • Training: Documented all onboarding training options EMs should review
  • Matrix: Finished up all but one job family position
  • Matrix: career competencies were tried within Dev sub-department

Bad

  • MR Rate: Some teams are feeling they are starting to reach limits
  • MR Rate: Less vacation may be the cause of some of the additional productivity which could lead to other bad results
  • MR Experience: Unclear for quite some time what we are going to tackle
  • MR Experience: Also unclear in those overlapping topics who is responsible of getting it scheduled
  • MR Experience: Due to that delays in execution
  • Speed: Too ambitious for one quarter and quite simply a lot of work
  • Speed: Lot of huge Do it all before you see impact initiatives like the icons
  • Speed: Our CSS is still huge and tackling that started only in July
  • Speed: A lot of dependencies involved, like jQuery removal lead to no impact so far
  • Speed: Hard to identify from early on the best changes for impact so some of the issues came in late
  • Speed: Not enough bandwidth in teams to tackle the topics fully
  • Training: Didn't get Feature Flag Training in place this quarter
  • Matrix: We cut it close to the end of the quarter and didn't distribute/delegate fast enough.

Try

  • MR Rate: Switch to Member MR Rate based on authorship.
  • MR Experience: Clear DRI for all issues, who coordinates across teams
  • MR Experience: Clear setting of Priority through labels and deadlines for everyone to show the importance to help in scheduling
  • Speed: Keep pushing on performance topic in Q3
  • Speed: Define clearer targets around web vitals
  • Speed: Spread performance knowledge in teams
  • Training: Continue to look at additional book clubs/training opportunities for managers
  • Matrix: Start earlier in the quarter with distribution of work and plan.
Edited Aug 10, 2020 by Eric Johnson
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking