Growth:Activation planning for 13.8
The following is the Group:Activation group priorities for %13.8
Process and timeline
Click to expand!
Process
- https://about.gitlab.com/handbook/product-development-flow/
- https://about.gitlab.com/handbook/engineering/workflow/#product-development-timeline
- https://about.gitlab.com/handbook/engineering/development/growth/
- https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/growth/#how-we-work
- Please add/update/change any information directly in the description. Add a comment if you think the change needs an explanation.
- We link to but won't discuss details of security issues here, as this issue is public
- Previous Growth:Adoption planning issues
Timeline
- 4th - issue created, all group members can contribute ideas/issues (PM/EM/IC)
- Add proposed milestone to issues (PM)
- Label issues as ~"Growth-Deliverable" (PM)
- Update the Goals section (PM)
- Apply weight to issues for this milestone (Engineering)
- Apply the Deliverable label to issues we expect to close this milestone (Engineering)
- 15th - milestone planning finished - EM to summarize in planning summary for review in retrospective
Boards
- Validation: https://gitlab.com/groups/gitlab-org/-/boards/1506660?scope=all&utf8=%E2%9C%93&label_name[]=devops%3A%3Agrowth&label_name[]=group::activation
- Build: https://gitlab.com/groups/gitlab-org/-/boards/1506701?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=devops%3A%3Agrowth&label_name[]=group::activation
- Milestone https://gitlab.com/groups/gitlab-org/-/boards/1370834?scope=all&utf8=%E2%9C%93&label_name[]=devops%3A%3Agrowth&label_name[]=group::activation
Goals for 13.8:
Goal / Epic | Detail | UX | Eng |
---|---|---|---|
In Product Emails | Allow communication to all users of a namespace / instance to help them get started with GitLab |
Stretch goals:
Goal / Epic | Detail | UX | Eng |
---|---|---|---|
Future planning (issues for review)
Engineering and UX notes
- Any follow up or missed deliverable issues from the previous milestone...
- Technical debt, security issues, or bugs based on severity/priority/due date...
- Any non-product led initiatives related to career development or Engineering KRs...
- ...
Planning summary (for retrospective)
&62 is still in planning breakdown, with an aim to deliver an MVC for SaaS in %13.8.
Edited by Phil Calder