Quad Planning group counterpart mapping and communication plan
We will be rolling out Quad Planning next week so I would like to ensure that everyone is aware of the group that they are in.
| SET | Primary Quad Planning Product Group | Group PM | Group UXer | Proposed Secondary Group | Signed off |
|---|---|---|---|---|---|
| @mlapierre | groupsource code | @jramsay |
@pedroms |
groupgitaly | |
| @sliaquat | ~"group::access" | @jeremy |
@amandakhughes |
n/a | |
| @tmslvnkc | groupknowledge | @cdybenko |
@jareko |
n/a | |
| @wlsf82 | groupproject management | @gweaver |
@hollyreynolds |
~"group::portfolio management" | |
| @dchevalier2 | ~"group::import" | @hdelalic |
@dmoraBerlin |
n/a | |
| @a_mcdonald | ~"group::editor" | @phikai |
@mvanremmerden |
groupgitaly | |
| @ddavison | ~"group::orchestration" | @danielgruesso |
@tauriedavis |
n/a | |
| @zeffmorgan | ~"group::testing" | @jheimbuck_gl |
@jj-ramirez |
n/a | |
| @treagitlab | ~"group::continuous integration" | @jyavorska |
@dimitrieh |
n/a | |
| @svistas | ~"group::apm" | @dhershkovitch |
@nadia_sotnikova |
~"group::health" | |
| @grantyoung | ~"group::memory" | @joshlambert |
@jackib |
n/a | |
| @jennielouie | groupgeo | @fzimmer |
@sunjungp |
n/a | |
| @niskhakova | ~"group::ecosystem" | @deuley |
@lvanc |
n/a | |
| @ebanks | ~"group::search" | @phikai |
@mvanremmerden |
n/a | |
| W.M. Feb 24th | groupcomposition analysis | @NicoleSchwartz |
@kmann |
~"group::exposure analysis" |
@gl-quality/managers please check my assignments and un-backtick :white_check_mark: in the signed off column.
Overall expectations
SETs
When the ~feature proposal issue moves into workflowplanning breakdown. SETs owns the completion of the Availability and Testing section in the Feature Proposal to complete the definition of done. As we grow to reach our desired ratio, we will only have the quad approach in groups where we have an assigned SET in place.
- Assign the issue to yourself if the PM hasn't initiate this and the issue should be multi-assigned along with the counterpart UXer.
- SET is the DRI for the
Availability and Testingsection, ensuring that the strategy accounts for all test levels and facilitating discussions and feedback with the group. - SET determines if the feature change needs to run
package-and-qaregression job, this is made clear in the above section. - SET applies the ~"quad-planning" label and unassign themselves from the issue.
QEMs
For Quality Engineering Managers please:
- Review the assigned product groups here and sign-off.
- You should already be doing some prep and socializing with the EMs, and PMs in the groups above mapped to your team's charter.
- As these issues get tackled please make sure these are surfaced on your team board so you can see the overall activity of your counterpart teams and help/assist/unblock your SETs
Eng Prod
- Engineering Productivity will be helping spinning up GitLab Insights dashboard to visualize how many ~feature issues have ~"quad-planning" per release. gitlab-org/gitlab-insights#160 (closed)
- Dashboard will drill down to each of the product group so we know which area needs more help and hot spots.
cc @gl-quality
Edited by Ramya Authappan