[{"data":1,"prerenderedAt":868},["ShallowReactive",2],{"blog-zh-TW-comparison-metrics-for-agile-teams":3,"blog-related-zh-TW-comparison-metrics-for-agile-teams":161,"blog-chapter-zh-TW-comparison-metrics-for-agile-teams":581},{"id":4,"title":5,"author":6,"body":7,"dateModified":136,"datePublished":137,"description":138,"extension":139,"heading":140,"image":141,"imageAlt":16,"keywords":142,"locale":148,"meta":149,"navigation":150,"path":151,"reviewed":150,"seo":152,"sitemap":153,"slug":158,"stem":159,"translationKey":158,"__hash__":160},"blog\u002Fblog\u002Fzh-TW\u002Fcomparison-metrics-for-agile-teams.md","敏捷團隊的比較指標 | AELBOX","AELBOX",{"type":8,"value":9,"toc":124},"minimark",[10,22,25,29,32,41,46,49,52,56,59,67,71,79,82,85,88,97,101,104,111,114,118,121],[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":28,"height":36,"loading":37,"src":38,"width":39,"decoding":40},487,"lazy","\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun2.png",525,"async",[11,42,43],{},[44,45,28],"em",{},[26,47,48],{"id":48},"創造公平機會的指標",[11,50,51],{},"以下是四項比較團隊的基本指標。它們衡量每個團隊在公平立足點上競爭的能力，僅此而已。可比較的指標創造公平的機會。",[53,54,55],"h3",{"id":55},"成功的衝刺",[11,57,58],{},"如果衝刺只是一個時間框架，那就毫無意義。衝刺是一個里程碑，需要目標。衝刺目標（最重要的一組故事）是較大的里程碑，完成每一個故事則是較小的里程碑。在每個衝刺結束時舉辦跨團隊展示，讓各團隊呈現自己交付了什麼。這種良性競爭會鼓勵團隊完成衝刺目標。人需要看得見的目標才會被激勵。",[11,60,61],{},[14,62],{"alt":63,"height":64,"loading":37,"src":65,"width":66,"decoding":40},"朝目標衝刺",680,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun1.png",874,[11,68,69],{},[44,70,63],{},[11,72,73,74,78],{},"這會不會變成過度承諾與承諾不足的遊戲？如果團隊承諾不足，展示會讓一切無所遁形：能秀的東西變少了。如果過度承諾，展示就變成",[75,76,77],"strong",{},"又一次失敗的衝刺","。交付團隊所承諾的事，會建立做得更多的動力。團隊會對工作感到滿意。",[53,80,81],{"id":81},"速度穩定性與誠實估算",[11,83,84],{},"這是知識工作，不是生產線作業。如果團隊裡沒有人真正理解某個問題、足以估算它的解法，那代表這個問題沒有事先研究。",[11,86,87],{},"在上一個衝刺安排一個限時的 Spike，接著由團隊檢視研究結果，就能輕鬆把實作拆成更小的故事，妥善估算。對於複雜的工作，寫一份更完整的技術設計文件，列出實作故事。",[11,89,90,91,96],{},"Spike 與設計工作本身就是可以估算的故事。關鍵在於為複雜解法定義工作的結構與順序。與其承諾一個團隊不懂的故事，不如建立一項研究型工作來補上缺口。這樣估算才能",[92,93,95],"a",{"href":94},"\u002Fzh-TW\u002Fblog\u002Fsheepherding-story-points","以證據為基礎","。",[53,98,100],{"id":99},"容量可預測性避免意料之外的工作","容量可預測性（避免意料之外的工作）",[11,102,103],{},"研究先行，實作隨後。當研究發現問題，就建立新的工作項目並估算。你接著會對下一個衝刺有更清楚的圖像。已知的工作可以估算與規劃；未知的工作則先取得一個限時的研究工作項目，再進行估算。這項紀律就是把大型工作拆成小而可估算的片段。",[11,105,106,107,96],{},"複雜的工作可以提早開始，即使只是為了發現它需要自己的一組故事。這仍然能降低",[92,108,110],{"href":109},"\u002Fzh-TW\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint","未知的風險",[11,112,113],{},"支援與生產救火通常以限時的看板流程在衝刺之外進行。在那裡，首次回應時間與 SLA 違約就成了比較指標。",[53,115,117],{"id":116},"團隊可用度投入工作的時間除以衝刺總時間","團隊可用度（投入工作的時間除以衝刺總時間）",[11,119,120],{},"可用度是團隊成員花在已估算工作上的時間比例。如果某個團隊比其他團隊更常被拉去訓練、知識分享或其他內部工作，就要修正這個失衡。維持速度穩定的唯一方法，就是維持可用度穩定。當團隊之間的可用度相等，其他比較指標才會奏效。",[11,122,123],{},"比較團隊不是為了懲罰低績效，而是為了提高動力，以及競爭與交付更多的精神。這也是為什麼這些指標不應該讓個別團隊成員看到：它們是輔導的工具，不是公開的排行榜。透過追蹤這些指標、間接引導 Scrum Master，你就能讓團隊站在平等的立足點上競爭。",{"title":125,"searchDepth":126,"depth":126,"links":127},"",2,[128,129],{"id":28,"depth":126,"text":28},{"id":48,"depth":126,"text":48,"children":130},[131,133,134,135],{"id":55,"depth":132,"text":55},3,{"id":81,"depth":132,"text":81},{"id":99,"depth":132,"text":100},{"id":116,"depth":132,"text":117},"2026-11-21","2018-05-04","指標應該創造公平的立足點，而不是排行榜。四種能激勵敏捷團隊、又不會懲罰他們的比較指標。","md","敏捷團隊的比較指標","\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.jpg",[143,144,145,146,147],"敏捷指標","團隊速度","敏捷團隊","Scrum","容量","zh-TW",{},true,"\u002Fblog\u002Fzh-tw\u002Fcomparison-metrics-for-agile-teams",{"title":5,"description":138},{"loc":151,"images":154,"lastmod":136},[155,156,157],{"loc":19},{"loc":38},{"loc":65},"comparison-metrics-for-agile-teams","blog\u002Fzh-TW\u002Fcomparison-metrics-for-agile-teams","02GYIXumbgYlagHSXkvZT1etbyroF2QAtzOmofeHoE0",[162,331,488],{"id":163,"title":164,"author":6,"body":165,"dateModified":136,"datePublished":310,"description":311,"extension":139,"heading":312,"image":313,"imageAlt":171,"keywords":314,"locale":148,"meta":320,"navigation":150,"path":321,"reviewed":150,"seo":322,"sitemap":323,"slug":328,"stem":329,"translationKey":328,"__hash__":330},"blog\u002Fblog\u002Fzh-TW\u002Fmanage-sprint-dependencies-with-chained-pull-requests.md","衝刺相依性與鏈式 Pull Request | AELBOX",{"type":8,"value":166,"toc":292},[167,174,177,184,188,191,198,201,204,207,210,213,216,219,223,226,230,233,241,246,249,252,255,258,261,264,267,270,273,276,280,283,286,289],[11,168,169],{},[14,170],{"alt":171,"height":172,"loading":18,"src":173,"width":20,"fetchPriority":21},"桌上的金屬鏈條、Planning Poker 卡片與咖啡杯",960,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.webp",[11,175,176],{},"衝刺裡經常包含相依的工作項目，可能在同一團隊內，也可能橫跨多個 Scrum 團隊。理想世界中不會有相依性；實際上，業務需求優先，為了縮短發佈週期而加入相依性。本文說明軟體團隊管理相依工作的一種方法。",[11,178,179],{},[14,180],{"alt":181,"height":182,"loading":37,"src":183,"width":182,"decoding":40},"工作之間的相依關係",336,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fblog-dep1.png",[11,185,186],{},[44,187,181],{},[26,189,190],{"id":190},"傳統做法",[11,192,193,194,96],{},"最直接的做法，是等工作項目的前置相依合併進主分支後，立刻開始這項工作。採用這種做法，有些團隊成員會閒著等某項工作就緒。最後，剩下的相依工作幾乎沒有時間可用。最後幾項工作被遺留，",[92,195,197],{"href":196},"\u002Fzh-TW\u002Fblog\u002Fcomparison-metrics-for-agile-teams","團隊也不開心",[11,199,200],{},"為什麼容量明明估算正確，還是會這樣？主要原因是等待同事完成時的閒置時間。即使小小的延誤也會累積，尤其是在短衝刺裡。",[26,202,203],{"id":203},"同時處理相依工作",[11,205,206],{},"有辦法做到，只需一點額外負擔。當團隊成員同時處理工作，有幾項好處。",[53,208,209],{"id":209},"更好的協作",[11,211,212],{},"當團隊成員同時處理相依工作，就有點像結對程式設計。一個人必須理解上游工作，另一個人必須理解下游工作。團隊對正在解決的問題會有更廣泛的認識。",[53,214,215],{"id":215},"避免閒置時間",[11,217,218],{},"當工作並行進行，沒有人需要等待修正落地。每個人都能同時作業，有問題時也能更即時地討論。",[53,220,222],{"id":221},"pull-request-更早準備好接受程式碼審查","Pull Request 更早準備好接受程式碼審查",[11,224,225],{},"當你的分支基於同事的分支，核准原本的 Pull Request 就更容易。你已經理解上游工作項目是怎麼實作的，而原本的分支在整個實作過程中都經過測試與審查。它不再是陌生的領域。",[26,227,229],{"id":228},"使用鏈式堆疊式pull-request","使用鏈式（堆疊式）Pull Request",[11,231,232],{},"這種程度的並行需要合適的工具。使用以 Git 為基礎的版本控制，實作起來很直接。以下步驟說明流程。",[11,234,235],{},[14,236],{"alt":237,"height":238,"loading":37,"src":239,"width":240,"decoding":40},"相依樹狀圖",438,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fdep-img2.png",800,[11,242,243],{},[44,244,245],{},"相依樹狀圖（同時處理 6 項相依工作）",[53,247,248],{"id":248},"清楚描繪相依關係",[11,250,251],{},"在衝刺規劃時定義相依鏈。Pull Request 鏈接著完全遵循這個定義。開發中途變更鏈結代價高昂，因為需要 Rebase。",[53,253,254],{"id":254},"先從根工作開始",[11,256,257],{},"每條相依鏈都有不依賴其他工作的根工作。這些工作從第一天就能開始。",[53,259,260],{"id":260},"先做核心實作",[11,262,263],{},"這可能與測試驅動開發（Test-Driven Development）衝突，因為那裡是先寫測試。為了讓 Pull Request 鏈易於管理，先實作核心。這樣相依的團隊成員能更早取得內容。",[53,265,266],{"id":266},"以先進先出佇列組織與審查程式碼",[11,268,269],{},"最先建立的分支應該最先被審查與合併。每次合併都會觸發 CI；如果它弄壞主建置，問題還小的時候就能修好。",[26,271,272],{"id":272},"額外負擔",[11,274,275],{},"維護一條相依分支鏈有好處，也有一些缺點。",[53,277,279],{"id":278},"rebase-或合併","Rebase 或合併",[11,281,282],{},"這條鏈必須保持同步，需要投入心力。現代工具提供一鍵與基底分支同步，前提是沒有衝突。在需要時使用，等安全時再拉入上游變更。當建置通過、功能正常時，就同步。",[53,284,285],{"id":285},"團隊合作",[11,287,288],{},"相依鏈需要一個願意彼此對話的協作團隊。如果大家各自閉門造車，就行不通。",[11,290,291],{},"相依的工作項目最好留在當前衝刺之外。當業務需求要求它們並行進行時，一條衍生分支鏈是管理相依負擔的實用方法。",{"title":125,"searchDepth":126,"depth":126,"links":293},[294,295,300,306],{"id":190,"depth":126,"text":190},{"id":203,"depth":126,"text":203,"children":296},[297,298,299],{"id":209,"depth":132,"text":209},{"id":215,"depth":132,"text":215},{"id":221,"depth":132,"text":222},{"id":228,"depth":126,"text":229,"children":301},[302,303,304,305],{"id":248,"depth":132,"text":248},{"id":254,"depth":132,"text":254},{"id":260,"depth":132,"text":260},{"id":266,"depth":132,"text":266},{"id":272,"depth":126,"text":272,"children":307},[308,309],{"id":278,"depth":132,"text":279},{"id":285,"depth":132,"text":285},"2018-05-27","相依的工作項目會讓人空等，拖住整個衝刺。了解堆疊式 Pull Request 如何讓工作持續流動、減少閒置時間。","以鏈式 Pull Request 管理衝刺相依性","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.jpg",[315,316,317,318,319],"衝刺相依性","堆疊式 Pull Request","鏈式 Pull Request","程式碼審查","敏捷交付",{},"\u002Fblog\u002Fzh-tw\u002Fmanage-sprint-dependencies-with-chained-pull-requests",{"title":164,"description":311},{"loc":321,"images":324,"lastmod":136},[325,326,327],{"loc":173},{"loc":183},{"loc":239},"manage-sprint-dependencies-with-chained-pull-requests","blog\u002Fzh-TW\u002Fmanage-sprint-dependencies-with-chained-pull-requests","5rcAKCONG69DRt00CrtjxkOMGJLiNUAPu6SeMzmXJsQ",{"id":332,"title":333,"author":6,"body":334,"dateModified":136,"datePublished":465,"description":466,"extension":139,"heading":467,"image":468,"imageAlt":340,"keywords":469,"locale":148,"meta":474,"navigation":150,"path":475,"reviewed":150,"seo":476,"sitemap":477,"slug":485,"stem":486,"translationKey":485,"__hash__":487},"blog\u002Fblog\u002Fzh-TW\u002Fsheepherding-story-points.md","羊群式故事點：Planning Poker 中的定錨效應 | AELBOX",{"type":8,"value":335,"toc":456},[336,342,345,348,355,362,366,369,372,375,382,386,389,392,395,400,404,407,410,417,421,424,427,432,436,439,450,453],[11,337,338],{},[14,339],{"alt":340,"height":172,"loading":18,"src":341,"width":20,"fetchPriority":21},"咖啡桌上的一群羊與 Planning Poker 卡片","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.webp",[11,343,344],{},"故事點估算經常被忽略，或是在聊天室與公開會議中進行，每個人都能看到或聽到每一票。知道別人怎麼投，會扭曲結果，產生不準確的估算。反覆不準確的估算會導致有缺陷的計畫，以及延誤或取消的交付。以下是公開投票時會發生的事。",[26,346,347],{"id":347},"投票中的角色",[11,349,350,351,354],{},"公開估算投票裡會出現幾種角色。估算結果取決於誰先投，而且通常離誠實很遠。為什麼順序在公開投票中如此重要？因為",[75,352,353],{},"羊群效應","：一種定錨偏誤，讓其他團隊成員複製第一個估算。",[11,356,357],{},[14,358],{"alt":353,"height":359,"loading":37,"src":360,"width":361,"decoding":40},746,"\u002Fblog\u002Fsheepherding-story-points\u002Fsheep-1.png",1779,[11,363,364],{},[44,365,353],{},[53,367,368],{"id":368},"過度自信的投票者",[11,370,371],{},"每個團隊至少有一位成員認為自己最懂系統。他們通常最先投票，因為答案對他們來說顯而易見。他們常忽略可能讓估算失準的細節。這些細節可以事先被挖掘出來，但前提是有人開啟討論。公開投票時這不可能發生。",[11,373,374],{},"這個人通常投得比誠實估算更低。也許只有他們能那麼快完成這個故事，而且還得靠運氣。",[11,376,377],{},[14,378],{"alt":368,"height":379,"loading":37,"src":380,"width":381,"decoding":40},290,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg7.png",600,[11,383,384],{},[44,385,368],{},[11,387,388],{},"其他人跟著投，於是工作看起來輕鬆，任何人都能在規定時間內完成。實際上，最後通常是別人來做。",[53,390,391],{"id":391},"沉默的投票者",[11,393,394],{},"沉默的投票者通常不只一位，他們害怕先投。他們等別人先投，好照抄。他們很少參與討論，只有被問到才回答。他們第二個投，就在心不在焉的投票者之前。",[11,396,397],{},[14,398],{"alt":391,"height":379,"loading":37,"src":399,"width":381,"decoding":40},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg5.png",[11,401,402],{},[44,403,391],{},[53,405,406],{"id":406},"心不在焉的投票者",[11,408,409],{},"他們在實作期間很難捉摸，但投票時行為很明顯。他們總是最後投，抄別人的估算。如果估算不同，他們就挑最常見的那個。他們不想解釋為什麼選了較低或較高的數字，所以避免在需求梳理時協作，也迴避問題。",[11,411,412],{},[14,413],{"alt":406,"height":414,"loading":37,"src":415,"width":416,"decoding":40},353,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg4.png",758,[11,418,419],{},[44,420,406],{},[53,422,423],{"id":423},"疲倦的投票者",[11,425,426],{},"有些團隊成員無法長時間保持專注，錯過討論的關鍵部分。他們失去脈絡，只能猜，或尋找最常見的票來抄。",[11,428,429],{},[14,430],{"alt":423,"height":379,"loading":37,"src":431,"width":381,"decoding":40},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg6.png",[11,433,434],{},[44,435,423],{},[26,437,438],{"id":438},"如何在估算時保持專注",[11,440,441,442,446,447,449],{},"估算很重要，因為只有誠實的故事點才能",[92,443,445],{"href":444},"\u002Fzh-TW\u002Fblog\u002Fcorrectly-estimating-release-deadline","讓專案朝著發佈日期前進","。誠實估算的關鍵，在於對抗",[75,448,353],{},"，無論你用的是紙牌還是軟體。",[11,451,452],{},"在主持人揭曉之前，團隊成員不應該看到彼此的估算。這樣一來，沉默的投票者開始思考，心不在焉的投票者產生興趣，疲倦的投票者也會醒過來。最該問的問題，尤其是有人與團體意見不同時，是「為什麼你投 X 個故事點？」這會開啟一場關於實際實作問題的對話。「你同意 X 個故事點嗎？」這類封閉式問題，只會換來毫無意義的「同意」。",[11,454,455],{},"好的估算工具能讓需求梳理更有參與感，讓每個人保持警覺、隨時準備討論，即使是複雜的故事也能得到更好的估算。",{"title":125,"searchDepth":126,"depth":126,"links":457},[458,464],{"id":347,"depth":126,"text":347,"children":459},[460,461,462,463],{"id":368,"depth":132,"text":368},{"id":391,"depth":132,"text":391},{"id":406,"depth":132,"text":406},{"id":423,"depth":132,"text":423},{"id":438,"depth":126,"text":438},"2018-04-30","公開投票會讓第一個估算定錨全場。看看羊群效應如何扭曲故事點，以及如何誠實地進行 Planning Poker。","羊群式故事點","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.jpg",[470,471,472,353,473],"故事點","Planning Poker","定錨偏誤","敏捷估算",{},"\u002Fblog\u002Fzh-tw\u002Fsheepherding-story-points",{"title":333,"description":466},{"loc":475,"images":478,"lastmod":136},[479,480,481,482,483,484],{"loc":341},{"loc":360},{"loc":380},{"loc":399},{"loc":415},{"loc":431},"sheepherding-story-points","blog\u002Fzh-TW\u002Fsheepherding-story-points","phQlyJL9VUBC9K6Z0NTvpWsb5BmElopIc_ypWAg0qFg",{"id":489,"title":490,"author":6,"body":491,"dateModified":136,"datePublished":561,"description":562,"extension":139,"heading":563,"image":564,"imageAlt":497,"keywords":565,"locale":148,"meta":570,"navigation":150,"path":571,"reviewed":150,"seo":572,"sitemap":573,"slug":578,"stem":579,"translationKey":578,"__hash__":580},"blog\u002Fblog\u002Fzh-TW\u002Fthe-10-percent-scrumban-rule-for-every-sprint.md","每個衝刺都適用的 10% Scrumban 法則 | AELBOX",{"type":8,"value":492,"toc":556},[493,500,508,511,514,522,526,529,532,535,538,541,549,553],[11,494,495],{},[14,496],{"alt":497,"height":498,"loading":18,"src":499,"width":20,"fetchPriority":21},"咖啡桌上的 Planning Poker 卡片與看板",959,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fcoffee-table-scrumban.webp",[11,501,502,503,507],{},"許多團隊規劃時，會把 Jira 計畫中顯示的容量用得剛剛好。這往往是錯誤，會導致衝刺失敗。既然",[92,504,506],{"href":505},"\u002Fzh-TW\u002Fblog\u002Fthe-importance-of-predictable-velocity","容量計算","看起來那麼精確，為什麼還會這樣？",[26,509,510],{"id":510},"急著交付更多",[11,512,513],{},"產品負責人往往在每個成功的衝刺之後，就推動更高的速度，這是對最新結果的自然反應。如果團隊上個衝刺完成了一定數量的故事點，下個衝刺就被期待完成更多。這會不斷重複，直到某個衝刺失敗。這種催促是為了測試團隊的極限。根據我們的經驗，這適得其反。它最終會打擊團隊士氣，讓大家覺得未來的每個衝刺都注定失敗。",[11,515,516],{},[14,517],{"alt":518,"height":519,"loading":37,"src":520,"width":521,"decoding":40},"注定失敗的衝刺",349,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg1.png",400,[11,523,524],{},[44,525,518],{},[26,527,528],{"id":528},"交付衝刺期間手忙腳亂的尾聲",[11,530,531],{},"當容量被規劃到剛好填滿衝刺，任何延誤或成真的風險，都會在最後造成瘋狂趕工的壓力。團隊在高壓下反而交付得比承諾更少。這種衝刺尾聲的趕工應該被消除。",[26,533,534],{"id":534},"讓團隊自願交付更多",[11,536,537],{},"只規劃團隊容量的 90%，把剩下的 10% 留給未規劃的待辦事項工作。這些工作會在衝刺期間以 Scrumban 的方式從待辦事項拉進來。緩衝能吸收風險，讓團隊提早幾天完成衝刺（至少完成衝刺目標）。如果外部相依性威脅到衝刺，有緩衝的工作可以取代出問題的那一項。",[11,539,540],{},"那 10% 不屬於衝刺承諾。如果風險沒有成真，團隊就把它當成額外工作交付；如果出了問題，緩衝被用掉，但衝刺目標與承諾仍然達成。要追蹤緩衝用了多少：如果它經常達到 20%，例如，那就是時候在保留 10% 緩衝的前提下，把團隊速度提高 10%。",[11,542,543],{},[14,544],{"alt":545,"height":546,"loading":37,"src":547,"width":548,"decoding":40},"提早交付，額外交付",320,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg3-1.png",296,[11,550,551],{},[44,552,545],{},[11,554,555],{},"我們的經驗顯示，這正是員工在沒有壓力時工作、貢獻最多的時候。速度接著能依團隊自己的步調成長，沒有外部壓力，壓力也更小。這種成長感覺自然且可持續。",{"title":125,"searchDepth":126,"depth":126,"links":557},[558,559,560],{"id":510,"depth":126,"text":510},{"id":528,"depth":126,"text":528},{"id":534,"depth":126,"text":534},"2018-04-28","把容量排到滿，只會讓每個衝刺都很脆弱。10% 的 Scrumban 緩衝能吸收風險、守住衝刺目標，讓速度自然成長。","每個衝刺都適用的 10% Scrumban 法則","\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fcoffee-table-scrumban.jpg",[566,567,568,569,146],"Scrumban","衝刺容量","敏捷緩衝","速度",{},"\u002Fblog\u002Fzh-tw\u002Fthe-10-percent-scrumban-rule-for-every-sprint",{"title":490,"description":562},{"loc":571,"images":574,"lastmod":136},[575,576,577],{"loc":499},{"loc":520},{"loc":547},"the-10-percent-scrumban-rule-for-every-sprint","blog\u002Fzh-TW\u002Fthe-10-percent-scrumban-rule-for-every-sprint","xfbzmcVowwtewaX_SmGZ8cQd3SF0k6165RFNqMbElcE",{"id":582,"title":583,"body":584,"dateModified":853,"datePublished":854,"description":855,"extension":139,"heading":723,"image":856,"imageAlt":723,"keywords":857,"locale":148,"meta":858,"navigation":150,"order":859,"path":860,"section":861,"seo":862,"sitemap":863,"slug":864,"stem":865,"translationKey":866,"__hash__":867},"guide\u002Fguide\u002Fzh-TW\u002Faudit-logs-and-dashboards.md","稽核記錄與儀表板 | Scrumpy Planning Poker",{"type":8,"value":585,"toc":844},[586,589,592,595,600,603,625,628,666,673,676,683,686,691,705,714,717,720,725,728,738,741,799,806,809,815,832,835,838,841],[11,587,588],{},"Scrumpy 會維護兩套獨立的稽核軌跡，以提供完整的透明度與合規性。稽核、儀表板、聊天與估算歷史中的每個時間戳記，都會以你的 Jira 時區顯示。",[11,590,591],{},"稽核分頁與空間設定中的儀表板位於空間設定中。你需要有在 Jira 中管理該空間的權限才能開啟它們，且資料載入時會再次檢查該權限。只要能開啟工作項目面板並不足夠。空間估算頁面上較輕量的儀表板可供任何能開啟該頁面的人使用，且只會計入你能在 Jira 中開啟的工作項目。",[26,593,594],{"id":594},"投票稽核",[11,596,597,599],{},[75,598,594],{},"分頁會顯示空間中投票會話所有重要事件的時間順序記錄。",[11,601,602],{},"記錄的事件包括：",[604,605,606,610,613,616,619,622],"ul",{},[607,608,609],"li",{},"會話已建立、已投票、已暫停、已繼續、已完成、已取消",[607,611,612],{},"估算由主持人設定或修改",[607,614,615],{},"必要投票者已更新",[607,617,618],{},"非同步完成截止時間已設定或清除",[607,620,621],{},"估算已接受並寫入 Jira",[607,623,624],{},"已向尚未投票的參與者傳送提醒",[11,626,627],{},"每個事件會顯示：",[604,629,630,636,642,648,654,660],{},[607,631,632,635],{},[75,633,634],{},"發生時間","：事件的時間戳記",[607,637,638,641],{},[75,639,640],{},"類型","：工作項目類型的圖示，包括較新與自訂類型",[607,643,644,647],{},[75,645,646],{},"工作項目","：可點選的工作項目金鑰，會在對話方塊中開啟工作項目",[607,649,650,653],{},[75,651,652],{},"觀點","：使用了哪個估算觀點",[607,655,656,659],{},[75,657,658],{},"操作者","：觸發事件的使用者",[607,661,662,665],{},[75,663,664],{},"描述","：發生什麼事的人類可讀摘要",[11,667,668,669,672],{},"輸入搜尋詞並按一下",[75,670,671],{},"搜尋","，即可依工作項目金鑰、觀點或描述篩選。選擇每頁 15、30、45 或 60 列，並使用分頁控制項瀏覽大量歷史記錄。",[11,674,675],{},"投票稽核只會列出你能在 Jira 中開啟的工作項目。被問題層級安全性對你隱藏的問題事件會略過，也不會計入頁面總數。",[11,677,678,679,682],{},"只有空間擁有者可以刪除投票稽核記錄。如果你能開啟空間設定但不是空間擁有者，",[75,680,681],{},"刪除稽核記錄","按鈕會替換為說明此事的附註。當你是空間擁有者時，會先顯示確認對話方塊，且刪除後無法復原。",[26,684,685],{"id":685},"設定稽核",[11,687,688,690],{},[75,689,685],{},"分頁會追蹤對空間權限與觀點設定所做的每一項變更。每個項目會記錄：",[604,692,693,696,699,702],{},[607,694,695],{},"誰做了變更",[607,697,698],{},"變更了什麼（附有人類可讀的描述）",[607,700,701],{},"何時做了變更",[607,703,704],{},"影響了哪個觀點（如適用）",[11,706,707,708,710,711,713],{},"與投票稽核相同，此表格可使用",[75,709,671],{},"按鈕搜尋，並使用相同的每頁筆數選取器分頁。只有空間擁有者可以使用",[75,712,681],{},"動作清除它。其他使用者會看到附註，而不是按鈕。",[26,715,716],{"id":716},"儀表板",[11,718,719],{},"Scrumpy 有兩個用途不同的儀表板。",[721,722],"docs-figure",{"alt":723,"caption":723,"stem":724},"稽核記錄與儀表板","guide-dashboard",[53,726,727],{"id":727},"空間設定儀表板",[11,729,730,731,733,734,737],{},"空間設定中的",[75,732,716],{},"分頁提供完整分析檢視。使用範圍選取器選擇 1、2、4 或 8 週，或",[75,735,736],{},"全部時間","。你的選擇會保留到下次。全部時間仍限制在 90 天保留期間內，且圖表會在接受新估算時更新。",[11,739,740],{},"顯示的圖表：",[604,742,743,750,755,761,766,772,778,783,788,793],{},[607,744,745,746,749],{},"依觀點的",[75,747,748],{},"總投票數","（環圈圖）",[607,751,745,752,749],{},[75,753,754],{},"總估算數",[607,756,745,757,760],{},[75,758,759],{},"平均一致性","（長條圖）",[607,762,745,763,760],{},[75,764,765],{},"平均變異",[607,767,745,768,771],{},[75,769,770],{},"平均持續時間","（堆疊進行中與暫停時間，以秒或分鐘顯示）",[607,773,774,777],{},[75,775,776],{},"每日總估算數","（折線圖）",[607,779,780,777],{},[75,781,782],{},"每日平均投票者數",[607,784,785,760],{},[75,786,787],{},"每日平均一致性",[607,789,790,760],{},[75,791,792],{},"每日平均變異",[607,794,795,798],{},[75,796,797],{},"每日總持續時間（分鐘）","（堆疊）",[11,800,801,802,805],{},"只有空間擁有者可以使用分頁底部的",[75,803,804],{},"刪除估算記錄","刪除所有已接受的會話記錄。刪除前會先顯示確認，且刪除後無法復原。",[53,807,808],{"id":808},"估算頁面儀表板",[11,810,811,812,814],{},"空間估算頁面上的",[75,813,716],{},"分頁是較輕量的即時概覽，包含三張圖表，沒有時間篩選器或刪除動作：",[604,816,817,822,827],{},[607,818,819],{},[75,820,821],{},"依觀點的進行中會話",[607,823,824],{},[75,825,826],{},"依觀點的不重複投票者",[607,828,829],{},[75,830,831],{},"依觀點的會話狀態",[11,833,834],{},"沒有可顯示的內容時，每張圖表會顯示自己的空白狀態。圖表下方，頭像會顯示任何進行中會話中投過票的所有人。即使尚無人投票，頭像列也會保留位置，因此參與者出現時圖表不會移動。你已在另一個分頁查看過的會話會立即出現，圖表也會在空間其餘會話於背景載入時更新。",[26,836,837],{"id":837},"資料保留",[11,839,840],{},"Scrumpy 會將投票稽核項目、設定稽核項目、已接受的估算與規劃會議保留三個月（90 天）。較舊的資料會每天自動移除。聊天訊息會保留 72 小時。空間擁有者也可以從各自的分頁刪除所有稽核項目與估算記錄；這些刪除後無法復原。",[11,842,843],{},"空間設定會保留到你變更為止。這包括投票密碼、投票者與主持人清單，以及每個觀點設定。90 天保留期間不會移除它們，因此受保護的空間會保持受保護，團隊也會保留其角色。",{"title":125,"searchDepth":126,"depth":126,"links":845},[846,847,848,852],{"id":594,"depth":126,"text":594},{"id":685,"depth":126,"text":685},{"id":716,"depth":126,"text":716,"children":849},[850,851],{"id":727,"depth":132,"text":727},{"id":808,"depth":132,"text":808},{"id":837,"depth":126,"text":837},"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":583,"description":855},{"loc":860,"lastmod":853},"audit-logs-and-dashboards","guide\u002Fzh-TW\u002Faudit-logs-and-dashboards","guide\u002Faudit-logs-and-dashboards","aUeGsECz3S6DLYCg5a0IFBAdKkJ7IwngAxDKHMgxu1Q",1795345554390]