|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/succeeding-with-agile-estimation-and-planning/
课程评论：没有评论
Coursera 课程 **《敏捷之路：估算与 Sprint 规划》** 是一门实用的课程，旨在帮助团队克服在敏捷环境中进行估算和规划时遇到的常见挑战。许多敏捷团队在估算和规划方面之所以挣扎，是因为他们依然沿用为制造业和标准化产品设计的传统方法。然而，这种方法对于复杂的知识工作并不奏效。 本课程基于超过 10 家组织和 100 多个敏捷团队的教练经验，分享了实用的见解。课程将重点介绍两种常见的估算方法：**“无估算”（No Estimates）** 和 **“用户故事点估算”（Story Point Estimation, SPE）**。 **关于用户故事点估算，课程将深入探讨 12 个常见问题，包括：** * SPE 是否强制？所有 Scrum 团队都应该使用吗？ * 谁应该参与估算过程？ * 为什么使用斐波那契数列？ * 如何处理复杂用户故事的估算？ * Sprint 中是否可以更改用户故事点估算？ * Sprint 结束时是否可以拆分未完成的用户故事？ * 用户故事点与时间有什么关系？ * 为什么使用用户故事点？有什么好处？ * 如何估算子任务、错误、生产缺陷和探索性任务（spikes）？ * 何时应该更改参考基准（wall of reference）？ * 如何分析（并提高）估算的准确性？ * 如何估算史诗（Epics）、特性（Features）和项目（Initiatives）？ **在 Sprint 规划方面，课程将剖析传统规划方法为何在 Sprint 规划中效果不佳，以及如何转向更有效的 Sprint 规划。** 课程还将解答 8 个关于 Sprint 规划的常见问题，**例如：** * 我们如何决定一个 Sprint 要规划多少工作量？ * 为什么用小时/天来估算子任务？ * 人们在估算时应该保留多少缓冲？ * 是否需要在 Sprint 中更新任务级别的估算？ * 如何处理上一个 Sprint 的遗留工作（spillovers）？ * 当存在未解决的问题时，我们如何规划一个条目？ * 如何在 Sprint 规划中处理外部团队依赖？ * 还有其他 Sprint 规划的方法吗？ 总而言之，这门课程旨在为敏捷团队提供实用的工具、技术和思维方式，以改进他们的估算和 Sprint 规划能力，从而提升整体的敏捷实践效能。
Estimation and Planning are two basic practices that are essential for the success of every team. Most agile teams struggle with estimation and planning because they continue using traditional planning approach that is designed for manufacturing and works for well-defined, standardised products. Traditional planning approach is not effective for complex knowledge work.In this course, we will share practical insights based on my coaching experience with 10+ organizations and 100+ agile teams.We will cover two common estimation approaches - No Estimates and Story Point Estimation.Plus, we answer 12 frequently asked questions on Story Point Estimation:Is SPE mandatory? Should all Scrum teams use it?Who should participate in the estimation process?Why do we use Fibonacci sequence?How to address estimation for Complex user stories?Can we change the Story Point estimate during Sprint?Can we split unfinished stories at the end of Sprint?What is the relation between Story Points and time?Why Story Points? What are the benefits?How to estimate subtasks, bugs, production defects, spikes?When should we change the wall of reference?How to analyze (and improve) the accuracy of estimates?How to estimate Epics, Features, Initiatives?In Sprint Planning, we discuss why traditional planning approach does not work well for Sprint Planning and how to make a shift to an Effective Sprint Planning.We also cover the following 8 frequently asked questions on Sprint Planning:How do we decide how much work to plan for a Sprint?Why estimate Subtasks in hours/days?How much buffer should people keep while estimating?Do we need to update task-level efforts during Sprint?How to handle spillovers from previous Sprint?How to plan an item when we have open questions?How to address external team dependencies during Sprint Planning?Are there any other ways of planning Sprint?
