敏捷 Agile
Contents
敏捷宣言
个体和互动 高于 流程和工具
工作的软件 高于 详尽的文档
客户合作 高于 合同谈判
响应变化 高于 遵循计划
也就是说,尽管右项有其价值,
我们更重视左项的价值。
|
|
Agile 12 Principle
- Our Highest Priority Is To Satisfy Customer through Early and Continuous Delivery
- Welcome-Changing Requirements Even Late In Development. Agile Processes Harnesses Change for Customer Competitive Advantage
- Deliver Working Software Frequently (Weekly or Monthly) With Focus on Shorter Timescale
- Business People and Developers Should Work Together Daily
- Build Projects around Motivated Individual. Provide Them the Environment and Support They Need and Trust Them
- The Most Efficient Way to Convey Information to Your Development Team is Face To Face Conversation
- Working Software Is a Primary Measure of Success
- Agile Process Promotes Sustainable Development. Sponsors, Developers and Users Should Maintain a Constant Pace
- Continuous Attention to Technical Excellence and Good Design Boosts Agility
- Simplicity—The Art of Maximizing The Amount of Work Not Done but Is Essential
- The Best Requirements, Architecture, and Design Emerge From Self Organizing Teams
- At Regular Interval, Team Reflects on How to Become More Effective and Tweak Behavior Accordingly
敏捷开发十二原则
- 我们的最高目标是,通过尽早和持续地交付有价值的软件来满足客户。
- 欢迎对需求提出变更——即使是在项目开发后期。要善于利用需求变更,帮助客户获得竞争优势。
- 要不断交付可用的软件,周期从几周到几个月不等,且越短越好
- 项目过程中,业务人员与开发人员必须在一起工作。
- 要善于激励项目人员,给他们以所需要的环境和支持,并相信他们能够完成任务。
- 无论是团队内还是团队间,最有效的沟通方法是面对面的交谈。
- 可用的软件是衡量进度的主要指标。
- 敏捷过程提倡可持续的开发。项目方、开发人员和用户应该能够保持恒久稳定的进展速度。
- 对技术的精益求精以及对设计的不断完善将提升敏捷性。
- 要做到简洁,即尽最大可能减少不必要的工作。这是一门艺术。
- 最佳的架构、需求和设计出自于自组织的团队。
- 团队要定期反省如何能够做到更有效,并相应地调整团队的行为。
敏捷的核心可以归纳成四个字:“渐进增强”。
https://blog.csdn.net/hanyongan300/article/details/79678030
https://blog.csdn.net/superkunkun/article/details/52940329
https://www.infoq.cn/article/k4TB7hZU4uM_8lhXEY9h?utm_source=rss&utm_medium=article
Author w1100n
LastMod 2019-04-21