GitLab CI/CD UX Milestone Kick-off, 18 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: UX Kickoff 13.1 - Verify and Release - UX Research

Description

Welcome to the 13.1 Release Management UX kickoff! I'm Lorie Whitaker, Staff UX Researcher at GitLab.

The Release Management Team is responsible for the categories of Release Evidence, Release Orchestration, Secrets Management, and GitLab Pages.

In 13.1, my research efforts will be focused on Merge Requests. I'll be diving into defining what poor performance looks like for various users as well as supporting the design teams who are making design changes to the MR process.

I'll also be working on defining JTBD across GitLab, in order to establish shared definitions of what JTBD are, how to create them and validate them, and how Product and UX should use them.

- MR - https://gitlab.com/gitlab-org/ux-research/-/issues/836
- JTBD - https://gitlab.com/gitlab-org/ux-research/-/issues/865

A

This is the verify and release cux milestone kickoff for 13.1, I'm lori whitaker. I am the staff researcher for verify and release here at git lab and two things that I'll be working on. This milestone is jobs to be done. We're going to I'm going to run an alignment workshop.

A

This this milestone, talking about defining what jobs to be done are how to use them, how to create them and how to verify them and validate them across gitlab. So um the outcome for this workshop will be an update to my mr on jobs to be done as well as getting started on some training modules in udemy that people can take. The other item that I'll be working on is merge, requests trying to understand what we got going on with that.

A

It ties to issue 836, and the main goal of that issue is to get more generalized research on merge requests around performance. So we can understand what are the performance issues and maybe why those are performance issues and really tie that back to some of the customers who indicated issues with that from the mps research uh and tying to that is also trying to define what poor performance is and also diving into our on-prem customers to see if they're also having those same issues and if not, what issues are they having?

A

So this is going to be a overarching project that will take the whole entire quarter, because it is such a large effort, but that is the beginning of the effort.