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

Use case: Version Control and Collaboration

Who to contact

Product Marketing Technical Marketing
Jordi Mon Companys William Galindez Arias

The Market Viewpoint

Version Control and Collaboration (VC&C)

As organizations accelerate delivery, through DevOps, controlling and managing different versions of the application assets from code to configuration and from design to deployment is incredibly important. Velocity without robust version control and traceability is like driving a car with out a seatbelt.

Version Control and Collaboration is more than simply tracking changes, versions, and branches of code. Effectively, it includes practices such as:

In general, Version Control and Collaboration is required because software is constantly changing. Regardless of the stage of development, there will be change to deal with.

No matter where we are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle.

E.H. Bersoff, 1980.

Companies that excel at version control and collaboration create high quality code while integrating it at high frequency.

Personas

User Persona

Being the entry point to GitLab means that many user personas find utility and a solution to their problem in Version Control and Collaboration. Let's go through the list of power user personas and describe briefly their key motivations to use Version Control and Collaboration in GitLab:

Parker the Product Manager

Delaney the Development Team Lead

Sasha the Software Developer

Devon the DevOps Engineer

Buyer Personas

Version Control and Collaboration purchasing typically do not require executive involvement. It is usually acquired and installed via our freemium offering without procurement or IT's approval. This process is commonly known as shadow IT and its a great opportunity for us to eventually become a paid for service. When the upgrade is required the VP of IT is the most frequent decision maker. The influence of the VP Application Development is notable too to the owner of the budget.

Industry Analyst Resources

Research relevant to this use case can be found in the Analyst Reports - Use Cases spreadsheet.

Market Requirements

Market Requirements is a collection of capabilites we recognize are present in the Version Control & Collaboration use case. People looking to solve this use case will consider fundamental that at least one, if not all of these requirements is present in the solution they implement. To gather these in a way that represents the market with acuracy we collect data from several sources like analysts, users, competitors and thought leaders.

Market Requirement Description Typical features that enable this capability Value / ROI
Protect and secure assets The solution provides mechanisms to host assets (repos), place and manage different change permissions for the users that access those repos as well as keep a detailed chain of custody of all changes these assets are subject of. Single sign-on, code ownership, change reviews, change approvals, IP Allowlist/Denylist, Activity stream, GPG signed commit, Reject unsigned commits, Protected branches, branching, committer access rules, Compliance dashboard etc. Secures IP and valuable assets. Provides information on project history changes
Enterprise Ready The solution is robust enough to make critical functionality available at large scale, widely distributed teams in highly regulated markets Geo, Geo High Availability, Disaster Recovery, Git protocol v2 support, Deduplicate Git objects for forked repositories, Download single repository files, fast and responsive application, project templates, file templates, access controls, and traceability. Prevents outages and disruptions of development team work. Enables traceability to authors of changes to address defects or bugs in the product and auditability throughout
Supports numerous assets The solution is able to manage and maintain the version history of the diverse assets and support the development patterns that each asset implies Component reuse, traceability, design management, branching, diffing, merging, object storage, design versioning Able to manage assets and files for the entire development team, no matter how diverse, creating a single source of truth for the product configuration and making visibility and communication available at every level
Foster Collaboration The solution is designed to enable and foster collaboration among team members. The collaboration system includes manual gates and approvals as well as automated workflows. Create fast new branches of the project, add new files/assets, collaborate on proposed changes, review comments, suggest changes, webIDE, suggestion approvals, conflict resolution, merge, diffing, hand-offs, Design management and operations, workflow automation, Wiki, snippets, version controlled snippets, Automatically update or close related issue(s) when a merge request is merged, Configurable issue closing pattern, display merge request status for builds in CI system, visibility into security scans and build stats. Code quality increase and improved release velocity through team review and validation.
Secure Development The solution allows for security practices to be enabled at the creation phases of the project Dependency scanning, SAST, License scanning, DAST, Container scanning Increasing resilience to external attacks, internal threats and ability to resume activity promptly
System and Architecture design The solution should support all the architectural decisions made and provide functionality to make concurrent work with the different modules easy. It should also connect the higher level of abstraction that a software architecture is to the lower level system components. The solution should play well with different levels of component decoupling, from large monorepos to service-oriented architectures (microservices being an example of it) Repo APIGit Submodules, Submodules API, PlantUML By providing a way to map and connect the structure of each component in codebase as a whole, SCM solutions make concurrent work easier, onboarding faster and help define goals in the shape of deliverable units.

The GitLab Solution

GitLab Stages and Categories

