[{"data":1,"prerenderedAt":930},["ShallowReactive",2],{"blog-index-zh-CN":3},[4,191,329,485,578,770],{"id":5,"title":6,"author":7,"body":8,"dateModified":166,"datePublished":167,"description":168,"extension":169,"heading":170,"image":171,"imageAlt":17,"keywords":172,"locale":178,"meta":179,"navigation":180,"path":181,"reviewed":180,"seo":182,"sitemap":183,"slug":188,"stem":189,"translationKey":188,"__hash__":190},"blog\u002Fblog\u002Fzh-CN\u002Fmanage-sprint-dependencies-with-chained-pull-requests.md","冲刺依赖与链式拉取请求 | AELBOX","AELBOX",{"type":9,"value":10,"toc":145},"minimark",[11,23,26,35,40,44,53,56,59,62,66,69,72,75,78,81,85,88,96,100,103,106,109,112,115,118,121,124,127,130,133,136,139,142],[12,13,14],"p",{},[15,16],"img",{"alt":17,"height":18,"loading":19,"src":20,"width":21,"fetchPriority":22},"桌上的金属链条、Planning Poker 卡片和咖啡杯",960,"eager","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.webp",1600,"high",[12,24,25],{},"冲刺中经常包含相互依赖的工作项，可能出现在一个团队内部，也可能跨多个 Scrum 团队。理想情况下，依赖本不该存在；但在现实中，业务需求优先，为了缩短发布周期，依赖被加了进来。本文介绍软件团队管理依赖任务的一种方法。",[12,27,28],{},[15,29],{"alt":30,"height":31,"loading":32,"src":33,"width":31,"decoding":34},"任务之间的依赖",336,"lazy","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fblog-dep1.png","async",[12,36,37],{},[38,39,30],"em",{},[41,42,43],"h2",{"id":43},"传统做法",[12,45,46,47,52],{},"最直接的做法是：等依赖项合并进主分支后，立刻开始任务。这样一来，一些成员会在任务就绪之前一直闲着。最终，剩下的依赖任务几乎没有时间可用。最后几个任务被遗留到下一个冲刺，",[48,49,51],"a",{"href":50},"\u002Fzh-CN\u002Fblog\u002Fcomparison-metrics-for-agile-teams","团队自然不高兴","。",[12,54,55],{},"为什么容量估算正确，却还是会发生这种情况？主要原因是等待同事完成工作时的空闲时间。即便是很小的延误也会累积，在短冲刺中尤其明显。",[41,57,58],{"id":58},"同时处理有依赖的任务",[12,60,61],{},"有一种方法可以做到这一点，只需付出很小的额外成本。当团队成员同时处理任务时，有几项好处。",[63,64,65],"h3",{"id":65},"更好的协作",[12,67,68],{},"当成员同时处理有依赖的任务时，这种方式类似结对编程。一个人必须理解上游任务，另一个人必须理解下游任务。团队对所解决的问题因此有了更广的了解。",[63,70,71],{"id":71},"避免空闲时间",[12,73,74],{},"任务并行推进时，没有人需要等某个修复落地。大家可以同时工作，遇到问题时也能随时讨论。",[63,76,77],{"id":77},"拉取请求更早进入代码评审",[12,79,80],{},"当你的分支基于同事的分支时，批准最初的拉取请求会更容易。你已经了解上游工作项是如何实现的，而原分支在整个实现过程中经过了测试和评审。它不再是陌生的领域。",[41,82,84],{"id":83},"使用链式堆叠式拉取请求","使用链式（堆叠式）拉取请求",[12,86,87],{},"这种程度的并行需要合适的工具。基于 Git 的版本控制就能直接做到。下面的步骤描述了这一过程。",[12,89,90],{},[15,91],{"alt":92,"height":93,"loading":32,"src":94,"width":95,"decoding":34},"依赖树（同时处理 6 个有依赖的任务）",438,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fdep-img2.png",800,[12,97,98],{},[38,99,92],{},[63,101,102],{"id":102},"清晰勾勒依赖关系",[12,104,105],{},"在冲刺规划期间定义依赖链。之后，拉取请求链严格遵循这个定义。开发中途修改链条的代价很高，因为需要变基。",[63,107,108],{"id":108},"先从根任务开始",[12,110,111],{},"每条依赖链都有不依赖任何其他任务的根任务。它们的工作可以从第一天就开始。",[63,113,114],{"id":114},"先完成核心实现",[12,116,117],{},"这可能与测试驱动开发相冲突，因为后者要求先写测试。为了让拉取请求链保持可控，先实现核心部分。这样，依赖它的成员能更早拿到可用的代码。",[63,119,120],{"id":120},"按先进先出队列组织代码评审",[12,122,123],{},"最先创建的分支应最先评审和合并。每次合并都会触发 CI；如果它破坏了主构建，问题还能在影响尚小时就被修复。",[41,125,126],{"id":126},"额外成本",[12,128,129],{},"维护一条依赖分支链有好处，也有一些代价。",[63,131,132],{"id":132},"变基与合并",[12,134,135],{},"链条必须保持同步，这需要付出精力。现代工具在没有冲突时提供与基础分支的一键同步。在安全的情况下按需使用，把上游变更拉进来。构建通过、功能正常时，就同步。",[63,137,138],{"id":138},"团队协作",[12,140,141],{},"依赖链需要一个愿意彼此沟通、善于协作的团队。如果大家各自为战，这套方法就行不通。",[12,143,144],{},"有依赖的工作项最好放在当前冲刺之外。当业务需求要求它们并行推进时，用一条派生分支组成的链来管理依赖带来的额外成本，是一种切实可行的办法。",{"title":146,"searchDepth":147,"depth":147,"links":148},"",2,[149,150,156,162],{"id":43,"depth":147,"text":43},{"id":58,"depth":147,"text":58,"children":151},[152,154,155],{"id":65,"depth":153,"text":65},3,{"id":71,"depth":153,"text":71},{"id":77,"depth":153,"text":77},{"id":83,"depth":147,"text":84,"children":157},[158,159,160,161],{"id":102,"depth":153,"text":102},{"id":108,"depth":153,"text":108},{"id":114,"depth":153,"text":114},{"id":120,"depth":153,"text":120},{"id":126,"depth":147,"text":126,"children":163},[164,165],{"id":132,"depth":153,"text":132},{"id":138,"depth":153,"text":138},"2026-11-21","2018-05-27","有依赖的工作项会让冲刺停滞，大家都在等待。了解堆叠式拉取请求如何让工作持续流动，并减少空闲时间。","md","用链式拉取请求管理冲刺依赖","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.jpg",[173,174,175,176,177],"冲刺依赖","堆叠式拉取请求","链式拉取请求","代码评审","敏捷交付","zh-CN",{},true,"\u002Fblog\u002Fzh-cn\u002Fmanage-sprint-dependencies-with-chained-pull-requests",{"title":6,"description":168},{"loc":181,"images":184,"lastmod":166},[185,186,187],{"loc":20},{"loc":33},{"loc":94},"manage-sprint-dependencies-with-chained-pull-requests","blog\u002Fzh-CN\u002Fmanage-sprint-dependencies-with-chained-pull-requests","9HWk5FBczoQcum_xZW8g0Ulmu7K8ofCsJ-pKr0hIWkw",{"id":192,"title":193,"author":7,"body":194,"dateModified":166,"datePublished":308,"description":309,"extension":169,"heading":310,"image":311,"imageAlt":200,"keywords":312,"locale":178,"meta":318,"navigation":180,"path":319,"reviewed":180,"seo":320,"sitemap":321,"slug":326,"stem":327,"translationKey":326,"__hash__":328},"blog\u002Fblog\u002Fzh-CN\u002Fcomparison-metrics-for-agile-teams.md","敏捷团队的对比指标 | AELBOX",{"type":9,"value":195,"toc":299},[196,203,206,209,212,220,224,227,230,233,236,244,248,256,259,262,265,272,276,279,286,289,293,296],[12,197,198],{},[15,199],{"alt":200,"height":201,"loading":19,"src":202,"width":21,"fetchPriority":22},"桌上的直尺、Planning Poker 卡片和咖啡杯",958,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.webp",[12,204,205],{},"比较敏捷团队并不容易，也值得问一问：我们究竟为什么要比较？把不同领域的团队放在一起对比，到底有什么帮助？",[41,207,208],{"id":208},"营造良性竞争",[12,210,211],{},"不应该用随意挑选的指标给团队排名，那只会打击士气。相反，指标应当让每个团队都有平等竞争的机会。这样，绩效的提升源自团队自身的意愿，而不是有人在一旁催促。",[12,213,214],{},[15,215],{"alt":216,"height":217,"loading":32,"src":218,"width":219,"decoding":34},"营造竞争氛围",487,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun2.png",525,[12,221,222],{},[38,223,216],{},[41,225,226],{"id":226},"创造平等机会的指标",[12,228,229],{},"以下是四项用于比较团队的基础指标。它们只衡量每个团队在公平条件下竞争的能力，仅此而已。可比的指标创造平等的机会。",[63,231,232],{"id":232},"成功的冲刺",[12,234,235],{},"如果冲刺只是一个时间区间，那它毫无意义。冲刺是一个里程碑，需要有一个目标。冲刺目标（最重要的一组故事）是较大的里程碑，完成每一个故事则是较小的里程碑。在每个冲刺结束时举行跨团队演示，让各团队展示自己交付的成果。这种良性竞争会鼓励团队完成冲刺目标。人需要一个看得见的目标才有动力。",[12,237,238],{},[15,239],{"alt":240,"height":241,"loading":32,"src":242,"width":243,"decoding":34},"朝着目标冲刺",680,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun1.png",874,[12,245,246],{},[38,247,240],{},[12,249,250,251,255],{},"这会不会变成一场过度承诺与刻意少承诺的游戏？如果团队承诺不足，演示会暴露一切：能展示的东西更少。如果承诺过多，演示就成了",[252,253,254],"strong",{},"又一次失败的冲刺","。交付自己所承诺的内容，会积累做得更多的动力，团队也会对工作感到满意。",[63,257,258],{"id":258},"速度的稳定性与诚实估算",[12,260,261],{},"这是知识工作，不是流水线作业。如果团队里没有人足够理解某个问题、能够估算它的解决方案，那就说明这个问题事先没有得到充分调研。",[12,263,264],{},"在上一个冲刺中安排一次限时调研，然后由团队一起评审调研结果，就能轻松地把实现拆成更小的故事并妥善估算。对于复杂的工作，可以写一份更完整的技术设计文档，列出各个实现故事。",[12,266,267,268,52],{},"调研和设计工作本身就是可以被估算的故事。关键在于为复杂的解决方案定义工作的结构和顺序。与其承诺一个团队并不理解的故事，不如创建一个调研任务来填补空白。这样，估算才",[48,269,271],{"href":270},"\u002Fzh-CN\u002Fblog\u002Fsheepherding-story-points","有据可依",[63,273,275],{"id":274},"容量的可预测性避免意外工作","容量的可预测性（避免意外工作）",[12,277,278],{},"先调研，后实现。随着调研暴露出问题，新的工作项被创建并估算。这样，你对下一个冲刺的把握就清晰得多。已知的工作可以被估算和规划；未知的工作先获得一个限时的调研工作项，然后再估算。这里的关键纪律，是把大块工作拆成小块、可估算的部分。",[12,280,281,282,52],{},"复杂的工作可以提前启动，哪怕只是为了发现它需要自己的一套故事。这仍然降低了",[48,283,285],{"href":284},"\u002Fzh-CN\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint","未知带来的风险",[12,287,288],{},"支持和生产环境救火通常以限时的看板流程在冲刺之外运行。在那里，首次响应时间和 SLA 违规次数就成了对比指标。",[63,290,292],{"id":291},"团队可用率任务时间除以冲刺总时间","团队可用率（任务时间除以冲刺总时间）",[12,294,295],{},"可用率是指团队成员花在已估算工作上的时间占比。如果某个团队比其他团队更频繁地被拉去参加培训、知识分享或其他内部工作，就要纠正这种失衡。保持速度稳定的唯一办法，是保持可用率稳定。当各团队之间的可用率相当时，其他对比指标才能发挥作用。",[12,297,298],{},"比较团队不是为了惩罚表现不佳者，而是为了提升动力，以及竞争和交付更多的意愿。正因如此，这些指标不应让团队成员个人看到：它们是辅导工具，而不是公开排行榜。通过跟踪这些指标并间接引导 Scrum Master，你能让各团队站在同一起跑线上竞争。",{"title":146,"searchDepth":147,"depth":147,"links":300},[301,302],{"id":208,"depth":147,"text":208},{"id":226,"depth":147,"text":226,"children":303},[304,305,306,307],{"id":232,"depth":153,"text":232},{"id":258,"depth":153,"text":258},{"id":274,"depth":153,"text":275},{"id":291,"depth":153,"text":292},"2018-05-04","指标应当创造公平的起点，而不是排行榜。四项对比指标，既能激励敏捷团队，又不会惩罚他们。","敏捷团队的对比指标","\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.jpg",[313,314,315,316,317],"敏捷指标","团队速度","敏捷团队","Scrum","容量",{},"\u002Fblog\u002Fzh-cn\u002Fcomparison-metrics-for-agile-teams",{"title":193,"description":309},{"loc":319,"images":322,"lastmod":166},[323,324,325],{"loc":202},{"loc":218},{"loc":242},"comparison-metrics-for-agile-teams","blog\u002Fzh-CN\u002Fcomparison-metrics-for-agile-teams","QZbrcKPUFp3IzMTSASesw2G1BOOvVyYLtbpROgZjQW8",{"id":330,"title":331,"author":7,"body":332,"dateModified":166,"datePublished":462,"description":463,"extension":169,"heading":464,"image":465,"imageAlt":338,"keywords":466,"locale":178,"meta":471,"navigation":180,"path":472,"reviewed":180,"seo":473,"sitemap":474,"slug":482,"stem":483,"translationKey":482,"__hash__":484},"blog\u002Fblog\u002Fzh-CN\u002Fsheepherding-story-points.md","羊群效应与故事点：Planning Poker 中的锚定 | AELBOX",{"type":9,"value":333,"toc":453},[334,340,343,346,353,360,364,367,370,373,380,384,387,390,393,398,402,405,408,415,419,422,425,430,434,437,447,450],[12,335,336],{},[15,337],{"alt":338,"height":18,"loading":19,"src":339,"width":21,"fetchPriority":22},"茶几上的一群绵羊和 Planning Poker 卡片","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.webp",[12,341,342],{},"故事点估算常常被忽视，或者在聊天室和公开会议中进行，每个人的投票都能被看到或听到。知道别人如何投票会扭曲结果，产生不准确的估算。一再失准的估算会导致计划有缺陷，交付延期甚至取消。下面就是公开投票中发生的事情。",[41,344,345],{"id":345},"投票中的几类角色",[12,347,348,349,352],{},"在一场公开的估算投票中，会出现几类典型角色。估算结果取决于谁先出牌，而且通常离诚实相去甚远。为什么在公开投票中顺序如此重要？因为",[252,350,351],{},"羊群效应","：这种锚定偏差会让其他成员照搬第一个估算。",[12,354,355],{},[15,356],{"alt":351,"height":357,"loading":32,"src":358,"width":359,"decoding":34},746,"\u002Fblog\u002Fsheepherding-story-points\u002Fsheep-1.png",1779,[12,361,362],{},[38,363,351],{},[63,365,366],{"id":366},"过度自信的投票者",[12,368,369],{},"每个团队至少有一名成员认为自己最了解系统。他们通常第一个投票，因为答案在他们看来显而易见。他们常常忽略那些可能让估算偏离正轨的细节。这些细节本可以提前发现，但前提是有人发起讨论。而在公开投票中，这不可能发生。",[12,371,372],{},"这个人给出的估算通常低于诚实的水平。也许只有他们能这么快完成这个故事，而且还得靠运气。",[12,374,375],{},[15,376],{"alt":366,"height":377,"loading":32,"src":378,"width":379,"decoding":34},290,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg7.png",600,[12,381,382],{},[38,383,366],{},[12,385,386],{},"其他人纷纷跟随，于是任务看起来很简单，仿佛在规定时间内谁都能完成。实际上，最后通常由别人来做。",[63,388,389],{"id":389},"沉默的投票者",[12,391,392],{},"沉默的投票者通常不止一个，他们不敢先投票，会等别人先出牌，然后照着抄。他们很少参与讨论，只在被问到时才回答。他们第二个投票，正好排在心不在焉的投票者之前。",[12,394,395],{},[15,396],{"alt":389,"height":377,"loading":32,"src":397,"width":379,"decoding":34},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg5.png",[12,399,400],{},[38,401,389],{},[63,403,404],{"id":404},"心不在焉的投票者",[12,406,407],{},"在实现阶段很难抓住他们，但在投票时他们的表现一目了然。他们总是最后投票，并照抄别人的估算。如果几个估算不一致，他们就挑最常见的那一个。他们不愿解释为什么选了更低或更高的数字，因此在梳理中回避协作，也躲闪问题。",[12,409,410],{},[15,411],{"alt":404,"height":412,"loading":32,"src":413,"width":414,"decoding":34},353,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg4.png",758,[12,416,417],{},[38,418,404],{},[63,420,421],{"id":421},"疲惫的投票者",[12,423,424],{},"有些成员无法长时间保持专注，会错过讨论中的关键部分。他们失去上下文，于是要么随口猜一个，要么找出最常见的投票抄下来。",[12,426,427],{},[15,428],{"alt":421,"height":377,"loading":32,"src":429,"width":379,"decoding":34},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg6.png",[12,431,432],{},[38,433,421],{},[41,435,436],{"id":436},"如何在估算过程中保持专注",[12,438,439,440,444,445,52],{},"估算之所以重要，是因为只有诚实的故事点才能",[48,441,443],{"href":442},"\u002Fzh-CN\u002Fblog\u002Fcorrectly-estimating-release-deadline","让项目按计划走向发布日期","。无论使用纸质卡片还是软件，诚实估算的关键都在于对抗",[252,446,351],{},[12,448,449],{},"在主持人揭晓之前，团队成员绝不应该看到彼此的估算。这样，沉默的投票者开始思考，心不在焉的投票者产生兴趣，疲惫的投票者也清醒过来。最值得问的问题，尤其是当有人与团队意见不同时，是“你为什么投了 X 个故事点？”这会开启一场关于真实实现问题的对话。而“你同意 X 个故事点吗？”这类封闭式问题，只会换来一句毫无意义的“同意”。",[12,451,452],{},"好的估算工具能让梳理更有参与感，让每个人保持警觉、随时愿意讨论，即使是复杂的故事也能得到更好的估算。",{"title":146,"searchDepth":147,"depth":147,"links":454},[455,461],{"id":345,"depth":147,"text":345,"children":456},[457,458,459,460],{"id":366,"depth":153,"text":366},{"id":389,"depth":153,"text":389},{"id":404,"depth":153,"text":404},{"id":421,"depth":153,"text":421},{"id":436,"depth":147,"text":436},"2018-04-30","公开投票会让第一个估算锚定全场。看看羊群效应如何扭曲故事点，以及如何诚实地开展 Planning Poker。","羊群效应与故事点","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.jpg",[467,468,469,351,470],"故事点","Planning Poker","锚定偏差","敏捷估算",{},"\u002Fblog\u002Fzh-cn\u002Fsheepherding-story-points",{"title":331,"description":463},{"loc":472,"images":475,"lastmod":166},[476,477,478,479,480,481],{"loc":339},{"loc":358},{"loc":378},{"loc":397},{"loc":413},{"loc":429},"sheepherding-story-points","blog\u002Fzh-CN\u002Fsheepherding-story-points","NSDqMFV96McI3KuKdQwrAbF7S9efeahz8eMEuTExyxw",{"id":486,"title":487,"author":7,"body":488,"dateModified":166,"datePublished":558,"description":559,"extension":169,"heading":560,"image":561,"imageAlt":494,"keywords":562,"locale":178,"meta":567,"navigation":180,"path":568,"reviewed":180,"seo":569,"sitemap":570,"slug":575,"stem":576,"translationKey":575,"__hash__":577},"blog\u002Fblog\u002Fzh-CN\u002Fthe-10-percent-scrumban-rule-for-every-sprint.md","每个冲刺都适用的 10% Scrumban 规则 | AELBOX",{"type":9,"value":489,"toc":553},[490,497,505,508,511,519,523,526,529,532,535,538,546,550],[12,491,492],{},[15,493],{"alt":494,"height":495,"loading":19,"src":496,"width":21,"fetchPriority":22},"茶几上的 Planning Poker 卡片和看板",959,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fcoffee-table-scrumban.webp",[12,498,499,500,504],{},"许多团队在规划时，会恰好用满 Jira 计划中显示的容量。这往往是错误的，并且会导致冲刺失败。既然",[48,501,503],{"href":502},"\u002Fzh-CN\u002Fblog\u002Fthe-importance-of-predictable-velocity","容量计算","看起来如此精确，为什么还会出问题？",[41,506,507],{"id":507},"急于交付更多",[12,509,510],{},"每成功完成一个冲刺，产品负责人往往就会推动更高的速度，这是对最新结果的自然反应。如果团队上个冲刺完成了若干故事点，下个冲刺就被期望完成更多。如此循环，直到某个冲刺失败。这种推动意在试探团队的极限。根据我们的经验，它适得其反，最终会让团队失去动力，把之后每一个冲刺都看作注定失败。",[12,512,513],{},[15,514],{"alt":515,"height":516,"loading":32,"src":517,"width":518,"decoding":34},"注定失败的冲刺",349,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg1.png",400,[12,520,521],{},[38,522,515],{},[41,524,525],{"id":525},"赶交付时的冲刺尾声",[12,527,528],{},"当容量被安排得恰好填满冲刺时，任何延误或已经发生的风险，都会在尾声造成拼命赶工的压力。压力之下，团队交付的反而少于承诺。这种冲刺末尾的赶工应当被消除。",[41,530,531],{"id":531},"让团队自愿交付更多",[12,533,534],{},"只规划团队容量的 90%，把剩下的 10% 留给待办事项中未规划的工作。这些任务会在冲刺期间以 Scrumban 的方式从待办事项中拉取。缓冲吸收风险，让团队提前几天完成冲刺（至少完成冲刺目标）。如果外部依赖威胁到冲刺，缓冲中的任务可以替换出问题的那一个。",[12,536,537],{},"这 10% 不属于冲刺承诺。如果风险没有发生，团队把它作为额外工作交付；如果出了问题，缓冲被消耗，但冲刺目标和承诺仍然达成。要留意缓冲的使用比例：如果它经常达到 20%，就该在保留 10% 缓冲的同时，把团队的速度提高 10%。",[12,539,540],{},[15,541],{"alt":542,"height":543,"loading":32,"src":544,"width":545,"decoding":34},"提前交付，额外交付",320,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg3-1.png",296,[12,547,548],{},[38,549,542],{},[12,551,552],{},"我们的经验表明，正是在没有压力的时候，员工贡献得最多。速度便能按团队自己的节奏提升，没有外部施压，压力也更小。这种增长显得自然且可持续。",{"title":146,"searchDepth":147,"depth":147,"links":554},[555,556,557],{"id":507,"depth":147,"text":507},{"id":525,"depth":147,"text":525},{"id":531,"depth":147,"text":531},"2018-04-28","按满容量承诺会让每个冲刺都变得脆弱。10% 的 Scrumban 缓冲可以吸收风险、保护冲刺目标，并让速度自然增长。","每个冲刺都适用的 10% Scrumban 规则","\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fcoffee-table-scrumban.jpg",[563,564,565,566,316],"Scrumban","冲刺容量","敏捷缓冲","速度",{},"\u002Fblog\u002Fzh-cn\u002Fthe-10-percent-scrumban-rule-for-every-sprint",{"title":487,"description":559},{"loc":568,"images":571,"lastmod":166},[572,573,574],{"loc":496},{"loc":517},{"loc":544},"the-10-percent-scrumban-rule-for-every-sprint","blog\u002Fzh-CN\u002Fthe-10-percent-scrumban-rule-for-every-sprint","p0-rghNVJvC4Txj3fyeUtSb67VhM9W4HVae02T8dXEs",{"id":579,"title":580,"author":7,"body":581,"dateModified":166,"datePublished":748,"description":749,"extension":169,"heading":750,"image":751,"imageAlt":587,"keywords":752,"locale":178,"meta":756,"navigation":180,"path":757,"reviewed":180,"seo":758,"sitemap":759,"slug":767,"stem":768,"translationKey":767,"__hash__":769},"blog\u002Fblog\u002Fzh-CN\u002Fcorrectly-estimating-release-deadline.md","如何用故事点估算发布日期 | AELBOX",{"type":9,"value":582,"toc":734},[583,589,592,595,602,605,608,616,620,623,626,629,632,635,643,647,650,653,656,659,662,665,673,677,680,683,686,689,697,701,704,707,712,719,727,731],[12,584,585],{},[15,586],{"alt":587,"height":18,"loading":19,"src":588,"width":21,"fetchPriority":22},"桌上的 Planning Poker 卡片、甘特图和咖啡杯","\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fcoffee-table-gantt-cards.webp",[12,590,591],{},"估算项目的发布日期是项目管理的重要组成部分。但面对一个庞大而复杂的系统，你该如何预测它的交付时间？",[41,593,594],{"id":594},"估算的难题",[12,596,597,598,601],{},"要按时交付，就需要对工作量做出可靠的估算。",[48,599,600],{"href":502},"估算任务通常很困难","，尤其是当你必须为每个任务承诺基于时间的估算时。从心理上说，承诺一个完成时间并不容易，而这些承诺往往落空。",[63,603,604],{"id":604},"时间估算的问题",[12,606,607],{},"用时间估算有个简单的原因：任务越复杂，错过截止日期的可能性就越大。它还取决于任务由谁接手。团队成员的工作节奏不同，产出也各不相同。由于可用率会随休假和培训而变化，由最快成员估算的任务，最终可能落到最慢的人手上。原本整齐的甘特图变得一团糟：任务不断逾期，管理者时刻担心项目能否按时完成。",[12,609,610],{},[15,611],{"alt":612,"height":613,"loading":32,"src":614,"width":615,"decoding":34},"被打乱的甘特图",351,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory1.png",510,[12,617,618],{},[38,619,612],{},[63,621,622],{"id":622},"对时间估算的抵触",[12,624,625],{},"当实现者被要求给出估算时，他们往往会抵触：如果估算没达成，责任算谁的？如果一个人估算的任务最终交给别人，实际耗时对不上时，又该怪谁？",[12,627,628],{},"结果就是大家干脆不愿意估算，管理层也因此难以准确估算交付日期。",[41,630,631],{"id":631},"使用故事点",[12,633,634],{},"故事点提供了时间估算之外的另一种选择。故事点不是固定的工作量单位，而是一种按指数增长的相对估算。整个团队在梳理期间一起估算。",[12,636,637],{},[15,638],{"alt":639,"height":640,"loading":32,"src":641,"width":642,"decoding":34},"估算示例",210,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory2.png",801,[12,644,645],{},[38,646,639],{},[63,648,649],{"id":649},"共担责任",[12,651,652],{},"使用故事点时，每个任务都由整个团队估算。当所有人达成一致，估算即被接受。这样就避免了日后争论任务是谁估算的、实际又花了多久。团队事先已经达成共识，责任自然由大家共担。",[63,654,655],{"id":655},"估算复杂度",[12,657,658],{},"故事点反映任务的复杂度，包括外部依赖以及可能出现问题的风险。由于它们不是对时间这类物理指标的承诺，团队给出估算时也更轻松。",[63,660,661],{"id":661},"最小估算",[12,663,664],{},"由于故事点是相对的，你需要一个起点作为锚点。这个锚点就是需要一定实现工作量的最小工作单元，也是团队能够估算的最小工作量。",[12,666,667],{},[15,668],{"alt":669,"height":670,"loading":32,"src":671,"width":672,"decoding":34},"最低估算",206,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory3.png",141,[12,674,675],{},[38,676,669],{},[63,678,679],{"id":679},"最大估算",[12,681,682],{},"故事点按指数增长，说明任务越复杂就越难估算。这个刻度可以延伸到无穷大（∞），尽管几乎没人会用到。最大的估算值应当是一个人平均在一个冲刺内能完成的最大工作量。冲刺长度本身也应与一个人在不失控的前提下能处理的最大工作量相匹配。",[63,684,685],{"id":685},"超出最大估算的故事",[12,687,688],{},"有些任务得到的故事点超过了一个人在一个冲刺内能完成的工作量。把它们放进冲刺，就会造成遗留。遗留会让冲刺显得不完整，也让工作显得没做完。估算超过这一上限的任务，必须拆分成更小的单元并重新估算。",[12,690,691],{},[15,692],{"alt":693,"height":694,"loading":32,"src":695,"width":696,"decoding":34},"拆分 13 个故事点",201,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory4.png",272,[12,698,699],{},[38,700,693],{},[41,702,703],{"id":703},"故事点速度",[12,705,706],{},"速度是指团队在满可用率下，每个冲刺平均完成的故事点数。可用率是指团队在扣除休假、培训和支持工作后，实际能投入项目工作的冲刺时间占比。容量等于速度乘以可用率。",[12,708,709],{},[38,710,711],{},"容量 = 速度 × 可用率",[12,713,714,715,718],{},"由于容量以故事点表示，可以用团队的故事点与时间的换算比例把它转换成时间。当",[48,716,717],{"href":502},"速度可预测","时，发布日期就能被精确估算。以故事点和冲刺为基础，得到的甘特图稳定而可预测：",[12,720,721],{},[15,722],{"alt":723,"height":724,"loading":32,"src":725,"width":726,"decoding":34},"恢复秩序的甘特图",362,"\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fstory5.png",519,[12,728,729],{},[38,730,723],{},[12,732,733],{},"这就是关键转变：一旦速度稳定下来，发布日期就成了一道计算题，而不是一次猜测。",{"title":146,"searchDepth":147,"depth":147,"links":735},[736,740,747],{"id":594,"depth":147,"text":594,"children":737},[738,739],{"id":604,"depth":153,"text":604},{"id":622,"depth":153,"text":622},{"id":631,"depth":147,"text":631,"children":741},[742,743,744,745,746],{"id":649,"depth":153,"text":649},{"id":655,"depth":153,"text":655},{"id":661,"depth":153,"text":661},{"id":679,"depth":153,"text":679},{"id":685,"depth":153,"text":685},{"id":703,"depth":147,"text":703},"2018-04-14","当复杂度和可用率发生变化时，基于时间的估算就会失效。了解故事点、共同估算和速度如何让发布日期变得可预测。","如何估算发布日期","\u002Fblog\u002Fcorrectly-estimating-release-deadline\u002Fcoffee-table-gantt-cards.jpg",[753,467,470,754,755],"发布日期","冲刺速度","容量规划",{},"\u002Fblog\u002Fzh-cn\u002Fcorrectly-estimating-release-deadline",{"title":580,"description":749},{"loc":757,"images":760,"lastmod":166},[761,762,763,764,765,766],{"loc":588},{"loc":614},{"loc":641},{"loc":671},{"loc":695},{"loc":725},"correctly-estimating-release-deadline","blog\u002Fzh-CN\u002Fcorrectly-estimating-release-deadline","domrUbLQNygCG8IqEbb2qv4NL1EggMHUDp8Nxv0vzLo",{"id":771,"title":772,"author":7,"body":773,"dateModified":166,"datePublished":748,"description":912,"extension":169,"heading":913,"image":914,"imageAlt":779,"keywords":915,"locale":178,"meta":918,"navigation":180,"path":919,"reviewed":180,"seo":920,"sitemap":921,"slug":927,"stem":928,"translationKey":927,"__hash__":929},"blog\u002Fblog\u002Fzh-CN\u002Fthe-importance-of-predictable-velocity.md","可预测的速度：让冲刺承诺更可靠 | AELBOX",{"type":9,"value":774,"toc":902},[775,781,784,787,790,793,796,804,808,811,814,817,820,823,830,837,841,844,847,850,853,856,859,862,865,872,876,879,887,890,893,899],[12,776,777],{},[15,778],{"alt":779,"height":18,"loading":19,"src":780,"width":21,"fetchPriority":22},"茶几上的 Planning Poker 卡片和秒表","\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fcoffee-table-chronometer.webp",[12,782,783],{},"可预测的速度，是指团队能够事先知道：在给定时间段内，根据自身的可用率，能完成多少工作。",[41,785,786],{"id":786},"速度波动的问题",[12,788,789],{},"当速度在不同冲刺之间波动时，发布规划就会变得困难。没有人知道工作何时交付，整个 Scrum 流程也随之瓦解。混乱占据上风，团队士气自然好不到哪里去。",[12,791,792],{},"速度波动通常是因为团队成员都想尽力而为，承诺了超出自己交付能力的工作。在协作良好、开发流程设置得当的环境中，一项任务远不止直接实现那么简单。有些成员运气好，接到的任务实现起来相对简单；另一些人则撞上没人预料到的问题。某个冲刺里，团队在收尾遗留任务，速度看起来很高；下一个冲刺，新的遗留任务出现，速度又掉了下来。",[12,794,795],{},"遗留任务会让人觉得团队表现不佳：明明还能多做一点，却总有无法预料的事情挡在路上。管理层注意到了问题，看到了错过的截止日期，团队成员之间的紧张气氛也随之升温。",[12,797,798],{},[15,799],{"alt":800,"height":801,"loading":32,"src":802,"width":803,"decoding":34},"带遗留任务的常规冲刺",198,"\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fstory6.png",461,[12,805,806],{},[38,807,800],{},[41,809,810],{"id":810},"维持可预测性的常见问题",[12,812,813],{},"问题因项目而异，但许多问题在所有类型的项目中都存在。以下是常见问题及其实用对策。",[63,815,816],{"id":816},"为意外留出余地",[12,818,819],{},"有些任务在开始之前需要先做调研。设想一个功能依赖第三方公司，而对方可能在你需要时毫无回应；或者团队在创建任务时误解了底层技术，导致功能无法按计划实现。",[12,821,822],{},"如果这样的任务在没有完成必要调研的情况下被放进冲刺，它很可能比预期耗时更久，而估算则成了替罪羊。有人会说，应该先做一个限时调研（spike）把问题弄清楚。可是，你怎么知道哪些任务需要调研？",[12,824,825,826,829],{},"唯一的办法是",[48,827,828],{"href":284},"提前开始处理任务","。在任务被规划之前就动手，可以在问题发生之前发现它们。采用这种方式，任务只有在足够清晰、并且部分工作已经完成时，才会进入冲刺。",[12,831,832],{},[15,833],{"alt":834,"height":801,"loading":32,"src":835,"width":836,"decoding":34},"提前开始任务的冲刺","\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fstory7.png",721,[12,838,839],{},[38,840,834],{},[63,842,843],{"id":843},"避免含糊的任务定义",[12,845,846],{},"有些任务在创建者看来没有问题，却漏掉了重要细节。而某些实现细节可能会严重影响交付。",[12,848,849],{},"业务利益相关者可能会主张，任务定义不应包含技术细节；但实现者往往觉得业务需求过于模糊，根本无法据此动手。",[12,851,852],{},"解决办法是编写一份技术设计文档，并让实现任务引用它。这样就能明确究竟需要构建什么。",[12,854,855],{},"在任务描述中补充技术细节同样有帮助，实现者因此知道要做什么，也能更早发现潜在问题。",[63,857,858],{"id":858},"用斐波那契数列下调容量",[12,860,861],{},"有时团队成员休假，或者法定假日落在冲刺期间。培训和内部活动同样会降低可用率，也就是团队能投入项目工作的时间。在这种情况下，必须下调容量，以反映缺勤的人员。",[12,863,864],{},"速度被假定为恒定值，但它是根据团队所有成员的平均速度计算出来的。为简单起见，假设一个人每天完成一个故事点。如果一个人缺勤一天，就把冲刺容量减少一个故事点。如果两个人缺勤两天（四个故事点），应把容量减少五个故事点（下一个斐波那契数），而不是四个。如果两个人缺勤三天，则减少八个点而不是六个，以覆盖依赖风险。",[12,866,867],{},[15,868],{"alt":869,"height":801,"loading":32,"src":870,"width":871,"decoding":34},"承诺低于计算所得的容量","\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fstory8.png",392,[12,873,874],{},[38,875,869],{},[63,877,878],{"id":878},"避免有依赖的任务",[12,880,881,882,886],{},"常见的情况是，一个人完成的任务正是另一位成员任务的依赖前提。这就产生了",[48,883,885],{"href":884},"\u002Fzh-CN\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests","团队内部或团队之间的依赖","。如果第一个任务延期，所有依赖它的任务都会跟着推迟。团队成员先空闲等待，等依赖解除后再匆忙赶工，宝贵的时间就这样被浪费了。",[12,888,889],{},"依赖任务可以更早开始，这样到了下一个冲刺，关键的上游任务已接近完成。依赖关系对当前冲刺速度的影响也随之减小。",[63,891,892],{"id":892},"诚实估算",[12,894,895,898],{},[48,896,897],{"href":270},"诚实估算任务","并不容易，需要整个团队全神贯注。每个人都应在不受他人估算影响的情况下给出自己的判断。只有诚实的估算，才能反映史诗真正需要多久，也才能让发布日期保持现实。",[12,900,901],{},"可预测的速度不是强加给团队的工具或指标，而是一个接一个消除意外的结果。从上面五项改进开始，发布日期就不再是猜测。",{"title":146,"searchDepth":147,"depth":147,"links":903},[904,905],{"id":786,"depth":147,"text":786},{"id":810,"depth":147,"text":810,"children":906},[907,908,909,910,911],{"id":816,"depth":153,"text":816},{"id":843,"depth":153,"text":843},{"id":858,"depth":153,"text":858},{"id":878,"depth":153,"text":878},{"id":892,"depth":153,"text":892},"为什么冲刺之间的速度会波动，以及如何让承诺变得可预测：针对规划、容量和依赖关系的五项实用改进。","可预测速度的重要性","\u002Fblog\u002Fthe-importance-of-predictable-velocity\u002Fcoffee-table-chronometer.jpg",[916,754,470,467,917],"可预测的速度","发布规划",{},"\u002Fblog\u002Fzh-cn\u002Fthe-importance-of-predictable-velocity",{"title":772,"description":912},{"loc":919,"images":922,"lastmod":166},[923,924,925,926],{"loc":780},{"loc":802},{"loc":835},{"loc":870},"the-importance-of-predictable-velocity","blog\u002Fzh-CN\u002Fthe-importance-of-predictable-velocity","E_HWZx4rpwaNWcD0wIyhLurssbaPoumailEcwgKDH_c",1795345553565]