敏捷宣言与十二原则

敏捷宣言

Individuals and interactions over processes and tools

个体和互动  高于  流程和工具

Working software over comprehensive documentation

工作的软件  高于  详尽的文档

Customer collaboration over contract negotiation

客户合作  高于  合同谈判

Responding to change over following a plan

相应变化  高于  遵循计划

敏捷十二原则

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

我们最重要的目标,是通过持续不断地及早交付有价值的软件使客户满意。

Welcome changing requirements,even late in development. Agile processes harness change for the customer’s competitive advantage.

欣然面对需求变化,即使在开发后期也一样。为了客户的竞争优势,敏捷过程掌控变化。

Deliver working software frequently, from a couple of weeks to a couple of mouths, with a preference for the shorter timescale.

要不断交付可用的软件,周期从几周到几个月不等,且越短越好。

Business people and developers must work together daily throughout the project.

项目过程中,业务人员和开发人员必须在一起工作。

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

要善于激励项目人员,给他们以所需要的环境和支持,并相信他们能够完成任务。

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

无论是团队内还是团队间,最有效的沟通方式是面对面地交谈。

Working software is the primary measure of progress.

可用的软件是衡量进度的主要指标。

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

敏捷过程倡导可持续的开发。项目方、开发人员和用户应该能够保持恒久稳定的进展速度。

Continuous attention to technical excellence and good design enhances agility.

对技术的精益求精以及对设计的不断完善将提升敏捷性。

Simplicity–the art of maximizing the amount of work not done–is essential.

要做到简洁,即尽最大可能减少不必要的工作。这是一门艺术。

The best architectures, requirements, and designs emerge from self-organizing teams.

最佳的架构、需求和设计出自组织团队。

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

团队要定期反应如何能够做到更有效,并相应地调整团队的行为。

评论(0)

发表评论

电子邮件地址不会被公开。 必填项已用*标注