5.Agile Project Management
2023-12-10 21:07:37 0 举报AI智能生成
敏捷项目管理
作者其他创作
大纲/内容
what<br>什么是敏捷项目管理
Based on the Agile Manifesto, consisting of four values and 12 principles.<br>基于敏捷宣言，由四个价值观和 12 条原则组成。<br>
Focuses on flexibility, iteration, and openness to change.<br>注重灵活性、迭代和变更的开放性。<br>
Strives for a mindset that emphasizes customer satisfaction and team collaboration.<br>努力形成强调客户满意度和团队协作的心态。<br>
why<br>为什么使用敏捷
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>
when<br>什么时候使用敏捷
industries or projects susceptible to or encouraging change and uncertainty<br>最适合容易变化或鼓励变化 以及 不确定性的行业或项目<br>
VUCA<br>一个缩写词，<br>定义了在不断变化的复杂世界中影响组织的条件；<br>由美军战争学院研发<br>
Volatility<br>波动性<br>
Uncertainty<br>不确定性
Complexity<br>复杂性
Ambiguity<br>模糊性
Agile Framework<br>敏捷框架
scrum
Origins<br>起源
derived from rugby，<br>based on a team working closely together to achieve a common objective<br>
Basics<br>基本概念
Sprints<br>时间段（迭代）
Work is completed in short cycles(typically one to four weeks long) <br>通常1到4个周
Stand-up meetings<br>站立会
15 minutes or less
Backlog<br>主要工件（任务清单）
Roles<br>角色
Scrum Master<br>敏捷专家<br>
ensures the team follows Agile values and principles, <br>adheres to processes, and focuses on delivering their best work<br>确保团队遵循敏捷价值观和原则，遵守流程，并专注于交付最好的工作<br>
Product Owner<br>产品负责人<br>
responsible for maximizing the value of the product <br>and prioritizing work<br>负责产品价值最大化<br>并确定工作的优先顺序<br>
Development Team<br>开发团队
responsible for delivering the product<br>负责开发产品
Advantages<br>优势
Clear roles and responsibilities<br>清晰的角色和职责
Regular and predictable meetings and delivery schedules<br>定期且可预测的会议和交付时间表<br>
Supports Agile values and principles<br>支持敏捷价值观和原则<br>
Open and adaptable, with ample online guidance and support<br>开放且适应性强，拥有充足的在线指导和支持<br>
Characteristics<br>特点
pizza-size team<br>最好是跨团队的3-9个成员
Suitable for projects where the team <br>and management value continuous learning <br>and adaptability<br>适合团队和管理层重视持续学习和适应性的项目<br>
KanBan<br>看板
Extreme Programming(XP)<br>极限编程
Lean
Blending project management approaches<br>混合使用项目管理方法
利益相关者偏好、监管要求以及与供应商的现有关系等因素都会影响混合方法的决定。<br>一致性至关重要，变化应该增加价值而不会对项目产生负面影响。
0 条评论
下一页
