四大價值觀：
個體和交互勝過過程和工具；
客戶合作勝過合同談判；
工作的軟件勝過全面的文檔；
響應變化重于遵循計劃。

12 原則：
準則1：Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
我們的最高目標是，通過盡早和持續地交付有價值的軟件來滿足客戶。
準則2：Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
歡迎對需求提出變更——即使是在項目開發后期。要善于利用需求變更，幫助客戶獲得競爭優勢。
準則3：Deliver working software frequently, from a couple of weeks to a couple of mouths, with a preference for the shorter timescale.
要不斷交付可用的軟件，周期從幾周到幾個月不等，且越短越好。
準則4：Business people and developers must work together daily throughout the project.
項目過程中，業務人員與開發人員必須在一起工作。
準則5：Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
要善于激勵項目人員，給他們以所需要的環境和支持，并相信他們能夠完成任務。
準則6：The most efficient and effective method of conveying information to and within
a development team is face-to-face conversation.
無論是團隊內還是團隊間，最有效的溝通方法是面對面的交談。
準則7：Working software is the primary measure of progress.
可用的軟件是衡量進度的主要指標。
準則8：Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
敏捷過程提倡可持續的開發。項目方、開發人員和用戶應該能夠保持恒久穩定的進展速度。
準則9：Continuous attention to technical excellence and good design enhances agility.
對技術的精益求精以及對設計的不斷完善將提升敏捷性。
準則10：Simplicity–the art of maximizing the amount of work not done–is essential.
要做到簡潔，即盡最大可能減少不必要的工作。這是一門藝術。
準則11：The best architectures, requirements, and designs emerge from self-organizing teams.
最佳的架構、需求和設計出自于自組織的團隊。
準則12：At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
團隊要定期反省如何能夠做到更有效，并相應地調整團隊的行為。

總結

以上是生活随笔為你收集整理的四大价值观和12准则的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。