Growth:Activation group priorities for 14.6
The following is the Growth:Activation group priorities for %14.6
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 and Tasks
- 4th - issue created, all group members can contribute ideas/issues (Anyone)
- Add any in progress goals from the previous planning issue or workflow board (Anyone)
- Add proposed milestone to issues (PM)
- Label issues as ~"Growth-Deliverable" (PM)
- Update the Goals section (PM)
- Notify the group by mentioning
@gitlab-org/growth/activation
in the description or directly assigning in a comment/assign @gitlab-org/growth/activation
- Complete the review section (Engineers)
- Apply weight to issues for this milestone (Engineers)
- Apply a release scoping label, Deliverable or Stretch label to issues we expect or hope to close this milestone (Engineers)
- 15th - milestone planning finished - EM to review and move the issue to
~workflow::in dev
Tasks
- All: optionally unassign from this issue when planning completed
- Inform other groups that may be impacted by the planned work (PM)
Capacity
All: update the doc to indicate time off / capacity for the upcoming milestone
Growth sub-department milestone capacity
Review
- PM: Update the milestone for any missed deliverables
- Engineers: inform PM if deliverables from the previous milestone are unlikely to be delivered
- PM: Make any changes to pending or active experiments on the experiment board
- PM: Any cleanup/followup/removal issues required for long running, legacy, or completed experiments? dashboard
- Engineers: Review any issues in planning breakdown that do not already have a weight
- Designers: Review engineering issues to ensure designs are still current. Discuss with PM and engineers.
Growth-Deliverable priorities for engineers
- When pipeline fails due to cc verification failure, email the user with instructions
- When pipeline fails due to cc verification failure, Create a persistent header in the UI for that user
- Add "verify your identity" flow to first mile
- Create a marketing header when user is on GitLab and not logged in
Notes: (PM)
All other engineering issues
- [SPIKE] Determine how to programmatically collect is_creating_ios_app
- Add trial signup to GitLab marketing header
Notes: (PM)
UX issues
- Add confirm identity via phone number to validation in first mile
- Add "setup a self-hosted runner" to the pipeline zerostate page
- Update pipeline zero state to walk through custom runner set up (when is_creating_ios_app is true)
- Add integrate GitLab with Test Flight to email campaigns (when is_creating_ios_app is true)
- Add integrate GitLab with Test Flight to continuous onboarding (when is_creating_ios_app is true)
- Add feature flag action to email campaigns (for ios apps)
Notes: (PM)
Other UX or engineering work:
- 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...
- Any Engineering Research issues required for planning breakdown...
- Add targeting by permission set to Broadcast Messages
- SPIKE - Add targeting by event set to Broadcast Messages
Boards
- Analytics: https://gitlab.com/gitlab-org/gitlab/-/analytics/issues_analytics?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group::activation&label_name[]=Growth-Deliverable
- 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
- Growth-Deliverable https://gitlab.com/groups/gitlab-org/-/boards/3160544?scope=all&label_name[]=Growth-Deliverable&milestone_title=14.6&label_name[]=group::activation
Checklist
-
PM has added
Growth-Deliverable
and milestone to issues (enough to meet the target of 2 / engineer) - PM has informed other stages/groups of planned work in their areas
-
Engineers have added a
weight
to issue in the lists above using the estimation guidelines -
Engineers have added
Deliverable
orStretch
to issues likely to be delivered in this milestone - Engineers have informed PM if planned experiments may conflicts with deployed experiments
-
Designers have added a
weight
to issue in the lists above