The goal of the Customer Reference Program is to provide opportunities for customers to share their story on how GitLab has helped them overcome the challenges, blockers and pain points within their organizations.
The goals of the Gitlab Customer Reference Program include:
Some examples of the types of assets we'd use as customer references once we have approval from the customer:
To create a new issue around the Customer Reference Program, open an issue on the Customer Reference Program Board. Make sure it has the label Customer Reference Program. Feel free to add any applicable labels around the request. Assign to Reference Program Manager as needed.
The most recent customer case studies are found on the GitLab customer's page. When we build case studies, we need to have quantifiable metrics and business value to help describe how GitLab helped a customer achieve a signficant business result. Below are a sample of KPIs / dimensions we need to find in a good case study.
Better / Quality
If a proposed customer case study doesn't have at least one metric to include, then we consider working with the account team to help identify a solid metric before building the case study.
Interview Questions: (Select the questions we should ask)
What insights do you have that might make a good case study today?
What are your goals for this case study?
Describe what your organization does.
What was the team/workflow/culture like when you first stepped into your role vs. today?
How are you using GitLab?
How does your team helps solve business challenges?
What were your directives for your role?
Which teams are using GitLab?
What does it mean to modernize the software team’s architecture, workflow, cross-functional relationships?
What is some of the feedback you got from product managers who said they had too many tools?
How did GitLab solve those problems?
How has GitLab simplified workflow?
How has GitLab enabled cross-functional relationships?
How has it helped modernize architecture?
What and how are you automating?
What is the non-dev conversion on task management features?
What are some initial successes resulting from moving to GitLab?
Do you have any metrics available?
Number of builds per day now vs. past
Pushes to production
Time from planning to production
Number of automatic tests
Workflow physically going faster?
Catching bugs earlier?
Could you please talk a bit more about any AWS set up?
How are you using security testing features?
/data/case_studiesdirectory under Marketing site repo (www-gitlab-com project).
Today, we don't have a central collection for customer service, but we are starting to build one. For now we are capturing customer stories in an issue. If you have a customer story or anecdote leave a comment on issue 1834.
To initiate a formal case study process, follow the process listed here
* What led you to GitLab, what problems were you trying to solve? * Why did you choose GitLab and what other tools were you using or considering? * What has been your experience with GitLab? * How did you make the business case for GitLab and what metrics have you seen improve? * What have you heard from the GitLab users, what was the adoption curve like? * What has been the most unexpected success you have experienced? Adoption rates? Improved speed?
Purpose: To help foster DevOps transformation and adoption we are establishing a Customer Advisory Board, where we focus on sharing DevOps best practices and lessons learned with each other. We believe that transparency and sharing is a key way to help encourage the success of DevOps transformations. The GitLab customer advisory board is intended to be home to learning and collaboration so we can all experience success through DevOps transformation.
Members Executives/Champions for DevOps within their organizations
Frequency: We will try to meet virtually every 6 to 8 weeks
Membership: Approximately 15 - 20 customers, GitLab
Meeting Recordings Meetings are recorded for internal and member use. Members can seek these recordings by emailing CAB@gitlab.com
Recurring Content We will frequently ask for GitLab Product Managers to join to present the vision for their assigned DevOps stage. When doing so we will distribute a recorded video of their stage vision in advance.
Kickoff Meeting-September 5, 2018
GitLab Road Map review-September 26, 2018
GitLab Plan review-October 17, 2018
GitLab Create review-November 7, 2018
GitLab Release review-December 5, 2018
GitLab Manage review - January 9, 2019
GitLab Geo review-February 6, 2019
Purpose: We are forming Special Interest Groups to foster specific and focused discussions about how to apply DevOps practices and GitLab capabilities in specific domains such as planning, development, CI/CD, security, etc. These Special Interest Groups will encourage sharing and collaboration of DevOps best practices and lessons learned between users and GitLab.
We believe that transparency and sharing is a key way to help us all learn and improve how we deliver for our customers. GitLab special interest groups are intended to be home to learning and collaboration.
Members Technical utilizers and advocates of GitLab
Frequency: We will try to meet virtually every 6 to 8 weeks
Membership: Approximately 8-15 users, GitLab Product Manager
Customer anecdotes are short, "snackable" customer stories. These can be used on a call or in a meeting to share a point about GitLab by validating it with the customer story. An anecdote can be a summary of a formal, attributable case study or just an anonymous story from a conversation you had with a customer. It's important to keep customers anonymous unless we have explicit approval to use their name.
A communications company recently shared how they built their technology stack. "GitLab checks so many boxes for us that we don't need other tools." The company then explained they they are operating with a team of 2 people because GitLab makes the environment so simple. They said another organization would probably have to employ 15 people to accomplish what they can.
We hosted a dinner for customers and prospects to mingle with each other and share stories. When the topic of managing the DevOps toolchain came up, the Head of Risk at a large US bank mentioned that she had a team of 20 to keep SDLC tools running in her org. A GitLab customer, the managing director of a product group for a global investment management corporation said, "this is going to break your heart, but I have 1 guy that spends 25% time to keep GitLab up and going for my team of 1500 devs."
Pinterest is not a GitLab customer, but uses Kubernetes together with Jenkins. Because there's no native kubernetes integration for Jenkins they needed to dedicate a team of 4 spending 6 months to build a custom system to control access managment and allow teams to self-serve builds. This is functionality that comes out of the box on day one with GitLab.
A large enterprise in the software space is a recent GitLab Premium customer wanting to replace Perforce. They predicted that it would take them 3 years to hit 6K active users. But, the developer experience was so superior that they ended up hitting 6K active users in only 8 months.
A publishing firm is utilizing GitLab best of breed CI/CD functionality and with upcoming product advancements they have informed us that GitLab is a mission critical application for them. They also chose GitLab over the competition because security is currently the biggest aspect they want to improve on internally.
A financial services company recently stated that their teams went from two week releases to six times per day using GitLab. They are able to release this quickly because they do not need to wait for infrastructure.
An online gaming development house has a team of 9 looking after its toolstack for SDLC. GitLab is one of the tools in the stack, but is self-sufficient enough that they only deal with it every six months.
A large media company recently stated that GitLab is the best architected application they have ever used. According to this company, "This product is a joy to use. We cannot believe how much incremental value you crank out with each release."
Ticketmaster is a global event ticketing leader with one of the world's top five e-commerce sites, getting almost 27 million monthly unique visitors. Ticketmaster was using Jenkins for continuous integration. Weighed down by plug-ins and legacy development, their pipeline was taking 2 hours to complete. After getting stuck late on a friday night waiting for the build to complete, their ops team began exploring other options. They were able to run their pipeline on GitLab CI/CD in 8 minutes for a 15x increase.
Axway, is a global enterprise software company with over €300 million in yearly revenue. Axway wanted to adopt DevOps practices but their legacy Subversion toolchain was blocking them. By moving from Subversion to Git using GitLab as their Source Code Management (SCM) solution they were able to implement DevOps integrating GitLab into tools like JIRA, for issue management and Jenkins for continuous integration. They increased demployents from once-a-year to every two weeks.
Paessler AG provides the award-winning PRTG Network Monitoring software used by over 150,000 IT administrators in more than 170 countries. QA engineers were manually testing software with a routine set of tasking taking an hour to complete. By implementing GitLab pipelines they were able to automate QA tasks requiring only 3 minutes of effort for a 120x efficiency increase.
Equinix is a leading global data center company. Their client-side development teams are responsible for building software products and business critical applications, increase development speed, self-serviceability, and ship fixes and features quickly. Equinix needed a version control and continuous integration tool for distributed workflows to support globally distributed development teams.