Commit f58f4d60 authored by Eric Johnson's avatar Eric Johnson

Tightening up terminology a bit

* Cross-functional -> devops stage group
* Developer -> Engineer
parent a46f1a3b
Pipeline #42605193 passed with stages
in 21 minutes and 43 seconds
......@@ -11,17 +11,17 @@ ee_cta: false
twitter_text: "Here's an inside look at the new cross-functional groups at @gitlab"
---
Hello world, meet the GitLab Configure group! They’re the folks hard at work improving [Auto DevOps](https://docs.gitlab.com/ee/topics/autodevops/), the [Kubernetes integration](https://docs.gitlab.com/ee/user/project/clusters/), and all the related applications on GitLab. They, like the rest of the GitLab engineering organization, recently changed how they work together when they split up into brand new cross-functional groups according to [product area](/handbook/product/categories/). Each working unit contains a product manager, UX designer, and several developers. They still belong to [teams](/company/team/structure/#team-and-team-members) with others usually in their same role, but they work together as a [group dedicated to a stage](/company/team/structure/#stage-groups) of the product lifecycle.
Hello world, meet the GitLab Configure group! They’re the folks hard at work improving [Auto DevOps](https://docs.gitlab.com/ee/topics/autodevops/), the [Kubernetes integration](https://docs.gitlab.com/ee/user/project/clusters/), and all the related applications on GitLab. They, like the rest of the GitLab engineering function, recently changed how they work together when we split up into devops stage groups according to [product area](/handbook/product/categories/). Each group contains a product manager, UX designer, several engineers, and other contributors. They still belong to [teams](/company/team/structure/#team-and-team-members) with others usually in their same role, but they work together as a [group dedicated to a stage](/company/team/structure/#stage-groups) of the product lifecycle.
![meet the configure group](/images/blogimages/configure-team.jpg){: .shadow.medium.center}
So far, Configure group members say this has helped them stay focused and connected. Staff UX Designer Taurie Davis explains that while she used to have to switch gears and spend time getting caught up on different product areas, she can now hone in on finding solutions to familiar problems. Having a fixed group of collaborators also promotes shared learning, because they’re working together on the same issues at the same time. Product Manager Daniel Gruesso also sees benefits in having a dedicated set of people for each product area; they enjoy more latitude and no longer face as much competition for getting their work prioritized. These are all benefits of [stable counterparts](/handbook/leadership/#stable-counterparts), or people in different functions who routinely work together, easing communication to avoid conflict and the [downsides of a matrix organization](/handbook/leadership/#no-matrix-organization).
So far, Configure group members say this has helped them stay focused and connected. Staff UX Designer Taurie Davis explains that while she used to have to switch gears and spend time getting caught up on different product areas, she can now hone in on finding solutions to familiar problems. Having a stable group of collaborators also promotes shared learning, because they’re working together on the same issues at the same time. Product Manager Daniel Gruesso also sees benefits in having a dedicated set of people for each product area; they enjoy more latitude and no longer face as much competition for getting their work prioritized. These are all benefits of [stable counterparts](/handbook/leadership/#stable-counterparts), or people in different functions, departments, or teams who routinely work together, easing communication to avoid conflict and the [downsides of a matrix organization](/handbook/leadership/#no-matrix-organization).
<%= partial "includes/blog/content-newsletter-cta", locals: { variant: "b" } %>
Some of the challenges that drove this change have been echoed in our user research, with cross-group communication a common and recurring roadblock. In our [2018 Global Developer Report](/developer-survey/2018/), a quarter of developers indicated that they feel siloed, and lack visibility into what their colleagues in operations, product, and security are working on.
Some of the challenges that drove this change have been echoed in our user research, with cross-group communication a common and recurring roadblock. In our [2018 Global Developer Report](/developer-survey/2018/), a quarter of engineers indicated that they feel siloed, and lack visibility into what their colleagues in operations, product, and security are working on.
This was reinforced in recent interviews by our UX research team, where many [developers](https://drive.google.com/file/d/1EVrjVcgIBbuNf4Gwenajsiy6Wv9HsTJw/view) we spoke with said that they’re frustrated by changing requirements and scope creep, and pinpointed poor communication with and empathy for other teams as the cause. Their colleagues in [operations roles](https://drive.google.com/file/d/1A5mSNoPJydjcWKE4rdO2287sjnABxGDA/view) face a similar challenge in convincing others to invest cycles in proactive work that can save them time and stress in the future. Although implementing cross-functional groups may seem like a big change, we’ve seen positive results and hope that sharing our experience may help others take the plunge.
This was reinforced in recent interviews by our UX research team, where many [developers](https://drive.google.com/file/d/1EVrjVcgIBbuNf4Gwenajsiy6Wv9HsTJw/view) we spoke with said that they’re frustrated by changing requirements and scope creep, and pinpointed poor communication with and empathy for other teams as the cause. Their colleagues in [operations roles](https://drive.google.com/file/d/1A5mSNoPJydjcWKE4rdO2287sjnABxGDA/view) face a similar challenge in convincing others to invest cycles in proactive work that can save them time and stress in the future. Although implementing stable groups may seem like a big change, we’ve seen positive results and hope that sharing our experience may help others take the plunge.
I recently caught up with a few members of the Configure group, read on for their perspectives on how it’s been going.
......@@ -29,9 +29,9 @@ I recently caught up with a few members of the Configure group, read on for thei
**Dylan:** Hi I'm [Dylan](/company/team/#DylanGriffith). I'm the [Backend Engineering Manager](/job-families/engineering/developer/#engineering-manager/) for the [Configure](/handbook/product/categories/) group.
**Thong:** I’m new here! I’m [Thong](/company/team/#thongkuah) and I'm a senior [developer](/job-families/engineering/developer/).
**Thong:** I’m new here! I’m [Thong](/company/team/#thongkuah) and I'm a senior [backend engineer](/job-families/engineering/backend-engineer/).
**Mayra:** I'm [Mayra](/company/team/#may_cabrera) and I'm a [developer](/job-families/engineering/developer/) for the Configure group.
**Mayra:** I'm [Mayra](/company/team/#may_cabrera) and I'm a [backend engineer](/job-families/engineering/backend-engineer/) for the Configure group.
**Taurie:** I'm [Taurie](/company/team/#tauried), the [UX designer](/job-families/engineering/ux-designer/) for the Configure group. I work closely with product and engineering to help shape the overall user experience of our products.
......@@ -39,7 +39,7 @@ I recently caught up with a few members of the Configure group, read on for thei
### In general, how do you think it's going so far?
**Dylan:** So far the cross functional group is working well. I believe that backend teams already were well focused on specific product areas, but I think the addition of focused UX and frontend engineers on our product area helps in a few ways. First, we know who to talk to about UX decisions, and the UX designer and frontend engineers have good context across the feature set and often have good insights based on this context. Backend engineers also get to collaborate and form better working relationships with UX and frontend, and as a consequence we communicate more effectively in general.
**Dylan:** So far the stable devops stage group is working well. I believe that backend teams already were well focused on specific product areas, but I think the addition of focused UX and frontend engineers on our product area helps in a few ways. First, we know who to talk to about UX decisions, and the UX designer and frontend engineers have good context across the feature set and often have good insights based on this context. Backend engineers also get to collaborate and form better working relationships with UX and frontend, and as a consequence we communicate more effectively in general.
### What are some of the big differences that arise from working with people in different roles, versus working more with people who share your background?
......@@ -87,7 +87,7 @@ We're focusing on making Auto DevOps clearer to users; making more decisions bas
### Anything else you want to share?
**Daniel:** We're always looking for [developers](https://about.gitlab.com/jobs/apply/?gh_jid=4055697002). Familiarity with Kubernetes and expertise with ruby will help you land an interview.
**Daniel:** We're always looking for [engineers](https://about.gitlab.com/jobs/apply/?gh_jid=4055697002). Familiarity with Kubernetes and expertise with ruby will help you land an interview.
**Dylan:** Try out [Auto DevOps](https://docs.gitlab.com/ee/topics/autodevops/) and don't be afraid to create issues for us if you run into trouble. We love hearing from our users!
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment