This is a system message 
This is a system message 
This is a system message 
Please upgrade your plan for unlimited use
Please update your credit card for unlimited use
INTRO

GitLoft | Mission

Use Template

AUTHOR

GitLoft | Mission

Looks like you're new here! Create a project to get started.
100%

PURPOSE

TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
100%
Make it so that Everyone Can Contribute 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
100%

VISION

TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
100%
Becoming the Most Popular Collaboration Tool for Knowledge Workers in any Industry 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%

STRATEGY

TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
ICONIC TEAM - Inclusive growth & development for every team member 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
OPEN CORE - Make Open Core the most intuitive, secure, and adaptable 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
CUSTOMER CENTRICITY - The customer will be the center of our operations. $800M in FY23. 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
OWN DEVOPS - Accelerate market maturity around the DevOps Platform 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%

VALUES

TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Collaboration 
TL

To achieve results, team members must work together effectively. At GitLab, helping others is a priority, even when it is not immediately related to the goals that you are trying to achieve. Similarly, you can rely on others for help and advice—in fact, you're expected to do so. Anyone can chime in on any subject, including people who don't work at GitLab. The person who's responsible for the work decides how to do it, but they should always take each suggestion seriously and try to respond and explain why it may or may not have been implemented.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Results 
TL

We do what we promised to each other, customers, users, and investors.

Measure results not hours

We care about what you achieve: the code you shipped, the user you made happy, and the team member you helped. Someone who took the afternoon off shouldn't feel like they did something wrong. You don't have to defend how you spend your day. We trust team members to do the right thing instead of having rigid rules. Do not incite competition by proclaiming how many hours you worked yesterday. If you are working too many hours, talk to your manager to discuss solutions.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Efficiency 
TL

Working efficiently on the right things enables us to make fast progress, which makes our work more fulfilling.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Diversity, Inclusion & Belonging 
TL

Diversity, inclusion and belonging are fundamental to the success of GitLab. We aim to make a significant impact in our efforts to foster an environment where everyone can thrive. We are designing a multidimensional approach to ensure that GitLab is a place where people from every background and circumstance feel like they belong and can contribute. We actively chose to build and institutionalize a culture that is inclusive and supports all team members equally in the process of achieving their professional goals. We hire globally and encourage hiring in a diverse set of countries. We work to make everyone feel welcome and to increase the participation of underrepresented minorities and nationalities in our community and company. For example, we celebrate our sponsorship of diversity events and triple the base referral bonus amount.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Iteration 
TL

We do the smallest thing possible and get it out as quickly as possible. If you make suggestions that can be excluded from the first iteration, turn them into a separate issue that you link. Don't write a large plan; only write the first step. Trust that you'll know better how to proceed after something is released. You're doing it right if you're slightly embarrassed by the minimal feature set shipped in the first iteration. This value is the one people most underestimate when they join GitLab. The impact both on your work process and on how much you achieve is greater than anticipated. In the beginning, it hurts to make decisions fast and to see that things are changed with less consultation. But frequently, the simplest version turns out to be the best one.

People that join GitLab all say they already practice iteration. But this is the value that is the hardest to understand and adopt. People are trained that if you don't deliver a perfect or polished thing, there will be a problem. If you do just one piece of something, you have to come back to it. Doing the whole thing seems more efficient, even though it isn't. If the complete picture is not clear, your work might not be perceived as you want it to be perceived. It seems better to make a comprehensive product. They see other GitLab team members being really effective with iteration but don't know how to make the transition, and it's hard to shake the fear that constant iteration can lead to shipping lower-quality work or a worse product. It is possible to ship a minimally viable product while continuing to adhere to the documented quality standards.

The way to resolve this is to write down only what you can do with the time you have for this project right now. That might be 5 minutes or 2 hours. Think of what you can complete in that time that would improve the current situation. Iteration can be uncomfortable, even painful. If you're doing iteration correctly, it should be. Reverting work back to a previous state is positive, not negative. We're quickly getting feedback and learning from it. Making a small change prevented a bigger revert and made it easier to revert.

However, if we take smaller steps and ship smaller, simpler features, we get feedback sooner. Instead of spending time working on the wrong feature or going in the wrong direction, we can ship the smallest product, receive fast feedback, and course correct. People might ask why something was not perfect. In that case, mention that it was an iteration, you spent only "x" amount of time on it, and that the next iteration will contain "y" and be ready on "z".

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Transparency 
TL

Be open about as many things as possible. By making information public, we can reduce the threshold to contribution and make collaboration easier. Use public issue trackers, projects, and repositories when possible.

