Skip to content

Clarify that Engineering OKRs that need Product help start early

Sean McGivern requested to merge clarify-shared-engineering-and-product-okr-timelines into master

Why is this change being made?

We've had an issue in the past with Engineering OKRs that need Product help, because we 'lose' on both ends:

  1. By the time the OKR process starts, we're too late for the first milestone of the quarter (which actually starts before the fiscal quarter).
  2. We can't extend past the end of the fiscal quarter for the following month's release on the 22nd, because we wrap up this quarter's OKRs and start next quarter's way before that.

From the Engineering Staff meeting notes (https://docs.google.com/document/d/1uaBOKgqYM5-pDWBgfAuOqFYDAA56yVz76lgMvv8jUCQ/edit#bookmark=id.d5afy9hons7w):

Sean: so we're in February, dev starts in March, and that's released in April. Going forward a quarter, we want to start work in April (slightly ahead of the OKRs which go live in May), which means Product need to be in the loop in March.

Justin: Phase 3 of Validation Track starts at least 1 milestone before Build Phase 2 starts. Often 2-3.

Sean: we are agreed on getting Engineering OKRs that need Product involvement over to Product half-way through the quarter (~6 weeks before the next quarter's OKRs are due).

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports