12.9 Planning for Analytics
| Group | Build Track |
|---|---|
| Analytics | Board |
Please filter the board above for department-specific issues (UX, backend, frontend).
Capacity
- 3 BE
- Adam out 2020-03-05 - 2020-03-06 (2 days)
- Aakriti reduced capacity due to Ruby performance training
- 3 FE
Proposed objectives
With Value Stream Management taking center stage in our analytics strategy, we should turn some development attention to this important feature. My opinion is that VSM is the framework on which all other analytics features in GitLab should sit, and it's worth dedicating time to making sure this feature is functional, beautiful, and valuable to our users. To further this objective, I'm proposing the following issues in this release:
- Add Lead Time and Cycle Time to Value Stream Analytics Kickoff Highlight
- Cycle analytics custom ordering of stages
- Improve approach for linking merge requests to issues for cycle analytics calculations
- Technical improvements/bugs
We'd also like to finish off a couple of nifty new feature additions:
Additionally, with the release of Code Review Analytics in 12.7, we should continue improving on this cool feature:
- Start code review on assigning an MR Kickoff Highlight
- Start code review on approval Kickoff Highlight
- Empty state
We've also introduced Planning Analytics as a category, and have a couple of small desired improvements to get this category off to a strong start:
UX
TODO
-
Tentatively define goals, sharing asynchronously with the team. -
Review on a planning meeting with Dennis and Dan. Rest of Analytics more than welcome (invited as optional). -
Review UX goals with Nick. -
Complete estimation. -
Confirm final release scope and Kickoff items. 💥 -
Mark in-scope items with Deliverable. -
Mark Kickoff items with directionlabel. -
Create Kickoff video. And we're dooooone. 💃