An example is the public repository of this website that also contains this company handbook. Everything we do is public by default, such as the GitLab CE and GitLab EE issue trackers, as well as marketing and infrastructure. Transparency creates awareness for GitLab, allows us to recruit people that care about our values, gets us more and faster feedback from people outside the company, and makes it easier to collaborate with them. It is also about sharing great software, documentation, examples, lessons, and processes with the whole community and the world in the spirit of open source, which we believe creates more value than it captures.

There are exceptions. Material that is not public by default is documented. We are above average at keeping things confidential that need to be. On a personal level, you should tell it like it is instead of putting up a poker face. Don't be afraid to admit you made a mistake or were wrong. When something goes wrong, it is a great opportunity to say "What’s the kaizen moment here?" and find a better way without hurt feelings.

Even as a public company, we know that our value of transparency will be key to our success. This value can be hard to follow at times. You might ask yourself: what should be shared, how much to share, whether or not to speak up but definitely take the time to always opt for maximum transparency by adhering to the sub-values below. Often, company values get diluted as they grow, most likely because they do not write anything down. But we will make sure our values scale with the company. When we go public, we can declare everyone in the company as an insider, which will allow us to remain transparent internally about our numbers, etc. Everything else that can be transparent will continue to be so.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%

METRIC

TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Net ARR vs. plan (lagging) North Star KPI 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%

MISSION

TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Make it so that everyone can contribute by becoming the most popular collaboration tool for knowledge workers in any Industry. 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%

TEAM

TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%

PLAN

TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
/GitLoft | Q3 2022 Plan 
TL
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%

MESSAGE

TL
GitLoft is The DevOps Platform
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Increase Operational Efficiencies 
TL

Simplify the software development toolchain to reduce total cost of ownership

Before

  • Process - manual; complex
  • Tools - don’t scale; too many; legacy; custom; homegrown; outages
  • People - functional silos; misaligned priorities; working on wrong things; fighting fires; dissatisfied
  • Integrations - brittle; complicated

Negative Consequences

  • Lower productivity; more rework; slower cycle time
  • Toolchain is expensive to license and support
  • Poor developer experience; wasted talent; high turnover in engineering
  • Product launch delays

After

  • Process - simplified, predictable SDLC process; less ramp time; reduced context switching
  • Tools - scale with business and developer needs; more complete coverage; no customization
  • People - teams are more productive and collaborative
  • Integrations - fewer; less complicated

Positive Business Outcomes

  • Reduce product development and delivery costs
  • Elimination of bottlenecks leads to agility and faster time to market
  • Happy developers - attract and retain top talent
  • Move engineers from integration and maintenance to value-add activities

Required Capabilities

  • Consistent and efficient developer experience across the development lifecycle
  • Centralized reporting and visibility across the development lifecycle
  • At point of code change, developers can assess and resolve security, compliance and code quality issues
  • Solution that automatically scales to match performance and cost demands of the organization
  • Public cloud independent; develop in one place, deploy anywhere
  • SaaS and/or self-managed

Metrics

  • TCO (license, FTEs and compute costs) of toolchain
  • Cycle time (time per stage and waiting time); throughput per developer
    Deployment frequency
  • Change failure rate
  • MTTR (mean time to resolution)
  • Developer turnover; employee SAT

How We Do It

  1. Complete DevOps Platform - GitLab is a complete DevOps platform, delivered as a single application, fundamentally changing the way development, security and ops teams collaborate. The single platform delivers capabilities across DevSecOps SDLC.
    Start with GitLab just on the use case that you need to improve
    Continue using tools you love
    Begin evolution to a single end-to-end experience for all of DevSecOps
    Collaboration, visibility, control and reporting from idea to production
    Improving cycle time from weeks to minutes greatly reduces development costs and time to market while increasing developer productivity and the ability to attract and retain developer talent

  2. Faster cycle time while also improving quality and security:
    Single application
    Rapidly innovating platform
    High performance with easy scaling and management
    Increased developer productivity

