GMP Onboarding - Verify::Testing

Purpose

This issue will detail the tasks related to getting up to speed and understanding Verify::Testing group vision, roadmap, competitive landscape, team health, process, and partnership across the organization.

Opening Tasks

• Create issue
• Share with James H, @rickywiens BE EM, @samdbeckham FE EM, @v_mishra - Testing Designer (Interim), QA teammate - None, @parker_ennis PMM
• Schedule syncs with the stable counterparts
• Complete Onboarding

Market landscape

• Review key analyst reports in space
• Review CI Use case: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/ci/
• Open MRs as needed
• Prepare deep dive interview with James

Roadmap

• Review Direction Pages of Categories

• https://about.gitlab.com/direction/verify/code_quality/
• https://about.gitlab.com/direction/verify/code_testing/
• https://about.gitlab.com/direction/verify/load_testing/
• https://about.gitlab.com/direction/verify/web_performance/
• https://about.gitlab.com/direction/verify/usability_testing/
• https://about.gitlab.com/direction/verify/accessibility_testing/

• Open MRs as needed
• Review documentation of each category

• https://docs.gitlab.com/ee/ci/unit_test_reports.html
• https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html
• https://docs.gitlab.com/ee/user/project/merge_requests/load_performance_testing.html
• https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html
• https://docs.gitlab.com/ee/ci/metrics_reports.html
• https://docs.gitlab.com/ee/ci/review_apps/#visual-reviews-starter
• https://docs.gitlab.com/ee/user/project/merge_requests/accessibility_testing.html
• https://docs.gitlab.com/ee/ci/pipelines/settings.html#code-coverage-history

• Prepare deep dive interview with James

Backlog health of categories

• Create scorecard for Testing Categories

Relationships across the company

• Review team page https://about.gitlab.com/handbook/engineering/development/ops/verify/testing/
• Review throughput of engineering
  • https://app.periscopedata.com/app/gitlab/681347/MR-Metrics-by-Organization
• Review design process
• Review prior meetings with CS
• Open MRs as needed to process

Sensing Mechanisms

• How are decisions being made?
  • We're trying to focus on epics/features to improve our Performance Indicator, Count of active paid testing users and prioritizing that work. If we cannot build an up-tier feature we will focus efforts to build data and move maturity. You can see a mix of this in our next Code Quality epic.
• What do you rely the on most to prioritize work?
  • Problems/solutions that have been validated by customers (either directly in interviews or async in comments on issues).
• What role do prospects play?
  • Little, we're validating that future features solve their problems but not building to sell into any prospects at this point.
• What do you consider your TAM?
  • Right now the focus is to simply increase usage of paid features amongst existing CI users but we have no measure of what % of CI users are using Testing features.
• Can you share your Opportunity canvases?
  • Canvases that have been presented are on the shared drive