Manage Plan Create Verify Package Secure Release Non Dev-Ops Stage
Compliance Management Issue Tracking SCM Code Quality Jupyter Notebooks SAST Release evidence Geo-replication
Code Analytics   Code Review   Git LFS Secret Detection   Disaster Recovery
Insights   Wiki         Gitaly Clusters*
    Static Site Editor         Gitaly*
    Web IDE         Reference Architectures*
    Live Preview          
    Snippets          
    Design Management          
    Design Systems          
    Editor Extension          

How GitLab Meets the Market Requirements

A collection of short demonstrations that show GitLab's SCM capabilities.

Top 3 Differentiators

Differentiator Value Proof Point
Distributed version control It allows for asynch, remote, collaborative work to flourish since a single copy of the complete project's history can be stored in any machine, branching is easy and powerful so almost endless workflow possibilities open in opposition to centralized VCS like Perforce or CVS. All the information different teams produce while collaborating on source code and other digital assets in GitLab can be easily analyzed, authorized and streamlined from the Merge Request with clockwork precision. This, in turn, allows for team leads to correctly implement best practice workflows like GitLab Flow – Stackoverflow's 2018 survey says 87% of respondents use Git (jump from 69% in 2015) as opposed to other centralized and distributed VCSs. Similar trend is captures in the Open Hub data. In 2019 they didn't even ask the question in the same survey. – Gartner's Market Guide for Software Change and Configuration Management from 2015 lays out clearly the advantages of DVCS. In 2019 Gartner assess SCM as part of Application Release Orchestration of which GitLab is a challenger as of 2019Google trends since 2004 compared to other DVCS and CVCSs.
Single Application The ability to connect every phase of the Software Development Lifecycle in one single DevOps platform. One data layer, one design system, one set of commands to manage all the different stages of software design, development, build and deployment General proof points of the single app
Product Development Management GitLab is the only product that increasingly provides collaboration functionality to Product teams that work not only with source code but also and IP, graphic assets, animations and binaries to mention a few. Forrester's Adopt Product Management to Connect Design and Development clearly states that "Siloed Design And Dev Teams Deliver Subpar Software"

Message House

A message house contains all the pieces of content that will clearly convey GitLab's values and differentiators in each touch point with prospects and clients. Each touchpoint should be worth their while and should also be relevant in their relationship with GitLab in order to move the needle in their decision-making process. In other words, every single item of the message house is in context with each persona, connect with their intents, resonates with their inflection points (value drivers) and provides an easy narrative of the SCM use case to lay out next steps and make progress.

The message house for the use case provides a structure to describe and discuss the value and differentiators for the use case.

Discovery Questions

The sample discovery questions below are meant to provide a baseline and help you uncover opportunities when speaking with prospects or customers who are not currently using GitLab for VC&C. See a more complete list of questions, provide feedback, or comment with suggestions for GitLab's VC&C discovery questions and feel free to contribute!

Sample Discovery Questions

Competitive Comparison

Amongst the many competitors in the DevOps space, GitHub, Perforce, Azure DevOps, SVN are the closest competitors offering SCM capabilities. Phabricator, Gerrit, GitHub, BitBucket, Azure DevOps, Crucible, Review Board, Reviewable, CodeStream, GitLens, VS Live Share and Gitpod are the closest offering Code Review capabilities. Cloud9, Codesandbox, Repl.it, Koding, StackBlitz, Theia, Gitpod, Coder, VS Online are the closest competitors offering a webIDE. Psatebin, Blocks, Gist.io, Bitbucket Snippets, Codesandbox, JSBin, JSFiddle, Codepen are the closest offering snippets. Invision, Figma, UX Pin are the closest competitors offering Design Management capabilities.

Industry Analyst Relations (IAR) Plan

For a list of analysts with a current understanding of GitLab's capabilities for this use case, please reach out to Analyst Relations via Slack (#analyst-relations) or by submitting an issue and selecting the "AR-Analyst-Validation" template.

Proof Points - Customer Recognitions

General proof points and Customer Recognition

Quotes and reviews

Gartner Peer Insights

Gartner Peer Insights reviews constitute the subjective opinions of individual end users based on their own experiences and do not represent the views of Gartner or its affiliates. Obvious typos have been amended.

"The software is intuitive and quite easy to use. Since many software development projects require more than one person, this makes it easy to create teams and collaborate."

"Improves productivity of engineers by providing easy and fast ways to keep feature branches and merge them quickly and efficiently."

"Keeps your software projects under control. Rogue developers are kept at bay via enforced review processes and pipelines."

"For managing git repositories it is the best product available right now in the market."

"This has really aided in our ability to automate software delivery and return wasted overhead back to the pool of resources! This is a very simple to use and fast delivery tool to assist your code pipeline."

"We use this platform in our company to version our source [code] ensure they are up to date and as a backup option. It enables us build scalable and high quality products. Ease of use and compatible with most development environments."