Better

  • Single Application
  • Minimize friction and reduce handoff time between teams by collaborating at the point of code change
  • One interface and one login
  • One permissions model
  • One data store
  • Built for Multi-Cloud
  • Easily deploy anywhere, especially with Kubernetes
  • GitLab CD is seamlessly included in CI, enabling multi-cloud deployments and progressive delivery with easy automation
    Same Experience on Flexible GitLab Hosting Options
    Identical performance and flexibility on SaaS or self-managed (on prem or any cloud service)
  • Deploy GitLab to any cloud service
  • High Performance with Easy Scaling and Management:
  • Highly scalable architecture, powered by extensible YAML instead of plug-ins
  • Templated YAML file architecture enables self-service, flexible CI that doesn't require additional resources
  • Runners scale based on demand through auto-scaling and parallelizing pipelines
  • Distributed - execute runners on any operating system (Mac, Linux, or Windows) or in the cloud at the same time

Proof Points

Customer References/Case Studies

  • ENT - Goldman Sachs | Problem: Needed to increase developer efficiency and software quality | Solution: GitLab Premium (CI/CD, SCM) | Result: Improved from 2 builds/day to over 1000/day; simplified workflow and simplified administration

  • ENT - Jaguar Land Rover | Problem: Slow delivery and release cycles taking 4 to 6 weeks leading to infrequent feedback for developers | Solution: GitLab Premium (CI) | Result: Increased delivery speed from 3-6 weeks to 30 minutes giving teams faster feedback

  • MM - Alteryx | Problem: Legacy developer tools slowed software delivery frequency | Solution: GitLab Ultimate (CI, CD, Security, SCM) | Result: Decreased software builds from over 3 hours to 30 minutes; able to release 9 times a day

  • MM - Worldline | Problem: Long cycle times and difficulty collaborating between developers | Solution: GitLab Community Edition (SCM, CI) | Result: From 2 weeks to set up a new project to just minutes; 120x increase in code reviews

  • SMB - Wag! | Problem: Slow release process taking over 40 minutes | Solution: GitLab Ultimate (CI, CD) | Result: Release process reduced to 6 minutes; 8 releases per day with built in security; a full deployment pipeline to Amazon Elastic Container Service (ECS)

Industry Awards

  • 2019 | IDC Innovators: Tools Supporting Open (Unopinionated) Developer Platforms | Demonstrated either a groundbreaking business model or an innovative new technology or both
  • 2018 | IDC Innovators: Agile Code Development Technologies | Demonstrated either a groundbreaking business model or an innovative new technology or both
  • 2019 | Gartner Peer Insights Customers’ Choice - Enterprise Agile Planning Tools | Over 90 peer reviews with a 4.6 rating: “DevOps without the overhead” , “Simple, Intuitive and efficient DevOps Life Cycle tool”, and “GitLab increases engineering productivity”
  • 2018 | G2 Crowd Leader | Over 170 public reviews with a 4.4 rating - “Powerful team collaboration tool for managing software development projects”, “Great self-hosted open-source source control system”, and “efficient, can trace back, easy to collaborate”
  • 2018 | Gartner Peer Insights Customers’ Choice - Application Release Orchestration | Over 230 peer reviews with a 4.5 rating - “GitLab Makes Development Streamlined”, “One of the best DevOps Lifecycle tools”, and “Excellent Tools For DevSecOps Initiative…”
  • 2018 | Google Cloud Partner Awards | Innovative Solution in Developer Ecosystem for the tight integration with GKE

Analyst Reports/Studies

  • Forrester | Q3 2017 Continuous Integration Wave - Leader | Continuous Integration streamlines and accelerates building and testing developer code, shortening delivery to minutes rather than weeks and months. Continuous integration also automates compliance tasks and improves audibility.
  • Gartner | 2019 Enterprise Agile Planning Tools - Visionary | Agile planning tools help scale agile development practices, encourage collaboration and enable faster delivery to respond to customer needs.
  • Forrester | 2019 Manage Your Toolchain Before it Manages You | Multiple tools and toolchains create visibility, security and productivity challenges for development and operations teams; “Out-of-the-box” toolchain solutions are seen as a solution; increasing security, revenue and quality.
  • Gartner | 2019 Hype Cycle for DevOps | GitLab helped to define the market and is included as a relevant vendor for Toolchain, Toolchain Orchestration and Application Release Orchestration.
  • Gartner | 2019 Hype Cycle for Infrastructure and Operations Automation | GitLab helped to define the market and is recognized as a relevant vendor for both Continuous Delivery and Toolchain Orchestration
  • Gartner | 2019 Hype Cycle for Application Security | GitLab is recognized as a relevant vendor for Application Monitoring and Protection.

GitLab Reports/Studies

  • 2019 Global Developer Report: DevSecOps | Ops teams are 1.8x more likely to believe they get sufficient notice to support the developer side when their DevOps practice is very good. | Visibility and transparency into future work leads to more efficient planning and execution.
  • 2018 Developer Report | 86% of developers agree that continuous integration alleviates blockers in the development process. | Enabling automation and continuous integration can increase overall efficiency and velocity.

