GitLab Enablement Staff, 26 Jul 2019

Previous Meeting

⏯

youtube image

►

From YouTube: enablement staff meeting 2019 07 26

Description

2019-07-26 Enablement Staff Meeting

A

We'll just start over chatting, that's fine! That's.

B

B

Okay, I think each team probably is a different name in their domains and the practice or so, let's be flexible in the processes. Whatever works for the team, specifically I'm open to that concept, but- and some I didn't note there- some very high-level principles we may want to align on that like we need to be more agile that also help us to boost our productivity. So, let's make sure that we always encourage folks to chop the items to smaller pieces.

B

Make us more Amar's make small more issues, so we can continuous continuously adjusted our schedule and our priority or make changes as there's more items. That will help us to do that, and also speaking of the throughput and from Eric from Eric from Christopher. They encourage small pieces as more Amar's because of the agile practice. That's a better practice of agile, so yeah somewhere high level principles, let's be less aligned up, but exactly the operational practices approaches. So we can stay flexible if needed.

A

Yeah I'm super interested to hear how the Kanban experiment goes with Rachel's team. Something had done in the past with other teams and I honestly memory team might be well-suited for a Kanban style approach as well, especially now.

C

Well, we're one week in and so far so good that I'll have a much more detailed report back after a couple. Noise.

B

Okay and also today's Friday, so we next week we have three working days, probably or two to wrap up the quarter, so encourage people to do the small I Mars.

B

Yeah: okay, if this item.

A

Cool like so, we have the follow-up meetings in we'll figure out a cadence and action items from the meetings yeah.

B

Cool moving on to my item next, one after the interviewer very striking, so I actually had a Wang once with some engineers to follow up and also I already noticed that the participation of the section week in review is kind of low. So I want to get opinions from everyone. Do we want to continue this or roll out the information to the engineering working, our I think open to opinions just to ask everybody's feeling, and what do you think I think.

D

We should target everything to the engineering wir to get everyone's participation a little bit tighter on there and move away from the different section ones where people are kind of segmented away. That's just my right right or wrong. It's just kind of where, where I'm at with the yeah.

B

Yeah one little evidence I collected is and some folks who said they they are not sure where to put what it's just that they have some topic, they're, not sure if they should be put in a section or in engineering or balls. So that's some questions of people, folks that had in the past, I.

C

Also echo Steven's feeling there about rather putting focus on the engineering we can review.

A

C

A

I think we can go to engineer weekend review, maybe instead of the way it is now or it's kind of almost wild. Let's just put it in things where you want have it organized by sections would be a better way to go that way, I mean that kind of melds, the two together anyway, yeah.

C

I think having some organization on that would be great, because it also focuses the reader a bit more at the moment feels like a long list of things you need to read through, and there might be certain ones that are more important to different readers.

B

Actually, I also have another suggestions, so the IT officer is of working on creating email alias, so we will have our email alias for the entire section, so I'm seeking doing this way, everybody contributed to the weekly engineering review. I will pull down our section contents and send the email every Monday to the to our sections. So if people don't read that they get the email in their box, so they can read that that's more handy, that's probably what I can do from my my perspective.

B

Is that know a good approach.

C

D

I think I'm good with that I think generally just to round this one out, I think we're saying that, let's, let's move towards the engineering, get some structure around it. I get less like an Easter egg hunt and more like I'm reading about specific okay, specific sections are a more targeted message. I think I like how rich old legend it we.

A

Should put Easter eggs in there right.

D

Christopher, you still are the master of that.

A

Make him acknowledge in the slack channels.

D

Christopher, remember him doing that in the past I've done.

A

That before too, it's pretty entertaining.

B

Okay, let's experiment that I will also notify in the channel that we will put a halt or stop section. I mean.

A

Worst case, if nobody else want to do it by section, we can always do our own just say enable bit section and put our notes in there. Yeah.

D

B

Okay, a Camille, you haven't expressed your opinion. Well, what do you think I I.

E

Think that like, if we don't see the participation like there is no reason like to continue that, and that's basically like rephrase what everyone has said. Let's try to like just engineering week in your review, which seems like much whiter.

E

My my only I think is like I would like to see more like find ranking of each other while doing the work, because I just don't see this a lot. I, don't see that we utilize fine standard extensively and I think that we we can appreciate a lot of what other people thought, maybe like reviewing.

C

E

Or like what comments they are pushing, so this would be like an ass nice thought that was part of this, an ignorant weak in a ravine about like it, was also not utilized that healthy anyway, so and I wonder, maybe like by giving example by myself putting more funks, good and I wielders to also each other. More often soon,.

D

I agree, I'm, sorry, no go ahead, I was gonna, say, I, agree like I, remember. Even when I three months ago, when I started, there was just more traffic in the bank's channel and more just you know, people thanking other folks for for work and it feels like we probably could be fed up a little bit or get that more of a focus back on that.

A

Yeah agreed so um I totally agree, I'm trying to figure out how we can get that funneled into this dock. It seems like the enablement week in review was shared more widely with everybody, whereas the engineering week in review seems like it's more targeted towards engineering managers or as it shared out to everybody. So anybody can input. I. Think.

D