"I appreciate its ability to run limitless. It has various features like issue tracker, protected branches and merge requests, which gives very nice experience."

"GitLab is a very useful SCM. In our [organization] we have used it as a source code repository. We have extensively used branching and tags creation feature. As we work in a sprints, we have several sprint and feature branches."

"GitLab is a superb version control and collaboration [provider]."

"Before GitLab, we used to make local copies of code or backup the code and then pass on the code through the server. But if our organization knew about GitLab from start, we would have immediately integrated with our development practises for ease of deployment."

Case Studies

ESA (European Space Agency)

Goldman Sachs

Worldline

NorthWestern Mutual Commit San Francisco 2020: Why we chose GitLab as our Enterprise SCM Deck

References to help you close

Links to Salesforce References Note: Sales team members should have access to this report. If you do not have access, reach out to the customer reference team for assistance.

Adoption Guide

The following section provides resources to help TAMs lead capabilities adoption, but can also be used for prospects or customers interested in adopting GitLab stages and categories.

Playbook Steps

Adoption Recommendation

This table shows the recommended use cases to adopt, links to product documentation, the respective subscription tier for the use case, and telemetry metrics.

Feature / Use Case F/C Basic S/P G/U Notes Telemetry
Adopt GitLab Flow X X X X    
Native Highly Available / Performance Git Storage Support X X X X Technical Support for Gitaly Cluster only availabe for Premium/Utlimate  
Simplify Repository Management   X X X CodeOwners file, push rules  
Merge Request Approval Workflow   X X X MergeApproval  
Templates for efficient workflows     X X Project templates, Group/Instance templates for gitlab-ci.yml etc  
Commit Protection     X X Reject Unsigned Commits, Verified Committer  
Large distributed team     X X GitLab Geo  
Repository Protection       X IP Allowlist/Denylist  

The table includes free/community and paid tiers associated with GitLab's self-managed and cloud offering.

Enablement and Training

The following will link to enablement and training videos and content.

Professional Service Offers

GitLab offers a variety of pre-packaged and custom services for our customers and partners. The following are service offers specific to this solution. For additional services, see the full service catalog.

Key Value (at tiers)

Starter/Bronze

Why choose Gitlab Starter/Bronze for VC&C? GitLab Bronze/Starter makes it easy for development and design teams to efficiently collaborate and integrate more frequently while improving code security, quality, and compliance.

Even before fast branching is invoked, dev and design teams can work together at the requirements / user story level on design discussions setting expectations of the upcoming changes much clearer. Then, the GitLab Merge Request workflow encourages collaboration and provides stakeholder visibility and approvals becoming the hub for software development. Whatever happens to the code in that branch can be monitored and controlled from the MR. Developers, through the conversation the Merge Request hosts, are able to craft higher quality and more secure code with native code intelligence in the webIDE and code quality feedback. Collaboration happens while keeping the highest security for the IP hosted. This and compliance are achieved with secure user identification through LDAP and AD, user roles, signed commits, push and MR rules, protected branches, files and paths and audit trails provide.

The results are higher quality code with fewer defects and less rework as well as higher integration frequency with less cognitive load to new and existing team members.

Key features with Starter/Bronze:

Premium/Silver

Why choose Gitlab Premium/Silver for VC&C? Make your projects always available and keep all teams connected throughout the globe. With Premium/Silver access to source code and global collaboration is as trivial as pair programming in the office.

GitLab's GEO functionality can improve download speeds 300% by removing network frustration from globally distributed teams. It enables innovation at scale without compromising performance, security and uptime, especially combined with Gitaly Clusters which means High Availability, high performance, and disaster recovery.

Serve your different remote teams with filtered LDAP access to specific IP hosting repos. Be able to request signed commits and enforce collaboration rules like code review rules. Leverage the power of Git protocol v2, sparse checkout and partial clone to have the most relevant copy of the centralized repo anywhere, anytime.

Key features with Premium/Silver:

Ultimate/Gold

Why choose Gitlab Ultimate/Gold for VC&C? Keep your IP and teams compliant and secure all the time. Provide GitLab admin’s with state of the art capability to handle large, widely distributed instances of GitLab in the most secure and flexible way. Verify everything is in place and take immediate, concise action when something goes wrong in the Security Dashboard.

Compliance programs are fully supported in GitLab. Compliance professionals can use the Compliance Dashboard to promptly find the information they need by having the relevant information surfaced from the different projects to the dashboard. Time required to manage compliance needs is thus dramatically reduced.

Key features with Ultimate/Gold:

Resources

Presentations

Customer deck

Customer facing slides

Roadmap

6 months / 1 year roadmap slide

Videos

Git Training

Integrations Demo Videos

Clickthrough & Live Demos

Talks and customer References

GIT is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license