Discovery Questions

  1. Opening Questions (To Establish Credibility and Provide Relevant Insights)
    Thank you for chatting today. I am curious as to why you took this meeting.
    The most common reason organizations like yours contact us is to consolidate their DevOps toolchain to drive operational efficiencies. However, as we get deeper into those discussions, we often find that organizations have a digital transformation initiative. To meet their goals, they need to deliver better products faster and/or they want to ensure their code is tested to reduce risk. Which of these resonates with you? Why?
  2. Value Driver-Specific Questions (Increase Operational Efficiencies)
    Before/Negative Consequences
    Walk me through how you currently manage your application development and delivery process. What tools do you utilize and how satisfied are you with those tools?
    Describe how you would characterize the developer workflow for this process. How many different tools and screens (browser windows) does the developer have to navigate to in order to do their work? How does this affect their productivity and job satisfaction?
    What integrations does your team manage across the various DevOps tools? What complexities or challenges do these integrations present? Describe the level of effort that is required to maintain these integrations.
    How do you keep your teams up-to-date with the various tools they use? How much do you currently invest in licensing, managing, maintaining and training your teams?
    Describe the unforeseen delays you are experiencing as you build and deploy your applications. How do you currently mitigate these delays?
    Describe the separate toolchains your organization has in place to develop and deliver your software. What’s the impact on developer experience and productivity?

After/Positive Business Outcomes

  • In an ideal world, how would you like your development, security and operations teams to collaborate? Describe the current initiatives to address this.
  • If you were to streamline your toolchain, where would you start? What would you want to remain the same?
  • In what ways could streamlining your development toolchain impact your ability to deliver projects on time and on budget?
  • What percentage of your team’s time is spent on innovation versus on keeping the integrations operational? If most of those people could work on innovation, how would that impact the business?
  • Describe how your developer productivity could change if they only had one application to learn and use.

Required Capabilities/Metrics

  • What do you need to improve the alignment between your development, security and operations teams throughout the DevOps lifecycle?
  • What environments/clouds are you currently deploying to? Describe how your tool selection enables you to be efficient in supporting your cloud strategy.
  • What capabilities would enable BOTH organizational efficiencies AND developer satisfaction?
  • How would your team benefit if developers had full team visibility on their projects and respective code?
  • Walk me through how you currently track and measure developer satisfaction, productivity and turnover. Where do you think your company would stand in the rankings of ‘great place to be a developer’?
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Deliver Better Products Faster 
TL

Accelerate the software delivery process to meet business objectives

Before

  • Process - manual; complex
  • Tools - don’t scale; too many; legacy; custom; homegrown; outages
  • People - functional silos; misaligned priorities; working on wrong things; fighting fires; dissatisfied
  • Integrations - brittle; complicated

Negative Consequences

  • Lower productivity; more rework; slower cycle time
  • Toolchain is expensive to license and support
  • Poor developer experience; wasted talent; high turnover in engineering
  • Product launch delays

After

  • Process - simplified, predictable SDLC process; less ramp time; reduced context switching
  • Tools - scale with business and developer needs; more complete coverage; no customization
  • People - teams are more productive and collaborative
  • Integrations - fewer; less complicated

Positive Business Outcomes

  • Reduce product development and delivery costs
  • Elimination of bottlenecks leads to agility and faster time to market
  • Happy developers - attract and retain top talent
  • Move engineers from integration and maintenance to value-add activities

Required Capabilities

  • Consistent and efficient developer experience across the development lifecycle
  • Centralized reporting and visibility across the development lifecycle
  • At point of code change, developers can assess and resolve security, compliance and code quality issues
  • Solution that automatically scales to match performance and cost demands of the organization
  • Public cloud independent; develop in one place, deploy anywhere
  • SaaS and/or self-managed

Metrics

  • TCO (license, FTEs and compute costs) of toolchain
  • Cycle time (time per stage and waiting time); throughput per developer
    Deployment frequency
  • Change failure rate
  • MTTR (mean time to resolution)
  • Developer turnover; employee SAT

