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