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