How We Do It

  1. Complete DevOps Platform - GitLab is a complete DevOps platform, delivered as a single application, fundamentally changing the way development, security and ops teams collaborate. The single platform delivers capabilities across DevSecOps SDLC.
    Start with GitLab just on the use case that you need to improve
    Continue using tools you love
    Begin evolution to a single end-to-end experience for all of DevSecOps
    Collaboration, visibility, control and reporting from idea to production
    Improving cycle time from weeks to minutes greatly reduces development costs and time to market while increasing developer productivity and the ability to attract and retain developer talent

  2. Faster cycle time while also improving quality and security:
    Single application
    Rapidly innovating platform
    High performance with easy scaling and management
    Increased developer productivity

Better

  • Single Application
  • Minimize friction and reduce handoff time between teams by collaborating at the point of code change
  • One interface and one login
  • One permissions model
  • One data store
  • Built for Multi-Cloud
  • Easily deploy anywhere, especially with Kubernetes
  • GitLab CD is seamlessly included in CI, enabling multi-cloud deployments and progressive delivery with easy automation
    Same Experience on Flexible GitLab Hosting Options
    Identical performance and flexibility on SaaS or self-managed (on prem or any cloud service)
  • Deploy GitLab to any cloud service
  • High Performance with Easy Scaling and Management:
  • Highly scalable architecture, powered by extensible YAML instead of plug-ins
  • Templated YAML file architecture enables self-service, flexible CI that doesn't require additional resources
  • Runners scale based on demand through auto-scaling and parallelizing pipelines
  • Distributed - execute runners on any operating system (Mac, Linux, or Windows) or in the cloud at the same time

Proof Points

Customer References/Case Studies

  • ENT - Goldman Sachs | Problem: Needed to increase developer efficiency and software quality | Solution: GitLab Premium (CI/CD, SCM) | Result: Improved from 2 builds/day to over 1000/day; simplified workflow and simplified administration

  • ENT - Jaguar Land Rover | Problem: Slow delivery and release cycles taking 4 to 6 weeks leading to infrequent feedback for developers | Solution: GitLab Premium (CI) | Result: Increased delivery speed from 3-6 weeks to 30 minutes giving teams faster feedback

  • MM - Alteryx | Problem: Legacy developer tools slowed software delivery frequency | Solution: GitLab Ultimate (CI, CD, Security, SCM) | Result: Decreased software builds from over 3 hours to 30 minutes; able to release 9 times a day

  • MM - Worldline | Problem: Long cycle times and difficulty collaborating between developers | Solution: GitLab Community Edition (SCM, CI) | Result: From 2 weeks to set up a new project to just minutes; 120x increase in code reviews

  • SMB - Wag! | Problem: Slow release process taking over 40 minutes | Solution: GitLab Ultimate (CI, CD) | Result: Release process reduced to 6 minutes; 8 releases per day with built in security; a full deployment pipeline to Amazon Elastic Container Service (ECS)

Industry Awards

  • 2019 | IDC Innovators: Tools Supporting Open (Unopinionated) Developer Platforms | Demonstrated either a groundbreaking business model or an innovative new technology or both
  • 2018 | IDC Innovators: Agile Code Development Technologies | Demonstrated either a groundbreaking business model or an innovative new technology or both
  • 2019 | Gartner Peer Insights Customers’ Choice - Enterprise Agile Planning Tools | Over 90 peer reviews with a 4.6 rating: “DevOps without the overhead” , “Simple, Intuitive and efficient DevOps Life Cycle tool”, and “GitLab increases engineering productivity”
  • 2018 | G2 Crowd Leader | Over 170 public reviews with a 4.4 rating - “Powerful team collaboration tool for managing software development projects”, “Great self-hosted open-source source control system”, and “efficient, can trace back, easy to collaborate”
  • 2018 | Gartner Peer Insights Customers’ Choice - Application Release Orchestration | Over 230 peer reviews with a 4.5 rating - “GitLab Makes Development Streamlined”, “One of the best DevOps Lifecycle tools”, and “Excellent Tools For DevSecOps Initiative…”
  • 2018 | Google Cloud Partner Awards | Innovative Solution in Developer Ecosystem for the tight integration with GKE

Analyst Reports/Studies

  • Forrester | Q3 2017 Continuous Integration Wave - Leader | Continuous Integration streamlines and accelerates building and testing developer code, shortening delivery to minutes rather than weeks and months. Continuous integration also automates compliance tasks and improves audibility.
  • Gartner | 2019 Enterprise Agile Planning Tools - Visionary | Agile planning tools help scale agile development practices, encourage collaboration and enable faster delivery to respond to customer needs.
  • Forrester | 2019 Manage Your Toolchain Before it Manages You | Multiple tools and toolchains create visibility, security and productivity challenges for development and operations teams; “Out-of-the-box” toolchain solutions are seen as a solution; increasing security, revenue and quality.
  • Gartner | 2019 Hype Cycle for DevOps | GitLab helped to define the market and is included as a relevant vendor for Toolchain, Toolchain Orchestration and Application Release Orchestration.
  • Gartner | 2019 Hype Cycle for Infrastructure and Operations Automation | GitLab helped to define the market and is recognized as a relevant vendor for both Continuous Delivery and Toolchain Orchestration
  • Gartner | 2019 Hype Cycle for Application Security | GitLab is recognized as a relevant vendor for Application Monitoring and Protection.

