Distinguishing Agile from Waterfall<br>敏捷与瀑布的区别
Approach to Change<br>变更的方法
Waterfall: tries to avoid change、Formal change control processes<br>瀑布型：旨在避免变更、使用变更管理流程进行控制
Agile: Embraces uncertainty and unpredictability、quick customer feedback<br>敏捷型：拥抱不确定性和不可预测性、旨在快速反馈
Efficiency and Waste Reduction<br>提高效率并减少浪费
Waterfall: Emphasizes formal documentation and planning, <br>瀑布型：强调正式的文件和规划
Agile: person-to-person conversations. <br>Shorter and focused documentation is used, eliminating unnecessary formalities<br>敏捷型：强调人与人之间的对话，短的、针对性的文档，消除不必要的手续
Project Requirements<br>项目需求
Waterfall: detailed product requirements document、<br>formally approved project plans, and a change control board、<br>Focuses on protecting the team from building something the client or stakeholders don't want<br>瀑布型：详细的产品需求文档，正式批准的项目计划和变更控制委员会。<br>专注于保护团队免于构建客户或利益相关者不想要的东西<br>
Agile: Treats requirements as dynamic, expecting changes. <br>prioritize and continuously adapt requirements based on feedback. <br>Prioritization allows the team to focus on the most urgent or valuable items first<br>敏捷型：将需求视为动态的，期望变化。根据反馈确定需求的优先级并不断调整需求。<br>允许团队首先关注最紧急或最有价值的项目
Documentation<br>文档
Waterfall: Relies on extensive documentation. Formal documents are left at each stage<br>瀑布型：由于交接而依赖大量文档、 每个阶段都会留下正式文件<br>
Agile: person-to-person conversations. <br>Shorter and focused documentation is used, eliminating unnecessary formalities<br>敏捷型：强调人与人之间的对话，短的、针对性的文档，消除不必要的手续<br>
Deliverables<br>交付物
Waterfall: Typically releases the final deliverable at the end of the project, <br>瀑布型：通常在项目结束时发布最终可交付成果<br>
Agile: Emphasizes smaller, more frequent releases. <br>敏捷型：强调更小、更频繁的发布<br>
four values of the Agile Manifesto<br>敏捷宣言的四个价值观
Individuals and Interactions over Processes and Tools<br>人之间的沟通、协作 胜过 严格流程和工具
Working Software over Comprehensive Documentation<br>工作软件胜过全面的文档<br>
Customer Collaboration over Contract Negotiation<br>客户协作胜过合同谈判<br>
Responding to Change over Following a Plan<br>响应变化胜于遵循计划<br>
The 12 principles of the Agile Manifesto<br>敏捷宣言的 12 条原则<br>https://agilemanifesto.org/principles.html<br>
Early and continuous delivery of valuable software<br>快速、持续交付获得客户满意
Deliver working software frequently<br>经常、频繁交付，可以是两周，也可以是两个月，根据情况
Working software is the primary messure of progress<br>可用的软件是衡量进度的主要标准<br>
simplicity is essential<br>简单性，让工作任务关注重要的事情
Technical exchange and good design enchance agility<br>技术交流和良好的设计增强敏捷性<br>
Welcome changing requirement，even late in development<br>拥抱变化，即使变化会带来开发延迟
Business people and developers must work together<br>在一起办公
Support Effective Team Culture,Motivate and Trust Teams<br>围绕积极的员工展开项目，提供他们需要的环境，相信他们
face to face conversation<br>最有效的沟通方式：面对面沟通
maintain a constant pace indefinitely<br>保持固定的节奏
the best architectures,requirements, and designs emerge from self-organizing teams<br>最好的架构、需求和设计来自自组织团队<br>
Reflect and Adjust Regularly<br>建议团队定期反思其有效性，相应地调整和调整行为。 鼓励持续学习和改进<br>
