Property | Value |
---|---|
Date Created | 2022-06-29 |
End Date | Launch date of General Availability |
Slack | #f_gitlab_dedicated for GitLab Dedicated questions (only accessible from within the company) |
Slack | #wg_dedicated_cross_functional for working group items (only accessible from within the company) |
Google Doc | Working Group Agenda (only accessible from within the company) |
Epic | Cross-Functional Epic (only accessible from within the company) |
See Limited Availability Roadmap including milestones for cross-functional work.
The exit criteria for GitLab Dedicated Top Cross-Functional Initiative are the same as the exit criteria from Limited Availaility
The GitLab Dedicated Initiative Working Group follows the same processes as the GitLab Dedicated Engineering team from the Dedicated Engineering team page. This includes:
See epic management and hierarchy on Dedicated Team Page.
The Cross-Functional LA Requirements epic is a child epic of the GitLab Dedicated Top Level epic. This cross-functional epic is comprised of function-specific child epics managed by the DRI for that functional area. These functional child epics have sub-epics and/or issues representing groups of related tasks that are delivered in a specific phase from Limited Availability Roadmap.
Milestones for functional work from the Cross-Functional LA Requirements epic are included in Limited Availability Roadmap.
The GitLab Dedicated Initiative Working Group follows the status update process from Dedicated Engineering team page. The status updates that Functional DRIs make in their respective Functional Epics will incorporated in the status update cadence and used to update the status of the Cross-Functional epic and the Top-Level Initiative Epic.
In addition to the status process from Dedicated team page, the Dedicated initiative has additional status update requirements as a Top Cross-Functional initiative that the Initiative DRI is responsible for:
Below are the functional areas involved in this Cross-Functional Initiative as well as the Functional DRI representing that functional area.
Working Group Functions (alphabetical) | Team Member | Title |
---|---|---|
Functional Lead: Channel Partners | Honora Duncan | Senior Channel Services Manager |
Functional Lead: Comms & PMM | Saumya Upadhyaya | Principal Product Marketing Manager |
Functional Lead: Enablement | Kelley Shirazi | Manager, Sales Enablement |
Functional Lead: Engineering | Marin Jankovski | Director, Infrastructure Platforms |
Functional Lead: FP&A | Shuang Shackleford | Director, FP&A |
Functional Lead: Post-Sales (CS/PS) | Brian Will | Senior Manager, Professional Services |
Functional Lead: Pricing & Fulfillment | Justin Farris | Senior Director, Product Monetization |
Functional Lead: Product | Andrew Thomas | Principal Product Manager |
Functional Lead: Sales | Aileen Lu | Director, Sales Strategy |
Member | Josh Lambert | Director of Product, Enablement |
Member | Jake Bielecki | VP, Sales Strategy & Analytics |
Functional DRIs are also mentioned at the top of the description of their function's child epics in the Cross-Functional LA Requirements epic per epic structure.
Please see Functional Lead on Working Group page.
Functional DRIs are responsible for maintaining their function's epics by following process mentioned in Epic Owner Responsibilities and Epic Structure.
Below are the specific areas of responsibility within the Dedicated team:
Area | Tasks | DRI |
---|---|---|
E-Group reporting | Write status updates, Key review updates | @rwedmore |
Program management | Cross-functional workstream coordination, create launch list, ad hoc coordination requests | @rwedmore |
Customer Success (CS) | Define onboarding PS package, outline CS engagement post-sales | @rwedmore |
Environment Automation Roadmap | Updating direction page, prioritization changes etc. | @awthomas consulting and collaborating with @o-lluch |
Switchboard Roadmap | Updating direction page, prioritization changes etc. | @fzimmer consulting and collaborating with @marin |
PRE deal Customer interactions | Meeting with customer prospects, customer qualification, steps 1-6 in onboarding process Supporting customers until CS packages are defined | @awthomas |
POST deal onboarding management | steps 7-9 in in onboarding process; until CS package defined | @rwedmore or @fzimmer |
Automate manual onboarding tasks | Includes driving documentation changes. | @awthomas |
Drive cross-product feature requests needed for Dedicated | examples include Maintenance mode prometheus metric, silent mode | @awthomas |
Go to market definition | PMM and PM to define the remaining GTM items, rest in cross-functional workstream coordination, | @awthomas |
Coordinate with Finance | Fy24 Rev Projection, Cost Optimizations; P&L and min seat count later | @fzimmer consulting with @marin |
This table will be reviewed at the end of each month.