GitLab Plan Stage, 10 Jan 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Child epics in GitLab 11.7

Description

Documentation: https://docs.gitlab.com/ee/user/group/epics/

Upcoming improvements for child epics: https://gitlab.com/groups/gitlab-org/-/epics/312

Agile portfolio management vision: https://gitlab.com/groups/gitlab-org/-/epics/667

A

When my name is Victor Wu and I'm, a product manager here at gitlab and today, I wanted to share with you a really awesome cool new feature coming gitlab 11.7 called child epics. So good Lab is a single application for the complete DevOps lifecycle. As you see on the screen here, and one of those stages in the life cycle is the planned stage, and so the planned stage includes a bunch of product categories and one of those product categories is called.

A

What we have here add your portfolio management and within that particular product category. We have something really cool called an epic, so you might have seen this already if you've been using epics already in kit lab. So this is what a typical epic looks like inside get lab, but what we're shipping in get lab, 11.7 and just to preface that 11.7 is coming in January 22nd 2019, as you see when I'm recording here is January 10.

A

So just in a in in over a week's time, I will be sharing this feature we'll be shipping it as part of Gil lab 11.7. So back to this epic, as you can see, this is a big that you've seen and probably used already if you've been using git lab. But one thing that might be a little bit different that you haven't noticed on this screen is that there's a new category or a new section here called epics, and so before.

A

We've always had issues that you've gotten attached to a particular epic, and now you can attach also epics to epic. So that's what we mean by child epics. Essentially, you can attach epics unto epics or nested epics or sub ethics. However, you want to call them so the example I'll give here is actually I'm using production data on kill lab comm. So this is actually. This is actually we real data because we're a transparent company I can share this information with everybody on the Internet, and so what's really funny.

A

Is that I'm actually using the epic that I'm demoing right now? This is like the actual demo, the epic that we're actually tracking this particular feature and so, for example, more broadly we're calling this feature flexible, work, breakdown, structure with epic relationships. You know one of those epic relationships is the child, epic, and so we've done all this work.

A

We've done attach an epic to an epic as part of 11.7, as you can see, and what we want to do is we want to do additional work in the future, so you see that we're scoping out additional work, but another thing we want to do is some of the additional work instead of just individual issues as part of this epic, why don't we group all those additional issues into another epic and put that epic as a sub epic of this epic?

A

So if that's confusing I'll just show you what I mean so right here, I have another epic already scoped out with two additional issues: I have viewing epic relationships and epics and roadmaps, so my first epic is about creating the structure and myself. A second epic is about visualizing that, whether it's using you know a tree structure or using a row map structure and so on and so forth. So I'm gonna take this particular epic. You see on the screen 6:44 and make it a child epic of three one.

A

Two and all I have to do is copy. This link here, which I've done and I'm just going to click here. Paste and click add, and there you go now. This epic is a child epic of three one. Two and what's really cool is as I refresh here. You can see that on this particular epic, the parent is also shown in the sidebar here. So you can click here to go the parent and that will bring you to this particular epic, and so you can see also from this epic. Now you have a child.

A

So that's all really nice and cool and fine. But what's really awesome, is how you can actually leverage child epics. So what I've shown here is a way to have a sub structure to track work that you're doing in your particular team or your organization, or maybe across multiple teams, but what you can also use epics for is you know, initiatives, strategic themes and and so on and so forth, and so that's what actually we're doing at gitlab so ideal that we have what we're calling category epics.

A

So we we make these epics and we would put this label called product category and we surf this. These links and other pages such as here to find to organize the guild lab product, and so we have what we're calling epic a product category, epic vision, epics I, know that's a mouthful, but essentially we're using these objects to represent vision, our vision for that particular product category. So these are not necessarily deliverable work or planned work, but it's a page that represents the strategy, dis initiative. So it's it's long.

A

It's a long, long, lasting initiative, and so it would make sense if this is initiative that can I can also attach relevant epics to that initiative and I'm gonna do exactly that here. So I'm gonna take my work breakdown structure without epic relationships, epic I'm gonna copy that here and I'm gonna paste it here exactly there and voila right there now I. Can anybody that comes to this plan category vision for agile portfolio management? They can see. Oh, what are the relevant epics for that particular category vision.

A

So I've just started working on this particular category vision, page of this epic and so in the future, I'm going to add more topics that are relevant to the agile portfolio management product category, and so what's really helpful is then you know a customer or user or whoever's watching this video. If you are doing so and then you click on the link that I'm gonna, you know put in the YouTube description later, you can come to this particular page. You can click here.

A

You can now see this particular epic and you can dig down further and so on and so forth. You can go all the way down to the particular issue and you can see comments and designs and so on and so forth. So you can see for this particular issue. We've already have a lot of comments and you know description and as a user, you can go in and start you know commenting, and so so that's great. So so!

A

Actually that's what I'm gonna do next is to invite all of you watching this video to comment on these ideas. So what you've seen today, you know it looks very simple and it's that's how we roll like gitlab, we ship, the smallest iteration that we can think of that we think would be useful, and then we want to build out this further.

A

So if you actually click on this epic, you can see some of the great really fun things where we're thinking about and, for example, that's what I just showed you here, how we're gonna incorporate this sub structure, these child epics as a concept in the roadmap view in the future. We already have designs and we would love your back. So do please participate and one thing I wanted to end up with is the roadmap view itself looks just the same as before, and it looks absolutely beautiful.

A

You can see that you know you have the epochs here. You can see the the road map bars from the left to the right, and so that's unchanged with child epochs. You can still see all your epochs in the start, data and days on the road Matthew. But again, as I mentioned earlier, we're planning to improve that and you can actually see the substructure in the road map view in the future. So thanks for watching and yeah click on the links in the description talk to you next time. Bye now.