GitLab Reports/Studies

  • 2019 Global Developer Report: DevSecOps | Ops teams are 1.8x more likely to believe they get sufficient notice to support the developer side when their DevOps practice is very good. | Visibility and transparency into future work leads to more efficient planning and execution.
  • 2018 Developer Report | 86% of developers agree that continuous integration alleviates blockers in the development process. | Enabling automation and continuous integration can increase overall efficiency and velocity.

Discovery Questions

  1. Opening Questions (To Establish Credibility and Provide Relevant Insights)
    Thank you for chatting today. I am curious as to why you took this meeting.
    The most common reason organizations like yours contact us is to consolidate their DevOps toolchain to drive operational efficiencies. However, as we get deeper into those discussions, we often find that organizations have a digital transformation initiative. To meet their goals, they need to deliver better products faster and/or they want to ensure their code is tested to reduce risk. Which of these resonates with you? Why?
  2. Value Driver-Specific Questions (Increase Operational Efficiencies)
    Before/Negative Consequences
    Walk me through how you currently manage your application development and delivery process. What tools do you utilize and how satisfied are you with those tools?
    Describe how you would characterize the developer workflow for this process. How many different tools and screens (browser windows) does the developer have to navigate to in order to do their work? How does this affect their productivity and job satisfaction?
    What integrations does your team manage across the various DevOps tools? What complexities or challenges do these integrations present? Describe the level of effort that is required to maintain these integrations.
    How do you keep your teams up-to-date with the various tools they use? How much do you currently invest in licensing, managing, maintaining and training your teams?
    Describe the unforeseen delays you are experiencing as you build and deploy your applications. How do you currently mitigate these delays?
    Describe the separate toolchains your organization has in place to develop and deliver your software. What’s the impact on developer experience and productivity?

After/Positive Business Outcomes

  • In an ideal world, how would you like your development, security and operations teams to collaborate? Describe the current initiatives to address this.
  • If you were to streamline your toolchain, where would you start? What would you want to remain the same?
  • In what ways could streamlining your development toolchain impact your ability to deliver projects on time and on budget?
  • What percentage of your team’s time is spent on innovation versus on keeping the integrations operational? If most of those people could work on innovation, how would that impact the business?
  • Describe how your developer productivity could change if they only had one application to learn and use.

Required Capabilities/Metrics

  • What do you need to improve the alignment between your development, security and operations teams throughout the DevOps lifecycle?
  • What environments/clouds are you currently deploying to? Describe how your tool selection enables you to be efficient in supporting your cloud strategy.
  • What capabilities would enable BOTH organizational efficiencies AND developer satisfaction?
  • How would your team benefit if developers had full team visibility on their projects and respective code?
  • Walk me through how you currently track and measure developer satisfaction, productivity and turnover. Where do you think your company would stand in the rankings of ‘great place to be a developer’?
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
Reduce Security and Compliance Risk 
TL

Simplify processes to comply with internal processes, controls and industry regulations without compromising speed

Before

  • Process - manual; complex
  • Tools - don’t scale; too many; legacy; custom; homegrown; outages
  • People - functional silos; misaligned priorities; working on wrong things; fighting fires; dissatisfied
  • Integrations - brittle; complicated

Negative Consequences

  • Lower productivity; more rework; slower cycle time
  • Toolchain is expensive to license and support
  • Poor developer experience; wasted talent; high turnover in engineering
  • Product launch delays

After

  • Process - simplified, predictable SDLC process; less ramp time; reduced context switching
  • Tools - scale with business and developer needs; more complete coverage; no customization
  • People - teams are more productive and collaborative
  • Integrations - fewer; less complicated

Positive Business Outcomes

  • Reduce product development and delivery costs
  • Elimination of bottlenecks leads to agility and faster time to market
  • Happy developers - attract and retain top talent
  • Move engineers from integration and maintenance to value-add activities

