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