Skip to content

Add Plan 15.0 retro corrective actions

John Hope requested to merge jh-15-0-plan-retro-followups into master

Why is this change being made?

See 15.0 Plan retrospective (gl-retrospectives/plan#75 - closed)

I would like to refactor this handbook page a lot, now that there's quite a lot of guidance about spikes. However, this change attempts to capture the corrective actions from the 15.0 retro for now.

  1. Establish an internal release cut-off date, before which a feature should be deployed, tested and FF enabled on GitLab.com to allow for time to fix remaining defects. Date should be 15th (or release cut-off - 2d) (see gl-retrospectives/plan#75 (comment 958417436), gl-retrospectives/plan#75 (comment 958420913)) @kushalpandya @mushakov @cngo @digitalmoksha
  2. Improve collaboration on Spikes (See gl-retrospectives/plan#75 (comment 960488326)) @fguibert @egrieff @mushakov @gweaver
    1. Assign FE, BE and UX to each spike at the start of the milestone.
    2. Description is kept up-to-date with acceptance criteria. PM, EM, Eng and UX sign off on scope before work starts.
    3. Any higher-level architectural blueprints (e.g. for Work Items) are kept up-to-date with outcome of spike.
  3. Include docs counterpart (@msedlakjakubowski) in planning for features.

This only makes the change on the Product Planning page but I will aim to put this in a reusable partial for the groupproject management page also.

Author Checklist

  • Provided a concise title for this Merge Request (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 MR to the correct Directly Responsible Individual/s (DRI)
    • 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 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.
Edited by John Hope

Merge request reports