Required Capabilities

  • Consistent and efficient developer experience across the development lifecycle
  • Centralized reporting and visibility across the development lifecycle
  • At point of code change, developers can assess and resolve security, compliance and code quality issues
  • Solution that automatically scales to match performance and cost demands of the organization
  • Public cloud independent; develop in one place, deploy anywhere
  • SaaS and/or self-managed

Metrics

  • TCO (license, FTEs and compute costs) of toolchain
  • Cycle time (time per stage and waiting time); throughput per developer
    Deployment frequency
  • Change failure rate
  • MTTR (mean time to resolution)
  • Developer turnover; employee SAT

How We Do It

  1. Complete DevOps Platform - GitLab is a complete DevOps platform, delivered as a single application, fundamentally changing the way development, security and ops teams collaborate. The single platform delivers capabilities across DevSecOps SDLC.
    Start with GitLab just on the use case that you need to improve
    Continue using tools you love
    Begin evolution to a single end-to-end experience for all of DevSecOps
    Collaboration, visibility, control and reporting from idea to production
    Improving cycle time from weeks to minutes greatly reduces development costs and time to market while increasing developer productivity and the ability to attract and retain developer talent

  2. Faster cycle time while also improving quality and security:
    Single application
    Rapidly innovating platform
    High performance with easy scaling and management
    Increased developer productivity

Better

  • Single Application
  • Minimize friction and reduce handoff time between teams by collaborating at the point of code change
  • One interface and one login
  • One permissions model
  • One data store
  • Built for Multi-Cloud
  • Easily deploy anywhere, especially with Kubernetes
  • GitLab CD is seamlessly included in CI, enabling multi-cloud deployments and progressive delivery with easy automation
    Same Experience on Flexible GitLab Hosting Options
    Identical performance and flexibility on SaaS or self-managed (on prem or any cloud service)
  • Deploy GitLab to any cloud service
  • High Performance with Easy Scaling and Management:
  • Highly scalable architecture, powered by extensible YAML instead of plug-ins
  • Templated YAML file architecture enables self-service, flexible CI that doesn't require additional resources
  • Runners scale based on demand through auto-scaling and parallelizing pipelines
  • Distributed - execute runners on any operating system (Mac, Linux, or Windows) or in the cloud at the same time

Proof Points

Customer References/Case Studies

  • ENT - Goldman Sachs | Problem: Needed to increase developer efficiency and software quality | Solution: GitLab Premium (CI/CD, SCM) | Result: Improved from 2 builds/day to over 1000/day; simplified workflow and simplified administration

  • ENT - Jaguar Land Rover | Problem: Slow delivery and release cycles taking 4 to 6 weeks leading to infrequent feedback for developers | Solution: GitLab Premium (CI) | Result: Increased delivery speed from 3-6 weeks to 30 minutes giving teams faster feedback

  • MM - Alteryx | Problem: Legacy developer tools slowed software delivery frequency | Solution: GitLab Ultimate (CI, CD, Security, SCM) | Result: Decreased software builds from over 3 hours to 30 minutes; able to release 9 times a day

  • MM - Worldline | Problem: Long cycle times and difficulty collaborating between developers | Solution: GitLab Community Edition (SCM, CI) | Result: From 2 weeks to set up a new project to just minutes; 120x increase in code reviews

  • SMB - Wag! | Problem: Slow release process taking over 40 minutes | Solution: GitLab Ultimate (CI, CD) | Result: Release process reduced to 6 minutes; 8 releases per day with built in security; a full deployment pipeline to Amazon Elastic Container Service (ECS)

Industry Awards

  • 2019 | IDC Innovators: Tools Supporting Open (Unopinionated) Developer Platforms | Demonstrated either a groundbreaking business model or an innovative new technology or both
  • 2018 | IDC Innovators: Agile Code Development Technologies | Demonstrated either a groundbreaking business model or an innovative new technology or both
  • 2019 | Gartner Peer Insights Customers’ Choice - Enterprise Agile Planning Tools | Over 90 peer reviews with a 4.6 rating: “DevOps without the overhead” , “Simple, Intuitive and efficient DevOps Life Cycle tool”, and “GitLab increases engineering productivity”
  • 2018 | G2 Crowd Leader | Over 170 public reviews with a 4.4 rating - “Powerful team collaboration tool for managing software development projects”, “Great self-hosted open-source source control system”, and “efficient, can trace back, easy to collaborate”
  • 2018 | Gartner Peer Insights Customers’ Choice - Application Release Orchestration | Over 230 peer reviews with a 4.5 rating - “GitLab Makes Development Streamlined”, “One of the best DevOps Lifecycle tools”, and “Excellent Tools For DevSecOps Initiative…”
  • 2018 | Google Cloud Partner Awards | Innovative Solution in Developer Ecosystem for the tight integration with GKE

