Improve Dogfooding process
We should see if we can improve our dogfooding process. Right now there seem to be a few challenges:
- Awareness of
5xrule documented in the handbook: https://about.gitlab.com/handbook/product/product-processes/#dogfooding-process - Inconsistent opening of dogfooding issues when product groups are developing features
- Review the prioritization of dogfooding versus other work for Product/Engineering
- No documented prioritization framework of dogfooding issues
Proposed path forward
- Reinforce the dogfood first mindset,
5xrule - @awthomas- Highlight the MR and the 5x rule in PM meeting: Done https://gitlab.slack.com/archives/C0NFPSFA8/p1604424309331500
- Add to Infra handbook / reminder: www-gitlab-com!67178 (merged)
- Better embed dogfooding into the product development process, to increase coverage and shift-left - @awthomas
- Validate with the broader team on whether
dogfoodingis currently prioritized appropriately. Itis fairly low on the list today. - @joshlambert - Evaluate whether the existing dogfooding board is representative of the in-flight dogfooding work, whether we can build some metrics around this - @awthomas
- Metrics dashboard: https://app.periscopedata.com/app/gitlab/771297/Dogfooding-Activity-Dashboard
- Double check infra issues to ensure
Dogfoodinglabel is being applied. Discussion here: gitlab-com/gl-infra/mstaff#19 (comment 441840995)
- Better document the Infra intake process, including a prioritization framework if there is contention.
- Effort to dogfood
- Return on dogfooding
- Whether the feature is receiving continued investment
Edited by Andrew Thomas