Update handbook with Quad Planning Process and DRIs

Mek Stittrirequested to merge
ms-quad-planning into master

Per proposal in #6318 (closed)

  • Adds to the planning process how Software Engineer in Test works inside the product planning process.
  • Update labeling nomenclature of quad-planning label.
  • Update our product handbook to have quad dris

This improvement to our planning aims to align GitLab's product and engineering process to include our modern take on the three amigo process.

In the world of scrum/agile/devops, the leading principle of baking software quality in early is to involve test expertise much earlier in the planning cycle. This process is known as the three amigos. This is the industry standard for teams that ship high-quality software.

We initially had a brief mention of this when rolling out the new Product Development workflow https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/25877/diffs?diff_id=48249938&start_sha=d516573e0683e1bf9df842d75c3923d29013f78c#2e3fd5ad1348b4a72833e2785a0b4d41dc6ca282_49_49. This iteration evolves the process further with clear actionable items and measurement.

Plan

We currently have the trio dris that are engaged in product planning https://about.gitlab.com/handbook/product/#pm-em-and-ux-trio-dris. This plan evolves the trio into quad to include Software Engineers in Test (SET/SDET).

  1. Product Managers
  2. Engineering Managers
  3. UXers
  4. SETs

These 4 areas are the main pillars to ensure we can continue to ship features while ensuring optimal test coverage. Velocity is only productive when we don't incur test debt. We want to be nimble while shipping less bugs thus improving our own velocity. One can look at the metaphor of the 4 legs of the Tanuki, without either one of it's legs the Tanuki isn't able to run as fast.

Screen_Shot_2020-01-19_at_9.15.28_PM_copy

Does this MR meet the acceptance criteria?

Conformity

Edited by Mek Stittri

Merge request reports