Analyst Reports/Studies

  • Forrester | Q3 2017 Continuous Integration Wave - Leader | Continuous Integration streamlines and accelerates building and testing developer code, shortening delivery to minutes rather than weeks and months. Continuous integration also automates compliance tasks and improves audibility.
  • Gartner | 2019 Enterprise Agile Planning Tools - Visionary | Agile planning tools help scale agile development practices, encourage collaboration and enable faster delivery to respond to customer needs.
  • Forrester | 2019 Manage Your Toolchain Before it Manages You | Multiple tools and toolchains create visibility, security and productivity challenges for development and operations teams; “Out-of-the-box” toolchain solutions are seen as a solution; increasing security, revenue and quality.
  • Gartner | 2019 Hype Cycle for DevOps | GitLab helped to define the market and is included as a relevant vendor for Toolchain, Toolchain Orchestration and Application Release Orchestration.
  • Gartner | 2019 Hype Cycle for Infrastructure and Operations Automation | GitLab helped to define the market and is recognized as a relevant vendor for both Continuous Delivery and Toolchain Orchestration
  • Gartner | 2019 Hype Cycle for Application Security | GitLab is recognized as a relevant vendor for Application Monitoring and Protection.

GitLab Reports/Studies

  • 2019 Global Developer Report: DevSecOps | Ops teams are 1.8x more likely to believe they get sufficient notice to support the developer side when their DevOps practice is very good. | Visibility and transparency into future work leads to more efficient planning and execution.
  • 2018 Developer Report | 86% of developers agree that continuous integration alleviates blockers in the development process. | Enabling automation and continuous integration can increase overall efficiency and velocity.

Discovery Questions

  1. Opening Questions (To Establish Credibility and Provide Relevant Insights)
    Thank you for chatting today. I am curious as to why you took this meeting.
    The most common reason organizations like yours contact us is to consolidate their DevOps toolchain to drive operational efficiencies. However, as we get deeper into those discussions, we often find that organizations have a digital transformation initiative. To meet their goals, they need to deliver better products faster and/or they want to ensure their code is tested to reduce risk. Which of these resonates with you? Why?
  2. Value Driver-Specific Questions (Increase Operational Efficiencies)
    Before/Negative Consequences
    Walk me through how you currently manage your application development and delivery process. What tools do you utilize and how satisfied are you with those tools?
    Describe how you would characterize the developer workflow for this process. How many different tools and screens (browser windows) does the developer have to navigate to in order to do their work? How does this affect their productivity and job satisfaction?
    What integrations does your team manage across the various DevOps tools? What complexities or challenges do these integrations present? Describe the level of effort that is required to maintain these integrations.
    How do you keep your teams up-to-date with the various tools they use? How much do you currently invest in licensing, managing, maintaining and training your teams?
    Describe the unforeseen delays you are experiencing as you build and deploy your applications. How do you currently mitigate these delays?
    Describe the separate toolchains your organization has in place to develop and deliver your software. What’s the impact on developer experience and productivity?

After/Positive Business Outcomes

  • In an ideal world, how would you like your development, security and operations teams to collaborate? Describe the current initiatives to address this.
  • If you were to streamline your toolchain, where would you start? What would you want to remain the same?
  • In what ways could streamlining your development toolchain impact your ability to deliver projects on time and on budget?
  • What percentage of your team’s time is spent on innovation versus on keeping the integrations operational? If most of those people could work on innovation, how would that impact the business?
  • Describe how your developer productivity could change if they only had one application to learn and use.

Required Capabilities/Metrics

  • What do you need to improve the alignment between your development, security and operations teams throughout the DevOps lifecycle?
  • What environments/clouds are you currently deploying to? Describe how your tool selection enables you to be efficient in supporting your cloud strategy.
  • What capabilities would enable BOTH organizational efficiencies AND developer satisfaction?
  • How would your team benefit if developers had full team visibility on their projects and respective code?
  • Walk me through how you currently track and measure developer satisfaction, productivity and turnover. Where do you think your company would stand in the rankings of ‘great place to be a developer’?
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
0%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
%

New

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
%
 
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Enjoy your test drive.  Start a 7 day free trial for unlimited use.You can add 4 more items before upgrading.
Activity
Projects
Templates
Teams