Product Intelligence 15.1 Milestone Planning
15.1 Reference Information
- 15.1 Milestone period: 2022-05-18 - 2022-06-17
- Breakdown Phase 2022-05-18 - 2022-05-24: break down work, weigh issues, FE/BE collaboration
- 15.0 Retro https://gitlab.com/gl-retrospectives/product-intelligence/-/issues/27
- 14.10 Retro https://gitlab.com/gl-retrospectives/product-intelligence/-/issues/26
- 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.1 Summary
Welcome to milestone %15.1!
Current milestone focus
In milestone %15.1, we will place team focus on 7 deliverable issues. In the table below, I've provided context into why these are deliverable issues and the business value we hope to derived from the work.
Issue | Why | Business Value |
---|---|---|
Metrics dictionary - automatically designate "I... (gitlab-org/gitlab#351471 - closed) | Currently identifying when/where/why a metric was introduced is requires a bit of effort. This will make the process more efficient. | Reduce troubleshooting time when an issue or question arises related to a product usage metric. |
Add add operation (gitlab-org/gitlab#332713 - closed) | Add support to add numbers in instrumentation classes so we could instrument metrics like totals. | Reduce time to instrument totals metrics |
Recreate Redis Counters using Snowplow events -... (gitlab-org/gitlab#362274 - closed) Recreate Redis Counters using Snowplow events -... (gitlab-org/gitlab#362279 - closed) |
This is the 2nd phase of the project to replicate Redis counters in SaaS using Snowplow events. | As we deliver product usage data for SaaS namespaces as counters, the Customer Success and Product org will now be able to compare product usage data in an apples:apples fashion across self-managed and SaaS customers. |
Visualize the reasoning why a Service Ping failed (gitlab-org/gitlab#345391 - closed) | By viewing the errors visually, we may be able to understand the reason for the failure or have additional context than just seeing the errors in text. | This could reduce the time for resolution and troubleshooting of issues. |
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. |
Issue lists by type
Weight by Workflow Label at beginning of milestone
🚨 Issues scheduled for 15.1 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 |
---|---|---|---|---|---|---|---|---|---|
1+ | 42 | 19 | 0 | 9 | 0 | 5 | 0 | 5 | 81+ |
- + denotes unweighted issues in milestone
Milestone Weight History
BACKEND | 14.5 | 14.6 | 14.7 | 14.8 | 14.9 | 14.10 | 15.0 |
Total assigned | 74 | 95 | 84 | 66 | 84 | 69 | 84 |
Deliverable | 9 | 5 | 9 | 14 | 12 | 10 | 5 |
Unplanned | 11 | 5 | 3 | 11 | 0 | 16 | 0 |
Pushed to next milestone | 26 | 36 | 42 | 20 | 22 | 31 | 20 |
Closed | 59 | 64 | 45 | 57 | 52 | 38 | 64 |
FRONTEND | 14.5 | 14.6 | 14.7 | 14.8 | 14.9 | 14.10 | 15.0 |
Total assigned | 18 | 11 | 10 | 13 | 10 | 17 | 10 |
Deliverable | 11 | 4 | 1 | 3 | 5 | 3 | 2 |
Unplanned | 0 | 0 | 4 | 9 | 10 | 1 | 0 |
Pushed to next milestone | 8 | 4 | 4 | 2 | 3 | 0 | 3 |
Closed | 10 | 7 | 10 | 20 | 17 | 17 | 7 |
*denotes pending issues from prior milestone which may push or close
Work Type Classification
Per the Next Prioritization initiative, we will review our team's performance in applying appropriate type labels to MRs. At the close of the milestone, the EM or PM will post a link to this dashboard along with a summary of shipped work by type label (include null) to ensure we are observing the recommended work split of 60% feature, 30% maintenance, 10% bugs, and <=5% undefined.
Planned Work by Type
Type | Goal | Planned Issue % | Planned Weight % | Status | % MRs |
---|---|---|---|---|---|
Feature | 60% | 38% | 35% | tbd | |
Maintenance | 30% | 17% | 15% | tbd | |
Bugs | 10% | 20% | 18% | tbd | |
Undefined | ≤5% | 23% | 30% | tbd |
⚠ Team member action required
@gitlab-org/growth/product-intelligence Hey team!
- Async issue estimation. Using the process outlined in the async estimation guide, please crowd source estimation of these issues.
- Add your time off for this milestone to the Capacity Planning Spreadsheet
- Once you've completed the above and you've read this entire planning issue, please unassign yourself from the issue.