Project Execution


Project Kick-off

The kick-off may be handled as part of the Welcome to GitLab call orchestrated by the GitLab Customer Success Manager. However, many times the implementation kick off will be an on-site engagement or one handled directly by the Professional Services Engineer. This template is for use in those cases.

Sign-off

After the SOW, or a specific Milestone has been successfully delivered and completed, the customer will need to sign a Project sign off document. This should be sent by the Project Manager. To send a Project Sign off document:

  1. Create a Project sign-off document for the Project or Milestone, based upon the Project Sign off template
  2. Create an email using the message below and attach the new Project sign off document
  3. Add the recipient who will be signing the document to the email and CC yourself and the PS Operations Manager
  4. Update subject line to “[customer name]- project sign off
  5. Send the email
Dear [Signer],

Attached you will find the project sign off documentation for your GitLab Professional Services Statement of Work.

Please sign the document and return at your earliest convenience.  Alternatively, you may reply all with the word "accepted" and that will be accepted as sufficient approval as well.

If you have any questions, please feel free to reach out to let me know.

Thank you,
[your signature]

Once you receive the Project Sign off, via signed document or email acceptance, or passive acceptance, you’ll need to follow these steps to process in Mavenlink

Standing Calls

Customer Facing

  • At least once a week
  • Include all stakeholders
  • Manager, PS and SAE should be “optional”

Internal

  • 15 minute standup
  • CSM, SAE, IE(s), Manager, PS
Welcome E-mail

This welcome e-mail will be sent by the Manager, Professional Services to introduce the customer to our Professional Services Engineering team and the concept of a GitLab implementation.

E-mail Template

Dear [Main Contact],

Let me add my welcome to GitLab, and extend our sincere desire to ensure that your GitLab implementation process is smooth and efficient, resulting in a system that will benefit your workflow, your software delivery process and thus your business.  We look forward to working with [Customer Name] to make this project a success!

The most important next step in our process together is to identify key personnel on each side that will be dedicated to this project.  Over the coming days, I will be working to identify a member of our dedicated Professional Services Engineering team to be the project lead for GitLab for your implementation.  The GitLab Professional Services Engineer will work closely with the members of your team that will be working on this project.

The team members from [Customer Name] that will need to be identified to kick off the project include:
* GitLab Champion - this individual will be the champion for GitLab at your organization
* A GitLab Administrator(s) – this user or users will be the key lead for implementation decision making, system build, system management and aiding in coordinating resources from [Customer Name].
* Technical POC - this user or users will help the GitLab Professional Services Engineering team gain the necessary technical resources and access to aid your team in the GitLab implementation.
* Additional Stakeholders - please also identify any other stakeholders such as business and product stakeholders.

My team and I look forward to working with the team at [Customer Name], and we'll be in touch soon!

XXX XXX
Manager, Professional Services
GitLab
Last modified November 7, 2023: Move customer-success files in to place (de58a497)