Data Team Programs

Introduction

Welcome to the Data Programs page. Here you’ll find information about the various Data Programs around GitLab and those the Data Team supports, ranging from onboarding to day-to-day operations.

• Data Slack Channels
• Primary Data Slack Channel: #data
• Data Lounge Channel: #data-lounge

Show-n-Tell and Demos

Recordings of previous demos are posted to the GitLab Unfiltered Data Team playlist.

Data Onboarding

If you are onboarding to GitLab and will be working in the Data Program as an Engineer, Analyst or Developer, follow these steps:

1. Open a new issue in GitLab Data Analytics with the Data Onboarding template.
2. Give the issue a descriptive name: Your Name - Data Onboarding
3. Assign the issue to your Manager to add/remove relevant content

Data Proof of Value Guide

The Data Team performs Proof of Value Evaluations (PoVs) for all new technologies we are considering adding to the Data Platform or the broader Technology stack. This Guide is intended to help you perform a PoV efficiently and with great results.

Phase 1: Calculate Value and Define Requirements

1. Establish the Value the technology can provide GitLab. Value can be measured in a variety of ways, ranging from efficiency to increased Sales to reduced compute.
2. Create a Requirements document to define the business and technical requirements the technology must meet to be successful. Indicate whether each requirement is Must Have or Nice to Have. Here is a template we have used for Data Visualization PoV and another we have used for Product Analytics PoV.

Phase 2: Scoping & Policy Awareness

1. Review the Procurement New Software Guide to ensure you understand the latest procurement process to follow.
2. Execute an NDA with each Vendor included in the Evaluation.
3. Obtain preliminary pricing to help validate established budget. If no existing budget is established, work with the Department lead to determine if the project is feasible. Let’s not waste time or energy for projects we can’t fund.

Phase 3: Evaluation Design

Evaluation Design is the most complex part of the PoV.

1. Decide how to test the technology versus defined requirements. Often, successfully testing data technologies requires simulating production workloads and constructing a ‘Production Level SAFE Workload’ is a key challenge in a Data PoV Project.
   • No Red Data or Orange Data is ever suitable for inclusion in a PoV.

Phase 4: Procurement

1. Using the Requirements design as a guide, collaborate with the Vendor to create a Statement of Work (SoW).
   • The Statement of Work should include Success Criteria, Expectations, and a Project Timeline
   • We do not pay for PoVs and all should be $0 Cost
2. Along with the SoW, ask the vendor to send you their Master Services Agreement (MSA).
3. Because request with an amount of $0 is not supported in Coupa, you need to submit the SoW and MSA to Procurement via GitLab in the Procurement project.
   • Submit the SoW and MSA to Procurement via Coupa if the PoV amount is not $0, following this How Do I Submit a Request to Purchase New Software? guide.
     • The process to obtain security approvals is supported in Coupa.

Phase 5: Assessment

1. Create a shared Slack Channel to coordinate the PoV with the Vendor.
2. Reach out to the vendor for references to schedule a reference Calculate. In a reference call you can:
   • ask about the experience with the technology.
   • ask about their lessons learned.
   • ask how we can setup for success.

Phase 6: Wrap-Up

To Be Defined

Data Guides and Related Resources

View page source - Edit this page - please contribute.