敏捷開發Agile Software Development

文章目錄

• Principles behind the Agile Manifesto

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

 

敏捷式軟體開發 (Agile Software Development)宣言：

• 個體和互動     勝過 過程和工具
• 可以工作的軟體 勝過 面面俱到的文檔
• 客戶合作       勝過 合約談判
• 響應變化       勝過 遵循計劃

雖然右項也有價值，但是我們認為左項具有更大的價值

Principles behind the Agile Manifesto

We follow these principles:

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 months, with a preference to 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.

 

• 我們最優先要做的是通過儘早的、持續的交付有價值的軟體來使客戶滿意。
• 即使到了開發的後期，也歡迎改變需求。敏捷過程利用變化來為客戶創造競爭優勢。
• 經常性地交付可以工作的軟體，交付的間隔可以從幾個星期到幾個月，交付的時間間隔越短越好。
• 在整個項目開發期間，業務人員和開發人員必須天天都在一起工作。
• 圍繞被激勵起來的個體來構建項目。給他們提供所需的環境和支援，並且信任他們能夠完成工作。
• 在團隊內部，最具有效果並富有效率的傳遞資訊的方法，就是面對面的交談。
• 工作的軟體是首要的進度度量標準。
• 敏捷過程提倡可持續的開發速度。責任人、開發人員和使用者應該能夠保持一個長期的、恒定的開發速度。
• 不斷地關注優秀的技能和好的設計會增強敏捷能力。
• 簡單是最根本的。
• 最好的構架、需求和設計出於自組織團隊。
• 每隔一定時間，團隊會在如何才能更有效地工作方面進行反省，然後相應地對自己的行為進行調整。