Verified Commit cf4393d6 authored by Gabe Weaver's avatar Gabe Weaver 🌀
Browse files

updates project management pi data

parent 2bbfac94
......@@ -234,7 +234,7 @@
base_path: "/handbook/product/performance-indicators/"
definition: Number of unique users interacting with an issue (open, close, reopen,
adjust label, adjust milestone, adjust weight, comment)
target: 437,490 for All, 101,835 for Paid
target: 484,510 for All, 148,176 for Paid
org: Dev Section
section: dev
stage: plan
......@@ -246,18 +246,20 @@
is_key: false
lessons:
learned:
- The decline in SaaS for December does not seem isolated to Plan as nearly every group has a lower SaaS xMAU for the month. This is likely attributable more people taking extended vacations during the holiday season.
- The top 50 Plan paid self-managed customers, as well as the paid customers with the most expansion and shrinkage MoM. See the bottom of [this dashboard](https://app.periscopedata.com/app/gitlab/775807/Plan-xMAU-(monthly))
- The "health status" feature usage is [almost non-existent](https://app.periscopedata.com/app/gitlab/775807/Plan-xMAU-(monthly)?widget=10444593&udv=0) and we should consider down-tiering or continuing to iterate on it by automating it and integrating it into Boards and Roadmaps.
- Quantitative issue field level data validates that less frequently used fields -- such as setting confidentiality and locking an issue -- should be [moved into the secondary menu](https://gitlab.com/gitlab-org/gitlab/-/issues/296959) within the issue header to decrease clutter in the sidebar.
- Only 28% of instances are currently on a version with the new Plan xMAU metric counters.
- The ratio of [net new Paid GMAU to churned Paid GMAU](https://app.periscopedata.com/app/gitlab/775807/Plan-xMAU-(monthly)?widget=10634701&udv=0) improved from 3.75 in December to 3.99 in January, which indicates net retention for Plan Paid users is healthy.
- MAU interacting with Iterations increased by 52% from December to January. The next step to drive feature adoption is more holistically integrating Iterations into Boards.
monthly_focus:
goals:
- Driver - Determine technical feasibility for allowing an [issue to be assigned to multiple groups](https://gitlab.com/gitlab-org/gitlab/-/issues/296668), which would likely solve [Plan adoption blockers (priorities 1 and 3)](https://gitlab.com/gitlab-org/gitlab/-/issues/218333).
- Start work on the [13.9 release plan](https://gitlab.com/gitlab-org/plan/-/issues/236).
- Continue making progress on the [13.9 release plan](https://gitlab.com/gitlab-org/plan/-/issues/236).
- Open > 3 documentation MRs in support of [better articulating Plan use cases](https://gitlab.com/gitlab-org/gitlab/-/issues/213810).
- Complete the validation track for [saved filters/searches](https://gitlab.com/gitlab-org/gitlab/-/issues/14512), [customizable issue types](https://gitlab.com/gitlab-org/gitlab/-/issues/118666), and [interacting with a full issue from within a Board](https://gitlab.com/gitlab-org/gitlab/-/issues/13319)
- Merged architectural blueprint for [consolidating Groups and Projects](https://gitlab.com/gitlab-org/architecture/tasks/-/issues/7).
health:
level: 3
reasons:
- Achieved - FY21 Q4 targets of 437,490 for All, 101,835 for Paid. New targets set for FY22 Q1.
- Driver - For Paid, continue high level progress on [achieving feature parity between an Instance, Group, and Project](https://gitlab.com/groups/gitlab-org/-/epics/2885), [making issues more extensible](https://gitlab.com/groups/gitlab-org/-/epics/3354), and continuing to make incremental progress on [iterations](https://gitlab.com/groups/gitlab-org/-/epics/2422).
- Improvement - For All, work towards addressing the [problem areas](https://gitlab.com/groups/gitlab-org/-/epics/4104) that emerged out of the Category Maturity Scorecard exercise for Issue Tracking.
- Improvement - For All, continue making progress on [quality of life improvements](https://gitlab.com/groups/gitlab-org/-/epics/3216) for existing features.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment