Elements of agile cooperation
- Self organization
- Focus on Customer
- Iterative cooperation
- Prioritization by added value
- Continual learning
- Focus on the next step
敏捷合作的要素
- 自我组织
- 以客户为中心
- 迭代式合作
- 按附加值排列优先次序
- 持续学习
- 专注于下一步工作
In my first article of the Agility in the Nutshell series, we dealt with agile values. This time I will write about agile principles.
在这一系列短文的第一篇文章中，我们讨论了敏捷价值观。现在，我们将探讨敏捷原则。
The agile manifesto contains 12 principles according to which agile software development should be done.
- Our highest priority is to satisfy the customer by early and continuous delivery of valuable software (products).
- Radical changes in requirements are welcome even late in requirements are welcome even late in the development process. Agile processes use changes for the competitive advantage of the customer.
- Deliver working software (products) regularly within a few weeks or months, preferring the shorter period.
- Experts and developers must work together daily during the project.
- Set up projects around motivated individuals. Give them the environment and support they need and trust that they will get the job done.
- The most efficient and effective method of communicating information to and within a development team is face-to-face discussion.
- Functioning software is the most critical measure of progress.
- Agile processes promote sustainable development. Clients, developers and users should be able to maintain an even pace for an unlimited period.
- Constant attention to technical excellence and good design promotes agility.
- Simplicity -the kind of maximizing the amount of work not done – essential.
- Self-organised teams create the best architectures, requirements and designs.
- At regular intervals, the team reflects on how it can become more effective and adapts its behaviour accordingly.
敏捷宣言包含了12条原则，应该根据这些原则来进行敏捷软件的开发。
- 我们的首要任务是通过尽早和持续交付有价值的软件（产品）来满足客户需求。
- 即使在开发过程的后期，客户要求的巨大改动也是受欢迎的。敏捷过程将变化作为客户的竞争优势。
- 在几周或几个月内定期交付工作软件（产品），倾向于时间周期越短越好。
- 在项目期间，专家和开发人员必须每天一起工作。
- 围绕有积极性的个人设立项目。给他们需要的环境和支持，并相信他们能完成任务。
- 与开发团队之间以及开发团队内部的信息沟通的最有效的方法是面对面的讨论。
- 能够顺畅运行的软件是衡量进展的最关键标准。
- 敏捷过程促进可持续发展。客户、开发者和用户应该能够在无上限的时间内保持均匀的发展节奏。
- 不断关注技术的卓越性和良好的设计，有助于促进敏捷性。
- 简化—-最大限度地减少那种未完成的工作量—至关重要。
- 自我组织的团队创造了最好的架构、需求和设计。
- 每隔一段时间，团队就会反思如何才能变得更有效，并相应地调整其行为。
If we consider agile work also apart from pure software development, we recommend considering the following principles for method-free agile work:
如果我们考虑把敏捷工作从纯粹的软件开发中分离出来，我们建议考虑以下的“无方法”的敏捷工作的原则。
Self-organisation: Cooperation in teams is self-organised as far as possible – so that the experts can do their job in the best possible way.
自我组织：团队中的合作尽可能是自我组织的—这样专家就能以最佳方式完成他们的工作。
Iterative approach: The cooperation in the team is iterative according to the Plan-Do-Check-Act-Review cycle.
迭代的方法：团队中的合作是按照 “计划–执行–检查–行动—回顾 “的周期反复进行的。
Continuous learning: Result and process reviews enable the team to learn and develop further.
持续学习：结果和过程回顾使团队能够进一步学习和发展。
Customer in focus: Everything the team produces happens with the customer in mind. You should not do what you think is the best, but rather to create in the best possible way for the customer.
以客户为中心：团队产出的一切都以客户为中心。你不应该做你认为最好的事情，而是要以最好的方式为客户创造。
Prioritization according to added value: Actions that are set are prioritised according to the added value for the customer.
根据附加值确定优先次序：设定的行动是根据对客户的附加值进行优先排序的。
Focus on the next stage: Instead of long-term planning, the focus is always on the next step.
You can learn more about this in our training Cooperation in agile teams.
关注下一阶段：重点不是长期规划，而是始终关注下一步骤。
你可以在我们的培训中，了解更多关于敏捷团队的合作。