進入敏捷專案管理的第一步


敏捷宣言(Agile Manifesto)

四大核心價值

1.  人員及互動比流程與工具更重要。
Individuals and interactions over processes and tools

2.  可正常運作的軟體比繁複的文件更重要。
Working Software over Comprehensive Documentation

3.  與客戶的合作比合約協定更重要。
Customer collaboration over contract negotiation

4.  對變更做回應比依計畫行事更重要。
Responding to change over following a plan
 
十二項準則

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 process harness change for the customer’s competitive advantage.

3.  經常性交付可正常運作的軟體,頻率可從數週到數個月,但時間間隔越短越好。
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to 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 user 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.

沒有留言 :

張貼留言