@@ -19,7 +19,7 @@ An efficient Quote-to-Cash system makes purchasing, activating, and managing Git
## Teams
Quote-to-Cash system projects and initiatives often require close collaboration across functions and teams. The teams most often involved include: [Enterprise Applications](/handbook/business-technology/enterprise-applications/), [Billing Ops](/handbook/finance/accounting/finance-ops/billing-ops/), [Fulfillment](https://about.gitlab.com/direction/fulfillment/), [Field Operations](/handbook/sales/field-operations/), [Support](/handbook/support/), and [Data](/handbook/enterprise-data/).
Quote-to-Cash system projects and initiatives often require close collaboration across functions and teams. The teams most often involved include: [Enterprise Applications](/handbook/business-technology/enterprise-applications/), [Billing Ops](/handbook/finance/accounting/finance-ops/billing-ops/), [Fulfillment](/handbook/engineering/development/fulfillment/), [Field Operations](/handbook/sales/field-operations/), [Support](/handbook/support/), and [Data](/handbook/enterprise-data/).
In addition to the [Fulfillment Product Direction](https://about.gitlab.com/direction/fulfillment/), the Fulfillment Development Sub-department strives to:
In addition to the [Fulfillment Product Direction](/handbook/product/groups/fulfillment/direction/fulfillment_section/), the Fulfillment Development Sub-department strives to:
- Increase the reliability and availability of our Fulfillment infrastructure
- Make foundational technical improvements to the architecture and data models of the Fulfillment systems
@@ -95,7 +95,7 @@ On or around the `26th`: Product meets with Engineering Managers for a prelimina
### Intake Request
To request work to be added to the [Fulfillment Roadmap](https://about.gitlab.com/direction/fulfillment/#roadmap), please open an issue by following [this link](https://gitlab.com/gitlab-org/fulfillment-meta/-/issues/new?issue&issuable_template=intake) and tag one of the Fulfillment Product Managers.
To request work to be added to the Fulfillment Roadmap, please open an issue by following [this link](https://gitlab.com/gitlab-org/fulfillment-meta/-/issues/new?issue&issuable_template=intake) and tag one of the Fulfillment Product Managers.
A Fulfillment Product Manager will be assigned to review the request and start evaluating the scope and impact. This may take some time depending on team capacity. Once evaluated, the PM will:
@@ -734,15 +734,15 @@ This table lists recurring activities that are part of our Project Management Pr
@@ -7,7 +7,7 @@ description: "The Fulfillment Sub-department is responsible for the infrastructu
| Resource | Areas Covered |
| -------- | ------------- |
| [Fulfillment Direction](https://about.gitlab.com/direction/fulfillment/) | Fulfillment vision and what we are working on next. |
| [Fulfillment Direction](/handbook/product/groups/fulfillment/direction/fulfillment_section/) | Fulfillment vision and what we are working on next. |
| [docs.gitlab.com Subscription](https://docs.gitlab.com/subscriptions/) | Customer-facing documentation around GitLab subscriptions, including Customer Portal (customers.gitlab.com) information. |
| Fulfillment Guide (this page) | Documentation around CustomersDot Admin tools and process documentation that is not part of the docs.gitlab.com Subscription documentation above. |
| [Fulfillment Development Sub-Department](/handbook/engineering/development/fulfillment/) | Team members, stable counterparts (PM, UX, Quality, Security, EntApps, Field Ops, Sales, Billing, Customer Success, Support Engineering), project management processes, and more. |
@@ -191,7 +191,7 @@ Additional attributes can be applied:
## Subscription Management Features
List of features managed by the [subscription management group](https://about.gitlab.com/direction/fulfillment/subscription-management/) within the [Fulfillment section](https://about.gitlab.com/direction/fulfillment/).
List of features managed by the [subscription management group](/handbook/product/groups/fulfillment/direction/subscription_management/) within the [Fulfillment section](/handbook/product/groups/fulfillment/direction/fulfillment_section/).
### Subscription Renewal and Auto-Renewal
@@ -952,7 +952,7 @@ To request work to be added to the Fulfillment roadmap, please follow our [intak
The source of truth for our priorities for a given quarter are our Fulfillment OKRs.
By nature of our [direction](https://about.gitlab.com/direction/fulfillment/), Fulfillment works mostly on highly cross-functional projects where either or both of the following are true:
By nature of our [direction](/handbook/product/groups/fulfillment/direction/fulfillment_section/), Fulfillment works mostly on highly cross-functional projects where either or both of the following are true:
1. Many cross-team dependencies: project execution relies on collaboration with other teams, with significant coordination of time and resources required.
1. Downstream impacts: projects may change how other teams operate (e.g., Field Operations, Enterprise Apps, Billing) and may also impact the success of their efforts (e.g., achieving sales efficiency targets, accomplishing e-commerce conversion goals)
@@ -7,7 +7,7 @@ description: "The Fulfillment Sub-department is responsible for the infrastructu
| Resource | Areas Covered |
| -------- | ------------- |
| [Fulfillment Direction](https://about.gitlab.com/direction/fulfillment/) | Fulfillment vision and what we are working on next. |
| [Fulfillment Direction](/handbook/product/groups/fulfillment/direction/fulfillment_section/) | Fulfillment vision and what we are working on next. |
| [docs.gitlab.com Subscription](https://docs.gitlab.com/subscriptions/) | Customer-facing documentation around GitLab subscriptions, including Customer Portal (customers.gitlab.com) information. |
| Fulfillment Guide (this page) | Documentation around CustomersDot Admin tools and process documentation that is not part of the docs.gitlab.com Subscription documentation above. |
| [Fulfillment Development Sub-Department](/handbook/engineering/development/fulfillment/) | Team members, stable counterparts (PM, UX, Quality, Security, EntApps, Field Ops, Sales, Billing, Customer Success, Support Engineering), project management processes, and more. |
@@ -191,7 +191,7 @@ Additional attributes can be applied:
## Subscription Management Features
List of features managed by the [subscription management group](https://about.gitlab.com/direction/fulfillment/subscription-management/) within the [Fulfillment section](https://about.gitlab.com/direction/fulfillment/).
List of features managed by the [subscription management group](/handbook/product/groups/fulfillment/direction/subscription_management/) within the [Fulfillment section](/handbook/product/groups/fulfillment/direction/fulfillment_section/).
### Subscription Renewal and Auto-Renewal
@@ -952,7 +952,7 @@ To request work to be added to the Fulfillment roadmap, please follow our [intak
The source of truth for our priorities for a given quarter are our Fulfillment OKRs.
By nature of our [direction](https://about.gitlab.com/direction/fulfillment/), Fulfillment works mostly on highly cross-functional projects where either or both of the following are true:
By nature of our [direction](/handbook/product/groups/fulfillment/direction/fulfillment_section/), Fulfillment works mostly on highly cross-functional projects where either or both of the following are true:
1. Many cross-team dependencies: project execution relies on collaboration with other teams, with significant coordination of time and resources required.
1. Downstream impacts: projects may change how other teams operate (e.g., Field Operations, Enterprise Apps, Billing) and may also impact the success of their efforts (e.g., achieving sales efficiency targets, accomplishing e-commerce conversion goals)
