The Verify and Release stages were recently added to the Ops section. Some direction content listed on the page is still shown from the former CI/CD section. Over time it will be migrating to Ops pages.
GitLab CI/CD is a powerful tool built into GitLab that allows our customers to apply all the continuous methods (Continuous Integration, Delivery, and Deployment) to their software with no third-party application or integration needed.
The goal of the Verify and Release team is to provide a seamless experience and clear guidance to empower users of all knowledge levels to ship their code as fast as possible without interruptions. Our design mission is bringing to the forefront simple, clean ways to make GitLab be the tool of choice for deploying where, when, and how users want to.
See all Verify and Release UX Team members and open vacancies.
Our strategy is all about making sure that even complex delivery flows become an effortless part of everyone's primary way of working. We work closely with Engineering, Product Management, User Research, Technical Writing, and Product Marketing to make sure we have all the support in uncovering user needs and work to solve them together.
|Jobs to be done framework||Work with our PMs to identify the top tasks (in frequency or importance) for our users, based on user research (analytics or qualitative findings). By analyzing how they change depending on factors such as size of company, roles and responsibilities, and personas, we can evaluate their experience trhough an UX Scorecard.|
|UX Scorecards and recommendations||Creating an UX Scorecards with associated Recommendations enables us to identify our user's workflows, as well as understand different types of workflows from existing, new, and/or non-users, scope and track the efforts of addressing usability concerns for these workflows, explore specific situational problems we are look to solve now and in future iterations. When a scorecard is complete, we have the information required to collaborate with PMs on grouping fixes into meaningful iterations and prioritizing UX-related issues.|
|Opportunity canvas||Collaborate with PM during the validation track build a document to understand the user pain, the business value, and the constraints to a particular problem statement.|
|Stakeholder interviews||Serve as a quick and comprehensive way of taking inventory of our current challenges across the Release stage. The analysis of these will then allow us to understand what user data we should be looking for in order to support the team in addressing those challenges.|
|User and customer interviews||Gather external understanding from GitLab users and non-users. We use feedback from interviews to inform our personas, understand and develop objectives and goals for features.|
Visit CI/CD Product Section Direction to read about the product strategy.
We have business goals we are shooting for all the time. To understand how we can measure success in the CI/CD area, we collect insights from our strategic counterparts: Product Marketing Managers, Analyst Relations, and Customer Success.
|Stage group||PMM (Product Marketing Manager)||AR (Analyst Relations)||CS (Customer Success)|
|Verify:Continuous Integration||Joyce Tompsett, Ryan Ragozzine||Jamie Reid, Vladimir Dzalbo|
|Verify:Runner||Joyce Tompsett, Ryan Ragozzine||Jamie Reid, Vladimir Dzalbo|
|Verify:Testing||Joyce Tompsett, Ryan Ragozzine||Jamie Reid, Vladimir Dzalbo|
|Package||Joyce Tompsett, Ryan Ragozzine||Brian Cupini|
|Release:Progressive Delivery||Joyce Tompsett, Ryan Ragozzine||Karen Kwentus, Manuel Kraft|
|Release:Release Management||Joyce Tompsett, Ryan Ragozzine||Karen Kwentus, Manuel Kraft|
Our solutions are meant to help organisations scale efficiently and effectively by automating software delivery processes and orchestrating deployments to go production at a low cost. We are focusing on these roles and personas to create the best user experience possible.
OKRs stand for Objectives and Key Results and we manage them as quarterly goals. They lay out our plan to execute our strategy and help make sure our goals and how to achieve them are clearly defined and aligned throughout the organization.
Learn more about Verify and Release UX Team OKRs.
Our goal is to stay connected with GitLab users all around the world and gather insight into their behaviors, motivations, and goals when using GitLab.
Read more about how we do UX Research at GitLab.
We see customer journeys as stories about understanding our users, how they behave, and what we can do to improve their trip. We use UX Scorecards to perform this analysis and evaluate user experience.
See all Verify and Release UX Scorecards.
We work closely with Product Management to understand business goals by collaboratively answering product foundational questions:
The Verify & Release Design Review meeting goals are to showcase the work that every Product Designer in our team is performing, and collect feedback and ideas from other team members. This session is an excellent platform for identifying dependencies between design work in all Verify and Release stage groups.
We meet bi-weekly as a team to discuss our work, processes, talk about User Research activities, share knowledge, and raise questions to each other. We are also using session for team retrospectives, as well as sharing useful resources around design and DevOps domains.
We are currently experimenting with meeting once a month with all the Product Designers in Ops UX (Verify, Release, Package, Configure and Monitor stage groups) for Design Review sessions to discuss the design work we are performing, share knowledge, and manage dependencies.
The Verify and Release UX team is currently experimenting with a milestone kickoff pilot program that is led by designers. It aims to showcase upcoming work within Verify and Release groups, identify overlapping items, trigger design discussions, and find ways to keep the company informed of our UX work.
The purpose of Ops Cross-Stage ThinkBIG! meeting is to discuss the vision, product roadmap, user research, and design work related to the Cross-Stage Ops experience at GitLab.