12.8 Planning for Analytics
| Group | Build Track |
|---|---|
| Analytics | Board |
Please filter the board above for department-specific issues (UX, backend, frontend).
Proposed objectives
12.8 should get the full Analytics group focused back on analytics work. We've established a path forward on our analytics strategy and have a couple of great analytics features planned.
Overall, our strategy is to continue to iterate on project-level analytics in Starter/Core. Once we're confident that we have something useful, we can create more advanced versions of these analytics tools at the group/instance level for larger organizations. This means:
- Continuing to iterate and refine Code Review Analytics MVC
- Shipping an MVC of DevOps Score (instance-level activity that tells a story of value to help leaders and execs understand GitLab's value)
- Shipping an MVC for Project Health (show me areas of risk and things I need to action on, as a individual responsible for the health of a project)
- Refining project-level and group-level Analytics features
Capacity
- Backend
- Aakriti OOO 2020-02-03, 2020-02-12
- Frontend
UX
- DevOps Score (e.g. instance activity): gitlab-org/gitlab#195885 (closed)
- Unblocks gitlab-org/gitlab#193435 (closed)
- Project Health: gitlab-org/gitlab#196177 (closed)
- Unblocks gitlab-org/gitlab#196181 (closed)
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 Kickoff items with Highlightlabel. -
Create Kickoff video. And we're dooooone. 💃
Edited by Dan Jensen