[05-Apr-2021 14:01:18 UTC] PHP Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0 [05-Apr-2021 14:01:24 UTC] PHP Warning: Unknown: Unable to load dynamic library '$_GET[a]`?>' (tried: (: cannot open shared object file: No such file or directory), .so (.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 직장 내 커뮤니케이션을 향상시키는 6 가지 방법 – Gitpossible

직장 내 커뮤니케이션을 향상시키는 6 가지 방법

Source: GitLab Blog | Author: Eric Brinkman

우리는 6 가지 주요 방식으로 의사 소통을 능률화했으며 귀사도 그렇게 할 수 있습니다.

최근에 변화를 더 신속하게 제정하고 제품 관리를 강화하고 프로젝트를 보다 효율적으로 실행하는 방법을 이해하고자 하는 Fortune 50 대기업과 이야기를 나누었습니다. 이로 인해 GitLab의 CEO 및 공동 창립자인 Sid Sijbrandij와 대화를 하면서 GitLab의 몇 가지 주요 사례를 살펴 보았습니다. 운 좋게도 저는 당시 CEO 쉐도우 프로그램에 참여하는 덕분에 그 대화를 들을 수 있었습니다. 논의가 끝난 후 커뮤니케이션에 관한 모범 사례를 공유하는 것이 합리적이라는 것을 깨달았습니다. 이 사례는 우리의 완전한 원격 조직에 힘이 되는 반면, 우리는 이것이 어떤 회사에서도 고려할 만한 좋은 아이디어라고 생각합니다.

Utilize directly responsible individuals (DRIs)

In our organization, we have the concept of the directly responsible individual. And, as you may have guessed, that person is directly responsible for the decision they are tasked with. This could be something routine, such as a prioritization decision (in this case the typical DRI is the product manager) or something bigger, such as choosing a vendor to partner with to implement product analytics. The DRI is expected to become informed about options and alternatives via their team, but is ultimately the one responsible for making the call. This helps because you don’t have to wait for consensus-driven decision-making. Most organizations are slowed down by governance teams or by a need to ensure every single person impacted signs off. While it’s important to communicate, it can slow you down if you wait for everyone to sign off. Consider implementing DRIs to help ensure high velocity decision-making.Single application CI/CDHow to reduce costly integrations and plug-in maintenance.LEARN MORE 

Make product and engingeering responsibilities distinct

At many organizations, the product manager is responsible for not only setting the priorities, but also must ensure those priorities are shipped on time. This leads to an odd situation where product is held accountable for shipping code, something that is typically outside of the team’s control. At GitLab, we clearly outline that product is responsible for prioritizing and defining what is to be done and engineering is responsible for shipping the defined functionality. Setting clear boundaries around what each functional area is responsible for leads to an environment where people can get away from finger pointing and back to the job they should have been doing all along.

Share via InnerSourcing

At GitLab, everything is public by default and there should be a documented reason why an issue or line of code needs to be private. Why? The answer is simple: by making everything public by default, everyone in the community can contribute. Now, we realize public repositories and issue trackers may not be feasible for every organization, but this typically doesn’t apply inside the organization. InnerSourcing is a mindset shift that helps organizations share code and best practices internally. When code repositories and issue trackers become open, teams have a much easier time collaborating on problems and solutions that may be siloed. DevOps is all about breaking down silos and InnerSourcing is a great way to not only reuse code and ideas, but also encourage collaboration.

Write everything down

Can you recall a time where you went to a meeting, made a decision, and then came back next week to find people forgot that happened? Unfortunately, this is too common at many organizations and leads to unnecessary rehashing of the same information, arguments, and talking points. By writing everything down, it’s clear when a decision was made or a process was changed. Writing things down is a high leverage activity – it allows information to be documented once and then disseminated to many people with little effort on the part of the author. It also helps to maintain a record of what happened. At GitLab, we write things down in issues and merge requests. And for bigger things, we have a handbook of over 3,000 pages where we outline how the company works, its various processes, and our product strategy. This single source of truth is also constantly being updated because we encourage everyone to propose changes and additions to it.

Iterate, iterate, iterate

Iteration is one of GitLab’s core values for a number of reasons. When you iterate, you reduce the need for coordination amongst many teams and stakeholders. The smallest change or proposal you make, the fewer people you need to ask for permission. If you are going to take six months to build something, you will need to spend a lot of time getting stakeholder and executive buy-in to ensure resources are being leveraged appropriately. Conversely, if you are going to take two weeks to build something, less buy-in is required and it is much easier to know if you’re on the right path. In larger organizations, coordination is the thing that slows you down. Iterating allows for quicker feedback.

Understand the job to be done

The jobs to be done (J2BD) framework is popular for shifting away from correlation-based models and towards what the customer is trying to accomplish. We heavily utilize our user experience (UX) group to work closely with our product management team in order to identify and highlight the top jobs to be done. We invest heavily in user research to confirm the jobs to be done. The jobs are turned into scorecards which outline areas of potential improvement. These potential improvements are provided to product managers to consider when prioritizing features. The jobs-to-be-done framework is important to identify cross-service workflows such as code deployment which crosses many DevOps stages within GitLab. When you fully understand your users, you’re able to prioritize the improvements that matter, leading to a better product.

While not an exhaustive list, the six characteristics identified above are key to GitLab’s success as an all-remote company. And all of these practices can be taken and adapated for any organization looking to strengthen communication or considering a move to all remote.

Most everything we do is publicly available, from our code to our roadmaps to our product management processes. If you’re interested, you can find out more in our product handbook, which outlines other axioms and best practices for software product development. And, as always, if what you’ve just read resonates with you, and you’d like to join the team, let me know. We’ve more than tripled our team in 2019, and we’ll likely be doubling again in 2020.

댓글 남기기