Growth:Activation and Adoption group priorities for 14.9
The following is the Growth:Activation and Adoption group priorities for %14.9
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
or@gitlab-org/growth/adoption
in the description or directly assigning in a comment/assign @gitlab-org/growth/activation
or/assign @gitlab-org/growth/adoption
- 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
Activation
- 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.
Adoption
- 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 Activation engineers
groupactivation FCL takes precedence gitlab-org&7581 (closed)
- [Engineering] Add targeting by permission set t... (#461 - closed)
- [Engineering] Add "setup a self-hosted runner" ... (gitlab-org/gitlab#355127 - closed) (from [UX] Add "setup a self-hosted runner" to the pi... (#465 - closed))
- Update pipeline zero state to suggest IOS speci... (#509 - closed)
- Add integrate GitLab with Test Flight to email ... (#512)
- Programmatically collect is_creating_android_app (#574)
- [Engineering] SPIKE - Add targeting by event se... (#462 - closed)
Growth-Deliverable priorities for Adoption engineers
- gitlab-com-top-initiatives/free-saas-user-efficiency/free-saas#47+
- gitlab-com-top-initiatives/free-saas-user-efficiency/free-saas#26+ - may be able to get assistance from Conversion/Expansion teams
- Push SAST experiment
unchecked
variant to 100%, clean up experiment: [Experiment Rollout] new_project_sast_enabled -... (gitlab-org/gitlab#340929 - closed) - https://gitlab.com/gitlab-org/gitlab/-/issues/353605+
- gitlab-org/gitlab#339256+
- Experiment: Engineering - MVC add videos to con... (gitlab-org/gitlab#351915 - closed)
- Follow up work required to launch the MR widget experiment - Shift MR widget experiment to project level, ad... (gitlab-org/gitlab#348598 - closed)
Notes: (PM)
All other engineering issues
- bypass_registration Successful Cleanup (gitlab-org/gitlab#350278 - closed)
- gitlab-org/gitlab#325525+
- [Engineering] Signing-up for GitLab: Add the op... (ui-ux#90 - closed)
- [Engineering] Signing-up for GitLab: Add passwo... (ui-ux#91)
- ...
- ...
- ...
- ...
Notes: (PM)
UX issues
- Experiment: UX - MVC add videos to continuous o... (gitlab-org/gitlab#351914 - closed) - Kevin
- [UX] Create Illustration for Registration and Trial Flows
- https://gitlab.com/gitlab-org/ux-research/-/issues/1694+ - Kevin
- Send "Contact Sales?" email when 4 users have accepted invitation to a namespace - Emily
- Send "Contact Sales?" email when hosed runner setup is successfully completed - Emily
- Add walkthrough/wizard for the standard CI template - Emily
- Android tests - Emily
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...
- ...
- ...
- ...
- ...
Boards
- Analytics: Activation Adoption
- Validation: Activation Adoption
- Build: Activation Adoption
- Milestone Activation Adoption
- Growth-Deliverable Activation Adoption
Checklist
Activation
-
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
Adoption
-
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