GitLab TeamOps, 27 Jan 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Measuring the Uptake and Impact of TeamOps on an Organization

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

In this short, video I'm going to be talking about measuring team Ops and how we measure the uptake of Team Ops by team members and also the impact that tmops has on organizational results.

A

One of the guiding principles of Team Ops is measurement Clarity and it focuses on transparent measurements measure results, not hours, prioritize due dates over scope and iteration I'm, going to talk about how we can apply this guiding principle of measurement Clarity to the actual measurement of how well team Ops is working at an organization.

A

First I'll talk about the uptake, so the uptake is our team members actually using tmos across the organization, it's important to remember, transparent measurements. When we're talking about uptake. So we can get a clear idea of what divisions and departments are using team Ops to the most of its potential and also which teams and departments might be struggling with applying team-ups.

A

A couple of ideas for taking transparent measurements of uptake of tmops include engagement, surveys with questions that are specific to each team, Ops guiding principle and also hosting psychologically safe focus groups to discuss where team Ops is and isn't working. It's important to focus both these questions and the discussions on each of the guiding principles, because even organizations that are doing team Ops really well will have team members across the organization who might not even know how they could apply these guiding principles to their work.

A

So, as we are using transparent measurements to measure uptake of Team Ops we're also educating team members on how they can better apply it to their work.

A

Second, it's important to measure the impact that team Ops is having on the results that an organization is reaching here. It's important that we focus on measuring results and not ours. Two examples that we can use to measure the impact of t-mumps on results by an organization include transparent discussions that exemplify team Ops guiding principles at gitlab. This might look like discussions that are happening on merge requests or issues where we are talking about the way that the work is being done rather than the result that was achieved.

A

Another example could be having a retrospective question that also addresses how results were achieved in addition to what results were achieved so taking time with each result achieved to talk about not only the result that the team was able to reach, but how the team got. There is a really great way to both discuss and measure the impact of tmops.

A

It's really important and kind of a fun way to practice team Ops when we use the guiding principle of measurement Clarity to measure both the uptake and the impact of Team Ops at an organization.