GitLab Quality Department, 2 Jul 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Quality team roadmap process

Description

An informal chat demoing how the Quality team is using some great GitLab features to document their roadmap. https://about.gitlab.com/handbook/engineering/quality/roadmap/

A

It's recording okay, so this is a impromptu, unfiltered session on how the quality department documents our roadmap. So what it was saying earlier to Jason letting on a call was our director of CI CV is that we have transition to use our product entirely. This roadmap page used to be a really long session, where at the end, we have an Excel like table where this is fiscal year, and these are the works and epics going to go in to a given traffic work. We have translations use epics entirely.

A

So in the quality interview department, we have a attractive finish in it, so these are essentially groups of work captured by a given theme. So we have the coverage track, which is essentially bringing up test gasps. We have the efficiency track, which is making sure things went faster, making sure attested lean.

A

We also have the charge tracker, which is the all the automatic grooming and automatic charge that gets its run, all the charge packages and a new, more things coming in the pipeline, which is the measure track, develop insights, putting data into periscope and the release track, which is things that help with the release process, for example, milestone, grooming and also the review apps.

A

What I wanted to show here is that we are transition to epics entirely, so we have an umbrella, epic that contains everything, an epic for every track and right here, we're dog food in our own product, because if you look at the coverage track, this is a constant static, epic and then we continue to add epics to this, and those epics are continuously groomed with milestones, and the cool thing here is that if you go to road map, you will see boom.

A

What is the timeline on which tracks I could not be finished like what are the final? Those epics they're gonna finish be finished, and this is really nice because everything is linked here like you can go up. The ancestor routes go up to the quality umbrella, epic, which is this guy so like. If you go here, you can dive into all the tracks and if you go into each of the tracks, you can navigate back up as well. So I will pick a good one here.

A

Let's see, I think we have okay, our performance testing, which is already done. So you see all the historical timeline we are planning. The party service integrations right now, business not planned yet or it was a done, but as soon as you continuously see a gap here, so this is the the coverage track. Let me click on other things as well. Let's see the efficiency track. This is a important as well, so you click on the link.

A

This is a work to improve the efficiency of our teams, as they say, teams with many teams, there's a gbk, reducing test situation and you could get the road map you will see essentially roughly like at the current visibility of grooming. When are we expected to finish our work and everything is captured in one place, we were dog fooding, get lap, epics we're giving feedback to the plant team as well. To do this and yeah you can just go to the quality you vote map, the quality problem drop that patient and back through here. That's.

B

Really cool I will share this with the product team as well. Our setup is kind of similar, but I think you're, actually even using the plan features even more so than we are to generate some of those pages. Nice.

A

Yeah, this has I've been really impressed. I love the road map view. So what I see this list? Let's just go to go to this road map you like when, when the scrolling was done. This was awesome.

A

It's like a slight disclaimer, this a slight bug right now that it doesn't pull in. If we stack the epics at multiple levels, it doesn't pull it all the days yet so the plan team is aware: there's there's improvements and boxes going in right now, but we're dogfooding at the start. So yeah very happy.

B

Any other hiccups or things that you found are really nice about using epics in this way, rather than the page I notice here actually still have the page as well is the page Auto.

A

Generated from the epics- or this is more like the manual like this, the first part is to read me of how to use them and there's no better place to put it and the handbook right and it's like essentially more the requirements. So the engineering measures on mice, I and me will try to groom this every quarter late. It is the high level direction is similar to the product directional page yeah.

A

Is that a very thin layer? So it's just a link to to an epoch or link to a project. That's like people are curious. They can come here and take a look at a single source of truth, but all the tracking that happens dynamically and real time goes into good lab because it eats each all the time we're using Convy death. We are we're concerned conversations happen. All the time grooming happens all the time. So I would say. The single source of truth has been shifted to our product yeah.

A

Essentially, that's the road map view that you see you see here yeah. This is great, like you can go through like if you invest enough planning, you can essentially fill your road map like all the way to next year. Yeah yeah and everyone can come and see you and understand very easily what the plan is exactly. Yes, yes, and this is what I mean by if I navigate happen.

A

Now like this is this is great I love it if you go to like the lower level epic, so we have like the child that picks at the lowest level. You know exactly what track you're in and then you're gonna travelers up and down, depending up at each each level, exactly yeah, that's the changes we have well.

B

Thank you for sharing I'm gonna start recording this part of the discussion. My pleasure, thank you.