mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
translated
This commit is contained in:
geekpi
parent
4362af9137
commit
d74396e39b
@ -1,60 +0,0 @@
|
|||||||
[#]: subject: "5 open source principles that help organizational governance"
|
|
||||||
[#]: via: "https://opensource.com/article/23/4/open-source-principals-organizational-governance"
|
|
||||||
[#]: author: "John E. Picozzi https://opensource.com/users/johnpicozzi"
|
|
||||||
[#]: collector: "lkxed"
|
|
||||||
[#]: translator: "geekpi"
|
|
||||||
[#]: reviewer: " "
|
|
||||||
[#]: publisher: " "
|
|
||||||
[#]: url: " "
|
|
||||||
|
|
||||||
5 open source principles that help organizational governance
|
|
||||||
======
|
|
||||||
|
|
||||||
Throughout my career, I have been fortunate to work with many organizations of various sizes on a variety of projects. All of these projects had open source software at their core, and most contributed what they could back to the open source community. I recently worked on a greenfield project using open source software within a large organization. After the MVP phase of the project, the organization's leadership was interested in learning what led to project success and how they could apply it to other teams across the organization. Upon reflection, I saw similarities between our team's way of working and open source communities and development. The following are some insights into how open source principles can help organizations save money, [reduce technical debt][1], and bust internal silos.
|
|
||||||
|
|
||||||
### 1. Better spent budgets
|
|
||||||
|
|
||||||
I recently delivered a talk on [Headless Omni-Channel Web Platforms][2] at the Florida Drupal Camp. One of the key benefits highlighted in the presentation was how to save money by implementing this web platform. The idea comes from open source software development. Different groups within an organization can use their budget to contribute features or functionality to a core software or platform. They can also team up with other groups to pool dollars for more complex features. When the feature development is done, it's added to the core software or platform and available for all. Using this open source principle can provide mutual benefits to groups within an organization. Allowing the sharing of features and functionality and collectively benefiting from each other's spending can improve the software or platform.
|
|
||||||
|
|
||||||
Another aspect of this approach that saves money and allows for continuous improvement is the ability to test and develop a feature once and reuse it repeatedly. We frequently see this when creating a web platform that uses a component-based design system as a starting point. Users of the platform can reuse components or features developed by other users. Often, these have already been tested in numerous ways, such as user experience, accessibility, and even security testing.
|
|
||||||
|
|
||||||
This simple idea faces opposition in many organizations as individual groups covet and protect budgets. Groups don't want to give up their budgets to support the core software or platform. In some cases, differences in priority and opinion add to siloing in many institutions.
|
|
||||||
|
|
||||||
### 2. Reduce technical debt
|
|
||||||
|
|
||||||
Many organizations strive to reduce technical debt. Implementing a comprehensive core software or platform and using open source principles can help reduce technical debt. This happens by allowing development teams to think fully about how a feature impacts not just the group building it but the wider organization. This, plus collaboration with other groups within an organization, can help reduce the need for rebuilding or adding functionality in the future.
|
|
||||||
|
|
||||||
Sometimes organizations struggle with this type of collaboration and thinking because of internal competitiveness. Some companies foster a culture where being the first to build a feature or come up with an idea is rewarded. This can lead to groups not working together or sharing ideas, fostering silos within the organization and greatly hindering innovation.
|
|
||||||
|
|
||||||
### 3. Faster time to market
|
|
||||||
|
|
||||||
One of the terms I hear frequently is "Faster time to market." Everyone wants to get their thing out quicker and easier. This is often a benefit of a core software or platform, as internal groups can reuse existing, tested, and proven features and functionality instead of building their own from scratch. If your group is starting a project, and it could start from 80% complete instead of 0% complete, would you do it? I'm thinking yes. Now pile on the superhero feeling of adding needed functionality for other users. It's a win-win!
|
|
||||||
|
|
||||||
### 4. Release excitement
|
|
||||||
|
|
||||||
Another great open source principle that can help your organization is a release schedule that builds excitement. When your organization implements a core software or platform, users are invested in when updates come out. A release schedule and roadmap can communicate this to them. These two tools can help users to get excited about new features and plan their own roadmaps accordingly. It also helps build appreciation for other teams and pride for the teams building new features. This can unify an organization and allow for an organizational sense of teamwork and accomplishment while providing structure and a plan for the future.
|
|
||||||
|
|
||||||
### 5. A core team and governance
|
|
||||||
|
|
||||||
I have found you need two key items to overcome the above-noted obstacles and successfully apply open source principles within your organization. These are: A core team and solid organizational governance. A core team will allow for one group to maintain and manage your organization's core software or platform. It will support the solution and ensure new features and functionality are added wisely. This team can help to reduce the cost to internal teams and inform groups of roadmap features. The core team needs to be supported by strong organizational governance. This governance will provide groups within the organization with a common direction and organizational support to succeed. This organizational governance can mimic open source governance and principles in several ways. The most basic and highest level principle is community and the idea of working together toward a common goal.
|
|
||||||
|
|
||||||
### Open leadership
|
|
||||||
|
|
||||||
Adopting organizational governance based on [open source principles][3] can lead your organization to reduce cost, lower technical debt, increase team collaboration, foster innovation, and, above all, propel your organization forward together.
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: https://opensource.com/article/23/4/open-source-principals-organizational-governance
|
|
||||||
|
|
||||||
作者：[John E. Picozzi][a]
|
|
||||||
选题：[lkxed][b]
|
|
||||||
译者：[译者ID](https://github.com/译者ID)
|
|
||||||
校对：[校对者ID](https://github.com/校对者ID)
|
|
||||||
|
|
||||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
|
||||||
|
|
||||||
[a]: https://opensource.com/users/johnpicozzi
|
|
||||||
[b]: https://github.com/lkxed/
|
|
||||||
[1]: https://enterprisersproject.com/article/2020/6/technical-debt-explained-plain-english?intcmp=7013a000002qLH8AAM
|
|
||||||
[2]: https://noti.st/johnpicozzi/thgcPs/think-locally-build-globally-how-drupal-is-powering-headless-omni-channel-web-platforms
|
|
||||||
[3]: https://opensource.com/article/23/4/open-leadership-through-change
|
|
||||||
@ -0,0 +1,60 @@
|
|||||||
|
[#]: subject: "5 open source principles that help organizational governance"
|
||||||
|
[#]: via: "https://opensource.com/article/23/4/open-source-principals-organizational-governance"
|
||||||
|
[#]: author: "John E. Picozzi https://opensource.com/users/johnpicozzi"
|
||||||
|
[#]: collector: "lkxed"
|
||||||
|
[#]: translator: "geekpi"
|
||||||
|
[#]: reviewer: " "
|
||||||
|
[#]: publisher: " "
|
||||||
|
[#]: url: " "
|
||||||
|
|
||||||
|
有助于组织治理的 5 项开源原则
|
||||||
|
======
|
||||||
|
|
||||||
|
在我的职业生涯中，我很幸运地与许多不同规模的组织在各种项目上合作。所有这些项目的核心都是开源软件，而且大多数人都对开源社区做出了力所能及的回报。我最近在一个大型组织内从事一个使用开源软件的绿地项目。在项目的 MVP 阶段结束后，该组织的领导层很想知道是什么导致了项目的成功，以及他们如何将其应用到整个组织的其他团队中。经过思考，我发现我们团队的工作方式与开源社区和开发之间有相似之处。以下是对开源原则如何帮助组织节省资金、[减少技术债务][1]和打破内部孤岛的一些见解。
|
||||||
|
|
||||||
|
### 1. 更好地使用预算
|
||||||
|
|
||||||
|
我最近在佛罗里达 Drupal 营地发表了关于[无头全渠道网络平台][2]的演讲。演讲中强调的主要好处之一是如何通过实施这种网络平台来节省资金。这个想法来自于开源软件的开发。一个组织内的不同小组可以利用他们的预算来为一个核心软件或平台贡献特性或功能。他们还可以与其他小组合作，集中资金开发更复杂的功能。当功能开发完成后，它将被添加到核心软件或平台中，供所有人使用。使用这种开源原则可以为组织内的团体提供互利。允许共享特性和功能，并集体从彼此的支出中获益，可以改善软件或平台。
|
||||||
|
|
||||||
|
这种方法的另一个方面是可以节省开支，并允许持续改进，即对一个功能进行一次测试和开发，并重复使用它。在创建一个使用基于组件的设计系统作为起点的网络平台时，我们经常看到这种情况。该平台的用户可以重复使用其他用户开发的组件或功能。通常，这些都已经经过了无数次的测试，比如用户体验、可及性，甚至是安全测试。
|
||||||
|
|
||||||
|
这个简单的想法在许多组织中面临反对，因为个别团体觊觎和保护预算。团体不愿意放弃他们的预算来支持核心软件或平台。某些情况下，优先级和意见上的差异加剧了许多机构的孤岛化。
|
||||||
|
|
||||||
|
### 2. 减少技术债务
|
||||||
|
|
||||||
|
许多机构努力减少技术债务。实施一个全面的核心软件或平台并使用开源原则，可以帮助减少技术债务。这可以通过允许开发团队充分考虑一个功能不仅对建立它的小组，而且对更广泛的组织有什么影响。这一点，加上与组织内其他小组的合作，可以帮助减少未来重建或增加功能的需要。
|
||||||
|
|
||||||
|
有时，由于内部竞争，组织在这种合作和思考方面会有困难。一些公司培养了一种文化，即第一个建立一个功能或提出一个想法会得到奖励。这可能会导致各小组不一起工作或分享想法，在组织内形成孤岛，大大阻碍了创新。
|
||||||
|
|
||||||
|
### 3. 更快进入市场
|
||||||
|
|
||||||
|
我经常听到的一句话是“更快进入市场”。每个人都想更快、更容易地把他们的东西推出去。这通常是一个核心软件或平台的好处，因为内部团体可以重用现有的、经过测试和验证的特性和功能，而不是从头开始建立自己的功能。如果你的团队正在启动一个项目，而它可以从 80% 的完成度而不是 0% 的完成度开始，你会这样做吗？我想是的。现在再加上为其他用户增加所需功能的超级英雄感觉。这是一个双赢的结果！
|
||||||
|
|
||||||
|
### 4. 发布兴奋点
|
||||||
|
|
||||||
|
另一个可以帮助你的组织的伟大的开源原则是建立兴奋的发布时间表。当你的组织实施一个核心软件或平台时，用户会对更新的时间进行投资。一个发布时间表和路线图可以向他们传达这一点。这两个工具可以帮助用户对新功能感到兴奋，并相应地规划他们自己的路线图。这也有助于建立对其他团队的欣赏，以及对建立新功能的团队的自豪感。这可以统一一个组织，让组织有团队合作和成就感，同时提供结构和未来的计划。
|
||||||
|
|
||||||
|
### 5. 一个核心团队和管理
|
||||||
|
|
||||||
|
我发现你需要两个关键项目来克服上述障碍，并在你的组织内成功应用开源原则。这就是： 一个核心团队和坚实的组织管理。一个核心团队将允许一个小组来维护和管理你的组织的核心软件或平台。它将支持该解决方案，并确保明智地增加新的特性和功能。这个团队可以帮助减少内部团队的成本，并告知各组路线图的功能。核心团队需要得到强大的组织治理的支持。这种治理将为组织内的小组提供一个共同的方向和组织支持，以取得成功。这种组织治理可以在几个方面模仿开源的治理和原则。最基本和最高级别的原则是社区和为共同目标而工作的理念。
|
||||||
|
|
||||||
|
### 开放式领导
|
||||||
|
|
||||||
|
采用基于[开源原则][3]的组织治理可以引导你的组织降低成本，降低技术债务，增加团队协作，促进创新，最重要的是，推动你的组织共同前进。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://opensource.com/article/23/4/open-source-principals-organizational-governance
|
||||||
|
|
||||||
|
作者：[John E. Picozzi][a]
|
||||||
|
选题：[lkxed][b]
|
||||||
|
译者：[geekpi](https://github.com/geekpi)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://opensource.com/users/johnpicozzi
|
||||||
|
[b]: https://github.com/lkxed/
|
||||||
|
[1]: https://enterprisersproject.com/article/2020/6/technical-debt-explained-plain-english?intcmp=7013a000002qLH8AAM
|
||||||
|
[2]: https://noti.st/johnpicozzi/thgcPs/think-locally-build-globally-how-drupal-is-powering-headless-omni-channel-web-platforms
|
||||||
|
[3]: https://opensource.com/article/23/4/open-leadership-through-change
|
||||||
Loading…
Reference in New Issue
Block a user