Product Intelligence 15.0 Milestone Planning
15.0 Reference Information
- 15.0 Milestone period: 2022-04-18 - 2022-05-17
- Breakdown Phase 2022-04-18 - 2022-04-24: break down work, weigh issues, FE/BE collaboration
- 14.10 Retro https://gitlab.com/gl-retrospectives/product-intelligence/-/issues/26
- 14.9 Retro https://gitlab.com/gl-retrospectives/product-intelligence/-/issues/25
- Holiday time: Please add the amount of time off taken for the release period in the Capacity Planning Spreadsheet
Issue Boards
Some notes about the board by milestone...
- The issue board by milestone contains the current milestone as well as a list for the next two milestones. Not only will this help me plan easier, but it will give the dev team visibility into the next priorities.
- Issues within each milestone list are prioritized with the highest priority issues ranked from top to bottom, please pick issues in order wherever possible.
- If there is nothing left to pick in the current milestone, there is a list of options to follow in picking something to work on
- We aim to plan ambitiously. This means it is ok if we don't get through all planned issues in a single milestone. However, issues marked with Deliverable are issues we are committing to deliver in the current milestone. These are the highest priority.
- For folks onboarding to our team - please pick issues from the ~"product intelligence::onboarding issue" list on the issue board. The issues are listed in order so where possible pick from the top of the list, but feel free to skip an issue if it is something outside of your current learning scope.
15.0 Summary
Welcome to major release 15.0!
Current milestone focus
In milestone %15.0 the majority of our work is concentrated into three main themes: (1) Monitoring & Reliability, (2) Creating guardrails to make it hard for developers to fail; through the use of standard protocols, validation checks, helper tools and clear guidelines, dev's shouldn't be surprised test failures and review feedback, and (3) spike investigations to create well-researched technical plans for future work.
- Reliability
- Create guardrails
- Implement suggestions for MRs with metrics defi... (gitlab-org/gitlab#342249 - closed)
- Allow only implemented operation for DatabaseMe... (gitlab-org/gitlab#332553 - closed)
- Enable automated ways to configure/test/observe... (gitlab-org/gitlab#353495 - closed)
- Prevent incorrect usage of `tracking_attrs` helper (gitlab-org/gitlab#348968 - closed)
- Always return boolean for Snowplow events FE di... (gitlab-org/gitlab#358901 - closed)
- Technical Spikes
- Spike: Recover lost license information for Ser... (gitlab-org/gitlab#358708 - closed)
- Spike: Top non performing queries in VersionApp (gitlab-org/gitlab#356405 - closed)
- https://gitlab.com/gitlab-org/gitlab/-/issues/355451+
- Enable automated ways to configure/test/observe... (gitlab-org/gitlab#353495 - closed)
- Spike: Draft technical plan to migrate Snowplow... (gitlab-org/gitlab#351979 - closed)
- SPIKE: Add test for Service Ping generated quer... (gitlab-org/gitlab#347545 - closed)
But also documentation!
A very strong theme that I heard from our internal customers during interviews, is that our documentation is extensive but not effective. I'd like to ship the first iteration of a "Getting Started with Product Intelligence" guide this milestone. Please note that this issue is a Deliverable for %15.0.
Where are we headed?
- GitLab Direction: If you haven't done so in awhile, check out GitLab's short, mid and long-term direction here.
-
Product Intelligence Direction: You can find the Product Intelligence specific direction here.
- FY2023 focus: As a reminder, our focus for FY2023 is narrowed to the following 4 key categories with the north star goal of closing this fiscal year with a stable, scalable and reliable infrastructure of metrics instrumentation tooling, collection transformation and delivery. You can see more about where we are headed in our FY23 Roadmap for Product Intelligence.
Focus | Why? |
---|---|
Reliability | GitLab team members need a broad set of metrics and events to iterate, build new features, and capture emerging use cases without the need to manually instrument tracking. |
Scalability | GitLab team members need trustworthy data to build analysis upon. Whenever data is lost it causes disruption and reduces trust. |
Create product usage data parity between self-managed and SaaS | GitLab team members need the ability to measure product usage using a common method for customers on both self-managed and SaaS platforms |
Improve adoption | Comprehensive product usage data will allow us to make better product decisions. |
Milestone breakdown
Type | # of Issues | Total Weight | % of Total Weight | Target % |
---|---|---|---|---|
Deliverable | 3 | 7 | 7% | 30% |
System Reliability and Monitoring | 6 | 11 | 11% | 25% |
Maintenance | 11 | 20 | 21% | 10% |
Bugs | 8 | 23 | 24% | 10% |
Documentation | 4 | 9 | 9% | n/a |
Technical Spike | 4 | 11 | 11% | n/a |
Weight by Workflow Label at beginning of milestone
🚨 Issues scheduled for 15.0 which need weight
See handbook guide for how to async estimate issues
Planning Breakdown | Ready for Dev | In Dev | Ready for Review | In Review | Staging | Verification | Blocked | Closed | Total |
---|---|---|---|---|---|---|---|---|---|
0+ | 38 | 19 | 0 | 11 | 0 | 0 | 3 | 0 | 77+ |
- + denotes unweighted issues in milestone
Milestone Weight History
BACKEND | 14.4 | 14.5 | 14.6 | 14.7 | 14.8 | 14.9 | 14.10 |
Total assigned | 55 | 74 | 95 | 84 | 66 | 84 | 69 |
Deliverable | 18 | 9 | 5 | 9 | 14 | 12 | 10 |
Unplanned | 24 | 11 | 5 | 3 | 11 | 0 | 16 |
Pushed to next milestone | 20 | 26 | 36 | 42 | 20 | 22 | 31 |
Closed | 59 | 59 | 64 | 45 | 57 | 52 | 38 |
FRONTEND | 14.4 | 14.5 | 14.6 | 14.7 | 14.8 | 14.9 | 14.10 |
Total assigned | 9 | 18 | 11 | 10 | 13 | 10 | 17 |
Deliverable | 6 | 11 | 4 | 1 | 3 | 5 | 3 |
Unplanned | 10 | 0 | 0 | 4 | 9 | 10 | 1 |
Pushed to next milestone | 2 | 8 | 4 | 4 | 2 | 3 | 0 |
Closed | 17 | 10 | 7 | 10 | 20 | 17 | 17 |
*denotes pending issues from prior milestone which may push or close
⚠ Team member action required
@gitlab-org/growth/product-intelligence Hey team!
- Comment in the threads below regarding things you find helpful, things we should add and things you think we can remove from the planning issue. I want this issue to be a useful reference tool for you. I'm finding it a bit cluttered but am not sure which information you find useful and which you don't, so please share your opinion!
- Once you've added any comments you have (if you have any) and you've read this entire planning issue, please unassign yourself from the issue.
- Async issue estimation. Using the process outlined in the async estimation guide, please crowd source estimation of these issues.