Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Scoping Professional Services

Selling Professional Services

Getting Started

Services engagements can take three forms. These include SKUs, standard SOWs, and custom SOWs. For custom SOWs, the workflow for SOW creation involves a partnership between the SA/TAM and the Professional Services Engineering team.

This page is designed to collect details around the types of questions that are valuable in discovering the customer's required capabilities. That will help the team align the SOW with the positive business outcomes the customer is looking for with a services engagement. While not an exhaustive list, these questions, and suggestions will help spark the discovery conversations.

Migrations

Migrations are one of the most complex types of services in any technical field. Systems store data in a variety of ways that evolves. Also, customers and users often use the same data model and system to represent completely different logical units to their teams. To ensure a transition that meets the customer's needs, we want to make sure we understand their usage of their current systems.

GitLab to GitLab Scoping Questions

The following questions are about bringing multiple GitLab instances together into a single "parent" instance:

SVN to Git Scoping Questions

SVN to Git Questions

  1. What is the structure of the SVN repos and subprojects? Do they follow the "standard" of:
         Repository
             Project 1
                 branches/trunks/tags
             Project 2
                 branches/trunks/tags
    
    1. Any other variations? Example:
           Trunk
               Project 1
               Project 2
           Tags
               tag name
                   Project 1
                   Project 2
           Branches
               Branch name
                   Project 1
                   Project 2
      
  2. How many SVN repositories are there? How are they broken up?
  3. What is the overall size of the SVN repos?
  4. How much history (e.g. tags, branches, etc.) should be migrated?
  5. Are any binary files stored in SVN?
  6. How are you currently using SVN externals? Do you have some example use cases?

GitLab self-managed to GitLab.com Scoping Questions

Note: We have currently suspended the offering for Professional Services to help customers migrate from self-managed to GitLab.com. The Product team is looking to better support these transitions in an upcoming release. Once that import/export capability is released, we will reconsider our ability to provide this service.

Self-Manged to GitLab.com Questions

  1. How many repositories are there?
  2. What is the average size of the repositories? What is the size of the largest repositories?
  3. How many groups are there?
  4. How many users?
  5. Do we want the same structure of groups/projects/user access? Do we want it to be restructured?
  6. Do you use other tools with GitLab. If so, which ones?
  7. How are the runners currently set up?
  8. Where are they hosted?
  9. How many specific runners do you have and what are the details of these runners?
  10. Are you looking to make any changes to the runner strategy at your organization or will it stay the same?
  11. GitLab.com uses SAML for authorization. What SAML tool would your organization be using?

Implementations

For scoping infrastructure implementation, we have several questions that can help us understand the scope. To get started, make a copy of the spreadsheet below and fill in the answers. If there are questions you want to add, ping the @ps-team in slack in #g_professionalservice. Then you can attach this document to the issue created by the SOW calculator.

Implementation Infrastructure Scoping Questions

Note: This document contains tabs for various public and private cloud providers - AWS, GCP, Azure, OpenShift and other on-prem deployments - you should only have to fill out the tab(s) relative to your customer.