It's supposed to be anybody, that's in the engineering group, okay, I, think I think the snag comes in that we've got folks who start working at get lab, who have trouble getting in the engineering group or there's a long delay. Sean I think you're, probably aware of this to that and what happens is like they don't get invited to the vpe office hours. They don't get invited to some of the other. You.

C

B

D

Don't their visibility is just less until that they get added to that group which I think it'd be nice? You know people got on board and they right away. They saw like the Week in Review and stuff like that at least some of the higher level stuff to me.

B

We also talked about like open up this meeting to I mean in white I already do to participate or sold. Turning out the or another meeting to turn on the meeting to be a communication, channel I think that's too heavy weight and all the folks that won't be able to do I. My.

D

Groups anti sink and for stuff like the Hat, okay,.

B

Let's kill that idea.

D

B

D

Be harsh I'm just saying like.

B

Oh, it makes that.

E

D

Let's, let's all go to this meeting every next day and yeah I, don't know it's yeah. That's I like to let's take some baby steps on I, think I'm, condensing the some of the stuff we're doing now and targeting the we can review the engineering we can review and then from there we can. You know maybe turn it up. Okay,.

B

That's I'm not going to explicitly kill the section wicking are we are engineer, managers weekend completion complete, we can continue to contribute there. I will start of sending out the email by you know collating putting down the information from postal engineering and in the section working our W Week in Review, every Monday, so we'll see how that works and collect feedbacks from the engineers. If you have one wise, I'll appreciate it, talk to talk to other engineers collect the feedbacks of what works best for them with.

B

Basically, this is for everyone to improve the communication, keep everyone to the same page. What was happening if they don't find this information is beneficial.

B

We probably can stop it. Yeah, there's no point but I. My personally things think that the information helps us to get a job done more efficiently more effectively, because you know what other people are working on can take benefits from that.

B

So uh I'll start doing monthly emails and see how that helps. But we'll see we'll continue to see the section wiki in review, so you don't have to duplicate the information put on the to Doc's. If you put on one put in one place, don't have to put in another place, I will pull them into the into the email.

B

A

In the engineering we can review, are we just gonna go by section then I'll just put I can enablement section in there and maybe a thanks some bullet. So we can organize all of our information in that way. I think.

B

That's a good idea, I think that makes clear our whole section is put together. So it's not spread it all wrong. I'm.

A

Gonna put it in there now before we forget that three is called enablement or enablement section.

B

C

B

Enablement section yeah.

B

Cool cool, okay, okay, our cue to okay, ours. Please great your achievement signed by an early August. We shall conclude those those issues and great achievements by percentage. That's a grating way. We do here. You know development or engineering, okay and, of course, QE. Okay, ours, I really already stopped out. We try and having a checked ritual I, didn't check, sure I, don't know yours, but I saw steel and.

C

B

Step out, don't feel the details next week, so I think by end of next week. Next Friday we shall have the details fleshed out at this point just to stamp out Europe OPR issues there, one ish well, ok, ry issue, so it's been always like that yeah, that's a huzzah and then last one. My item is the killer comida, so I shared dig there.

B

If you, your team members, are interested, please go ahead to nominating your key members there, because is going faster. Actually, all is only 60. Kids were six six three in New York three in Linda. If you have someone interested just nominate as soon as possible, also shown already nominate one so yeah the media says whoever is interested.

B

The criteria is a sixty six months or above and close to the two location, so it doesn't have to be across the world.

D

Travel so close means the same continent is whatever Lew use.

B

Do your due diligence.

D

My due diligence, they.

B

Do say is 15 miles, 30 miles, 30 miles or Hyderabad a thousand miles or.

E

B

Yeah, so that's the basic of the two criteria.

B

Yeah, that's my last I know how about I'm pretty much at a time. Yep cool. Next one musicians, a little coffee chat. It's.

A

Making sure we record decisions made, oh.

B

Yeah, okay, so we finished our topics today. Anything else there's.

D

Two issues: I, don't want to like open too much. You know, make a big deal, but the labeling stuff I've been keeping track of that it looks like the BA is continuing to run, but the old labeling and the new labeling, the the numbers aren't lined up quite yet so I'm, assuming that it's not finished.

B

Yeah, oh yeah, you reminded me I, have a question: if we pull the, we collected a throughput data which Charter is correct or shall we do shall we do Plus this chart cross heart, I'd.

D

Say the old label seems to be more consistent: the new label, the the new labels, don't Matt one-for-one, which I think is what the bot is supposed to do- is go through and find all the old team labels and then add the group, the corresponding group label. So at some point the mr should line up so.

B

That means the buddy.

D

Knows they don't, but they don't yet so.

B

That means the throughput data by end of this mod can be off, I mean I, think.

D

Though I think the whole, since the old labels aren't being removed by the bots and I, wasn't sure about this until I until it actually run and in migrated, you know, you know, done its job. The old labels are still around. So as long as your team is still using the old labels, then the old insight stuff is correct. Okay, oh the discrepancy yeah I'm, seeing on the new, the new labels aren't fully populated. Yet, okay.

B

I'll check out our reference, the old labels cool. Thank you. That's it have a good day. Everyone goodbye yeah.