[{"data":1,"prerenderedAt":742},["ShallowReactive",2],{"blog-zh-TW-sheepherding-story-points":3,"blog-related-zh-TW-sheepherding-story-points":182,"blog-chapter-zh-TW-sheepherding-story-points":581},{"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-TW\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-TW\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-TW",{},true,"\u002Fblog\u002Fzh-tw\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-TW\u002Fsheepherding-story-points","phQlyJL9VUBC9K6Z0NTvpWsb5BmElopIc_ypWAg0qFg",[183,352,488],{"id":184,"title":185,"author":6,"body":186,"dateModified":155,"datePublished":331,"description":332,"extension":158,"heading":333,"image":334,"imageAlt":192,"keywords":335,"locale":166,"meta":341,"navigation":168,"path":342,"reviewed":168,"seo":343,"sitemap":344,"slug":349,"stem":350,"translationKey":349,"__hash__":351},"blog\u002Fblog\u002Fzh-TW\u002Fmanage-sprint-dependencies-with-chained-pull-requests.md","衝刺相依性與鏈式 Pull Request | AELBOX",{"type":8,"value":187,"toc":313},[188,194,197,204,208,211,219,222,225,228,231,234,237,240,244,247,251,254,262,267,270,273,276,279,282,285,288,291,294,297,301,304,307,310],[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,218],{},"最直接的做法，是等工作項目的前置相依合併進主分支後，立刻開始這項工作。採用這種做法，有些團隊成員會閒著等某項工作就緒。最後，剩下的相依工作幾乎沒有時間可用。最後幾項工作被遺留，",[129,215,217],{"href":216},"\u002Fzh-TW\u002Fblog\u002Fcomparison-metrics-for-agile-teams","團隊也不開心","。",[11,220,221],{},"為什麼容量明明估算正確，還是會這樣？主要原因是等待同事完成時的閒置時間。即使小小的延誤也會累積，尤其是在短衝刺裡。",[26,223,224],{"id":224},"同時處理相依工作",[11,226,227],{},"有辦法做到，只需一點額外負擔。當團隊成員同時處理工作，有幾項好處。",[52,229,230],{"id":230},"更好的協作",[11,232,233],{},"當團隊成員同時處理相依工作，就有點像結對程式設計。一個人必須理解上游工作，另一個人必須理解下游工作。團隊對正在解決的問題會有更廣泛的認識。",[52,235,236],{"id":236},"避免閒置時間",[11,238,239],{},"當工作並行進行，沒有人需要等待修正落地。每個人都能同時作業，有問題時也能更即時地討論。",[52,241,243],{"id":242},"pull-request-更早準備好接受程式碼審查","Pull Request 更早準備好接受程式碼審查",[11,245,246],{},"當你的分支基於同事的分支，核准原本的 Pull Request 就更容易。你已經理解上游工作項目是怎麼實作的，而原本的分支在整個實作過程中都經過測試與審查。它不再是陌生的領域。",[26,248,250],{"id":249},"使用鏈式堆疊式pull-request","使用鏈式（堆疊式）Pull Request",[11,252,253],{},"這種程度的並行需要合適的工具。使用以 Git 為基礎的版本控制，實作起來很直接。以下步驟說明流程。",[11,255,256],{},[14,257],{"alt":258,"height":259,"loading":42,"src":260,"width":261,"decoding":45},"相依樹狀圖",438,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fdep-img2.png",800,[11,263,264],{},[49,265,266],{},"相依樹狀圖（同時處理 6 項相依工作）",[52,268,269],{"id":269},"清楚描繪相依關係",[11,271,272],{},"在衝刺規劃時定義相依鏈。Pull Request 鏈接著完全遵循這個定義。開發中途變更鏈結代價高昂，因為需要 Rebase。",[52,274,275],{"id":275},"先從根工作開始",[11,277,278],{},"每條相依鏈都有不依賴其他工作的根工作。這些工作從第一天就能開始。",[52,280,281],{"id":281},"先做核心實作",[11,283,284],{},"這可能與測試驅動開發（Test-Driven Development）衝突，因為那裡是先寫測試。為了讓 Pull Request 鏈易於管理，先實作核心。這樣相依的團隊成員能更早取得內容。",[52,286,287],{"id":287},"以先進先出佇列組織與審查程式碼",[11,289,290],{},"最先建立的分支應該最先被審查與合併。每次合併都會觸發 CI；如果它弄壞主建置，問題還小的時候就能修好。",[26,292,293],{"id":293},"額外負擔",[11,295,296],{},"維護一條相依分支鏈有好處，也有一些缺點。",[52,298,300],{"id":299},"rebase-或合併","Rebase 或合併",[11,302,303],{},"這條鏈必須保持同步，需要投入心力。現代工具提供一鍵與基底分支同步，前提是沒有衝突。在需要時使用，等安全時再拉入上游變更。當建置通過、功能正常時，就同步。",[52,305,306],{"id":306},"團隊合作",[11,308,309],{},"相依鏈需要一個願意彼此對話的協作團隊。如果大家各自閉門造車，就行不通。",[11,311,312],{},"相依的工作項目最好留在當前衝刺之外。當業務需求要求它們並行進行時，一條衍生分支鏈是管理相依負擔的實用方法。",{"title":144,"searchDepth":145,"depth":145,"links":314},[315,316,321,327],{"id":210,"depth":145,"text":210},{"id":224,"depth":145,"text":224,"children":317},[318,319,320],{"id":230,"depth":150,"text":230},{"id":236,"depth":150,"text":236},{"id":242,"depth":150,"text":243},{"id":249,"depth":145,"text":250,"children":322},[323,324,325,326],{"id":269,"depth":150,"text":269},{"id":275,"depth":150,"text":275},{"id":281,"depth":150,"text":281},{"id":287,"depth":150,"text":287},{"id":293,"depth":145,"text":293,"children":328},[329,330],{"id":299,"depth":150,"text":300},{"id":306,"depth":150,"text":306},"2018-05-27","相依的工作項目會讓人空等，拖住整個衝刺。了解堆疊式 Pull Request 如何讓工作持續流動、減少閒置時間。","以鏈式 Pull Request 管理衝刺相依性","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.jpg",[336,337,338,339,340],"衝刺相依性","堆疊式 Pull Request","鏈式 Pull Request","程式碼審查","敏捷交付",{},"\u002Fblog\u002Fzh-tw\u002Fmanage-sprint-dependencies-with-chained-pull-requests",{"title":185,"description":332},{"loc":342,"images":345,"lastmod":155},[346,347,348],{"loc":193},{"loc":203},{"loc":260},"manage-sprint-dependencies-with-chained-pull-requests","blog\u002Fzh-TW\u002Fmanage-sprint-dependencies-with-chained-pull-requests","5rcAKCONG69DRt00CrtjxkOMGJLiNUAPu6SeMzmXJsQ",{"id":353,"title":354,"author":6,"body":355,"dateModified":155,"datePublished":467,"description":468,"extension":158,"heading":469,"image":470,"imageAlt":361,"keywords":471,"locale":166,"meta":477,"navigation":168,"path":478,"reviewed":168,"seo":479,"sitemap":480,"slug":485,"stem":486,"translationKey":485,"__hash__":487},"blog\u002Fblog\u002Fzh-TW\u002Fcomparison-metrics-for-agile-teams.md","敏捷團隊的比較指標 | AELBOX",{"type":8,"value":356,"toc":458},[357,364,367,370,373,380,384,387,390,393,396,404,408,415,418,421,424,431,435,438,445,448,452,455],[11,358,359],{},[14,360],{"alt":361,"height":362,"loading":18,"src":363,"width":20,"fetchPriority":21},"桌上的直尺、Planning Poker 卡片與咖啡杯",958,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.webp",[11,365,366],{},"比較敏捷團隊很困難，而我們也該問問，為什麼要比較。把不同領域的團隊拿來比較，究竟有什麼幫助？",[26,368,369],{"id":369},"創造競爭",[11,371,372],{},"團隊不應該用任意的指標互相排名。那只會打擊士氣。相對地，指標應該給每個團隊公平競爭的機會。績效會因為團隊自己想要而提升，而不是因為有人在後面推。",[11,374,375],{},[14,376],{"alt":369,"height":377,"loading":42,"src":378,"width":379,"decoding":45},487,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun2.png",525,[11,381,382],{},[49,383,369],{},[26,385,386],{"id":386},"創造公平機會的指標",[11,388,389],{},"以下是四項比較團隊的基本指標。它們衡量每個團隊在公平立足點上競爭的能力，僅此而已。可比較的指標創造公平的機會。",[52,391,392],{"id":392},"成功的衝刺",[11,394,395],{},"如果衝刺只是一個時間框架，那就毫無意義。衝刺是一個里程碑，需要目標。衝刺目標（最重要的一組故事）是較大的里程碑，完成每一個故事則是較小的里程碑。在每個衝刺結束時舉辦跨團隊展示，讓各團隊呈現自己交付了什麼。這種良性競爭會鼓勵團隊完成衝刺目標。人需要看得見的目標才會被激勵。",[11,397,398],{},[14,399],{"alt":400,"height":401,"loading":42,"src":402,"width":403,"decoding":45},"朝目標衝刺",680,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun1.png",874,[11,405,406],{},[49,407,400],{},[11,409,410,411,414],{},"這會不會變成過度承諾與承諾不足的遊戲？如果團隊承諾不足，展示會讓一切無所遁形：能秀的東西變少了。如果過度承諾，展示就變成",[33,412,413],{},"又一次失敗的衝刺","。交付團隊所承諾的事，會建立做得更多的動力。團隊會對工作感到滿意。",[52,416,417],{"id":417},"速度穩定性與誠實估算",[11,419,420],{},"這是知識工作，不是生產線作業。如果團隊裡沒有人真正理解某個問題、足以估算它的解法，那代表這個問題沒有事先研究。",[11,422,423],{},"在上一個衝刺安排一個限時的 Spike，接著由團隊檢視研究結果，就能輕鬆把實作拆成更小的故事，妥善估算。對於複雜的工作，寫一份更完整的技術設計文件，列出實作故事。",[11,425,426,427,218],{},"Spike 與設計工作本身就是可以估算的故事。關鍵在於為複雜解法定義工作的結構與順序。與其承諾一個團隊不懂的故事，不如建立一項研究型工作來補上缺口。這樣估算才能",[129,428,430],{"href":429},"\u002Fzh-TW\u002Fblog\u002Fsheepherding-story-points","以證據為基礎",[52,432,434],{"id":433},"容量可預測性避免意料之外的工作","容量可預測性（避免意料之外的工作）",[11,436,437],{},"研究先行，實作隨後。當研究發現問題，就建立新的工作項目並估算。你接著會對下一個衝刺有更清楚的圖像。已知的工作可以估算與規劃；未知的工作則先取得一個限時的研究工作項目，再進行估算。這項紀律就是把大型工作拆成小而可估算的片段。",[11,439,440,441,218],{},"複雜的工作可以提早開始，即使只是為了發現它需要自己的一組故事。這仍然能降低",[129,442,444],{"href":443},"\u002Fzh-TW\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint","未知的風險",[11,446,447],{},"支援與生產救火通常以限時的看板流程在衝刺之外進行。在那裡，首次回應時間與 SLA 違約就成了比較指標。",[52,449,451],{"id":450},"團隊可用度投入工作的時間除以衝刺總時間","團隊可用度（投入工作的時間除以衝刺總時間）",[11,453,454],{},"可用度是團隊成員花在已估算工作上的時間比例。如果某個團隊比其他團隊更常被拉去訓練、知識分享或其他內部工作，就要修正這個失衡。維持速度穩定的唯一方法，就是維持可用度穩定。當團隊之間的可用度相等，其他比較指標才會奏效。",[11,456,457],{},"比較團隊不是為了懲罰低績效，而是為了提高動力，以及競爭與交付更多的精神。這也是為什麼這些指標不應該讓個別團隊成員看到：它們是輔導的工具，不是公開的排行榜。透過追蹤這些指標、間接引導 Scrum Master，你就能讓團隊站在平等的立足點上競爭。",{"title":144,"searchDepth":145,"depth":145,"links":459},[460,461],{"id":369,"depth":145,"text":369},{"id":386,"depth":145,"text":386,"children":462},[463,464,465,466],{"id":392,"depth":150,"text":392},{"id":417,"depth":150,"text":417},{"id":433,"depth":150,"text":434},{"id":450,"depth":150,"text":451},"2018-05-04","指標應該創造公平的立足點，而不是排行榜。四種能激勵敏捷團隊、又不會懲罰他們的比較指標。","敏捷團隊的比較指標","\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.jpg",[472,473,474,475,476],"敏捷指標","團隊速度","敏捷團隊","Scrum","容量",{},"\u002Fblog\u002Fzh-tw\u002Fcomparison-metrics-for-agile-teams",{"title":354,"description":468},{"loc":478,"images":481,"lastmod":155},[482,483,484],{"loc":363},{"loc":378},{"loc":402},"comparison-metrics-for-agile-teams","blog\u002Fzh-TW\u002Fcomparison-metrics-for-agile-teams","02GYIXumbgYlagHSXkvZT1etbyroF2QAtzOmofeHoE0",{"id":489,"title":490,"author":6,"body":491,"dateModified":155,"datePublished":561,"description":562,"extension":158,"heading":563,"image":564,"imageAlt":497,"keywords":565,"locale":166,"meta":570,"navigation":168,"path":571,"reviewed":168,"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 計畫中顯示的容量用得剛剛好。這往往是錯誤，會導致衝刺失敗。既然",[129,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":42,"src":520,"width":521,"decoding":45},"注定失敗的衝刺",349,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg1.png",400,[11,523,524],{},[49,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":42,"src":547,"width":548,"decoding":45},"提早交付，額外交付",320,"\u002Fblog\u002Fthe-10-percent-scrumban-rule-for-every-sprint\u002Fimg3-1.png",296,[11,550,551],{},[49,552,545],{},[11,554,555],{},"我們的經驗顯示，這正是員工在沒有壓力時工作、貢獻最多的時候。速度接著能依團隊自己的步調成長，沒有外部壓力，壓力也更小。這種成長感覺自然且可持續。",{"title":144,"searchDepth":145,"depth":145,"links":557},[558,559,560],{"id":510,"depth":145,"text":510},{"id":528,"depth":145,"text":528},{"id":534,"depth":145,"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,475],"Scrumban","衝刺容量","敏捷緩衝","速度",{},"\u002Fblog\u002Fzh-tw\u002Fthe-10-percent-scrumban-rule-for-every-sprint",{"title":490,"description":562},{"loc":571,"images":574,"lastmod":155},[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":728,"datePublished":728,"description":729,"extension":158,"heading":634,"image":730,"imageAlt":634,"keywords":731,"locale":166,"meta":732,"navigation":168,"order":733,"path":734,"section":735,"seo":736,"sitemap":737,"slug":738,"stem":739,"translationKey":740,"__hash__":741},"guide\u002Fguide\u002Fzh-TW\u002Fwhat-is-story-point-estimation.md","什麼是故事點估算？ | Scrumpy Planning Poker",{"type":8,"value":585,"toc":723},[586,592,596,624,628,631,636,654,658,661],[11,587,588,589,591],{},"故事點估算是一種協作技巧，敏捷團隊用它來估算完成工作項目所需的投入。團隊不以小時或天數估算，而是使用稱為",[33,590,162],{},"的抽象單位，代表工作的相對複雜度、投入與不確定性。",[26,593,595],{"id":594},"為什麼使用故事點","為什麼使用故事點？",[597,598,599,606,612,618],"ul",{},[600,601,602,605],"li",{},[33,603,604],{},"相對大小","：說「這項工作比那項難兩倍」比猜測確切小時數容易",[600,607,608,611],{},[33,609,610],{},"團隊校準","：點數由團隊定義、為團隊而設，並以共同經驗為基礎",[600,613,614,617],{},[33,615,616],{},"速度追蹤","：隨著時間推移，團隊會了解每個衝刺能完成多少點數，進而做出更準確的預測",[600,619,620,623],{},[33,621,622],{},"減少錨定","：抽象單位可避免以時間估算帶來的情緒包袱",[26,625,627],{"id":626},"planning-poker-的運作方式","Planning Poker 的運作方式",[11,629,630],{},"Planning Poker 是一種以共識為基礎的估算技巧。團隊成員先私下選出代表估算值的卡片，再同時揭曉，以避免錨定偏誤。",[632,633],"docs-figure",{"alt":634,"caption":634,"stem":635},"什麼是故事點估算？","guide-voting-cards",[637,638,639,642,645,648,651],"ol",{},[600,640,641],{},"提出一個工作項目進行估算",[600,643,644],{},"每位團隊成員私下選出卡片值",[600,646,647],{},"同時揭曉投票",[600,649,650],{},"團隊討論差異，並可重新投票",[600,652,653],{},"接受並記錄最終估算",[26,655,657],{"id":656},"scrumpy-的角色","Scrumpy 的角色",[11,659,660],{},"Scrumpy 在 Jira 中自動化這個流程。它提供：",[597,662,663,669,675,681,687,693,699,705,711,717],{},[600,664,665,668],{},[33,666,667],{},"多個估算觀點","：從不同角度估算同一個工作項目（複雜度、時間、風險）",[600,670,671,674],{},[33,672,673],{},"即時投票","：團隊成員送出投票時，立即看到投票出現",[600,676,677,680],{},[33,678,679],{},"即時回饋","：你做的變更會立即顯示；如果無法儲存，先前的狀態會恢復",[600,682,683,686],{},[33,684,685],{},"自動計算結果","：可設定的平均方法會計算最終估算",[600,688,689,692],{},[33,690,691],{},"一致性訊號","：以百分比顯示參與者維持原本投票而非重新投票的頻率",[600,694,695,698],{},[33,696,697],{},"變異訊號","：以百分比顯示投票值圍繞平均值的分散程度",[600,700,701,704],{},[33,702,703],{},"必要投票者與提醒","：選擇誰必須投票，並提醒尚未投票的人",[600,706,707,710],{},[33,708,709],{},"非同步投票","：讓參與者依自己的步調投票，並可設定截止時間",[600,712,713,716],{},[33,714,715],{},"內建聊天","：在會話期間討論估算並回應訊息",[600,718,719,722],{},[33,720,721],{},"Jira 整合","：已接受的估算會直接寫入你的 Jira 看板或自訂欄位",{"title":144,"searchDepth":145,"depth":145,"links":724},[725,726,727],{"id":594,"depth":145,"text":595},{"id":626,"depth":145,"text":627},{"id":656,"depth":145,"text":657},"2026-11-10","故事點估算是一種協作技巧，敏捷團隊用它來估算完成工作項目所需的投入。 團隊不以小時或天數估算，而是使用稱為故事點的抽象單位，代表工作的相對複雜度、投入與不確定性。 Planning Poker 是一種以共識為基礎的估算技巧。 團隊成員先私下選出代表估算值的卡片，再同時揭曉，以避免錨定偏誤。","\u002Fog\u002Fguide-what-is-story-point-estimation.jpg",[],{},1,"\u002Fgetting-started\u002Fwhat-is-story-point-estimation","guide",{"title":583,"description":729},{"loc":734,"lastmod":728},"what-is-story-point-estimation","guide\u002Fzh-TW\u002Fwhat-is-story-point-estimation","guide\u002Fwhat-is-story-point-estimation","r1IhJFNfeGscmk-C2NA_JVArTY2rGVkHmYiKkCfbVLI",1795345554488]