[{"data":1,"prerenderedAt":850},["ShallowReactive",2],{"blog-zh-TW-the-importance-of-predictable-velocity":3,"blog-related-zh-TW-the-importance-of-predictable-velocity":190,"blog-chapter-zh-TW-the-importance-of-predictable-velocity":650},{"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-TW\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-TW\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-TW\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-TW\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-TW",{},true,"\u002Fblog\u002Fzh-tw\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-TW\u002Fthe-importance-of-predictable-velocity","7McazWrfhk2Nl5jRkx7oJNaz7mi68rT6gQje5_wiOGM",[191,360,495],{"id":192,"title":193,"author":6,"body":194,"dateModified":164,"datePublished":339,"description":340,"extension":167,"heading":341,"image":342,"imageAlt":200,"keywords":343,"locale":176,"meta":349,"navigation":178,"path":350,"reviewed":178,"seo":351,"sitemap":352,"slug":357,"stem":358,"translationKey":357,"__hash__":359},"blog\u002Fblog\u002Fzh-TW\u002Fmanage-sprint-dependencies-with-chained-pull-requests.md","衝刺相依性與鏈式 Pull Request | AELBOX",{"type":8,"value":195,"toc":321},[196,202,205,212,216,219,227,230,233,236,239,242,245,248,252,255,259,262,270,275,278,281,284,287,290,293,296,299,302,305,309,312,315,318],[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-TW\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,251],{"id":250},"pull-request-更早準備好接受程式碼審查","Pull Request 更早準備好接受程式碼審查",[11,253,254],{},"當你的分支基於同事的分支，核准原本的 Pull Request 就更容易。你已經理解上游工作項目是怎麼實作的，而原本的分支在整個實作過程中都經過測試與審查。它不再是陌生的領域。",[26,256,258],{"id":257},"使用鏈式堆疊式pull-request","使用鏈式（堆疊式）Pull Request",[11,260,261],{},"這種程度的並行需要合適的工具。使用以 Git 為基礎的版本控制，實作起來很直接。以下步驟說明流程。",[11,263,264],{},[14,265],{"alt":266,"height":267,"loading":44,"src":268,"width":269,"decoding":47},"相依樹狀圖",438,"\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fdep-img2.png",800,[11,271,272],{},[51,273,274],{},"相依樹狀圖（同時處理 6 項相依工作）",[60,276,277],{"id":277},"清楚描繪相依關係",[11,279,280],{},"在衝刺規劃時定義相依鏈。Pull Request 鏈接著完全遵循這個定義。開發中途變更鏈結代價高昂，因為需要 Rebase。",[60,282,283],{"id":283},"先從根工作開始",[11,285,286],{},"每條相依鏈都有不依賴其他工作的根工作。這些工作從第一天就能開始。",[60,288,289],{"id":289},"先做核心實作",[11,291,292],{},"這可能與測試驅動開發（Test-Driven Development）衝突，因為那裡是先寫測試。為了讓 Pull Request 鏈易於管理，先實作核心。這樣相依的團隊成員能更早取得內容。",[60,294,295],{"id":295},"以先進先出佇列組織與審查程式碼",[11,297,298],{},"最先建立的分支應該最先被審查與合併。每次合併都會觸發 CI；如果它弄壞主建置，問題還小的時候就能修好。",[26,300,301],{"id":301},"額外負擔",[11,303,304],{},"維護一條相依分支鏈有好處，也有一些缺點。",[60,306,308],{"id":307},"rebase-或合併","Rebase 或合併",[11,310,311],{},"這條鏈必須保持同步，需要投入心力。現代工具提供一鍵與基底分支同步，前提是沒有衝突。在需要時使用，等安全時再拉入上游變更。當建置通過、功能正常時，就同步。",[60,313,314],{"id":314},"團隊合作",[11,316,317],{},"相依鏈需要一個願意彼此對話的協作團隊。如果大家各自閉門造車，就行不通。",[11,319,320],{},"相依的工作項目最好留在當前衝刺之外。當業務需求要求它們並行進行時，一條衍生分支鏈是管理相依負擔的實用方法。",{"title":152,"searchDepth":153,"depth":153,"links":322},[323,324,329,335],{"id":218,"depth":153,"text":218},{"id":232,"depth":153,"text":232,"children":325},[326,327,328],{"id":238,"depth":159,"text":238},{"id":244,"depth":159,"text":244},{"id":250,"depth":159,"text":251},{"id":257,"depth":153,"text":258,"children":330},[331,332,333,334],{"id":277,"depth":159,"text":277},{"id":283,"depth":159,"text":283},{"id":289,"depth":159,"text":289},{"id":295,"depth":159,"text":295},{"id":301,"depth":153,"text":301,"children":336},[337,338],{"id":307,"depth":159,"text":308},{"id":314,"depth":159,"text":314},"2018-05-27","相依的工作項目會讓人空等，拖住整個衝刺。了解堆疊式 Pull Request 如何讓工作持續流動、減少閒置時間。","以鏈式 Pull Request 管理衝刺相依性","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests\u002Fcoffee-table-chain.jpg",[344,345,346,347,348],"衝刺相依性","堆疊式 Pull Request","鏈式 Pull Request","程式碼審查","敏捷交付",{},"\u002Fblog\u002Fzh-tw\u002Fmanage-sprint-dependencies-with-chained-pull-requests",{"title":193,"description":340},{"loc":350,"images":353,"lastmod":164},[354,355,356],{"loc":201},{"loc":211},{"loc":268},"manage-sprint-dependencies-with-chained-pull-requests","blog\u002Fzh-TW\u002Fmanage-sprint-dependencies-with-chained-pull-requests","5rcAKCONG69DRt00CrtjxkOMGJLiNUAPu6SeMzmXJsQ",{"id":361,"title":362,"author":6,"body":363,"dateModified":164,"datePublished":474,"description":475,"extension":167,"heading":476,"image":477,"imageAlt":369,"keywords":478,"locale":176,"meta":484,"navigation":178,"path":485,"reviewed":178,"seo":486,"sitemap":487,"slug":492,"stem":493,"translationKey":492,"__hash__":494},"blog\u002Fblog\u002Fzh-TW\u002Fcomparison-metrics-for-agile-teams.md","敏捷團隊的比較指標 | AELBOX",{"type":8,"value":364,"toc":465},[365,372,375,378,381,388,392,395,398,401,404,412,416,424,427,430,433,439,443,446,452,455,459,462],[11,366,367],{},[14,368],{"alt":369,"height":370,"loading":18,"src":371,"width":20,"fetchPriority":21},"桌上的直尺、Planning Poker 卡片與咖啡杯",958,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.webp",[11,373,374],{},"比較敏捷團隊很困難，而我們也該問問，為什麼要比較。把不同領域的團隊拿來比較，究竟有什麼幫助？",[26,376,377],{"id":377},"創造競爭",[11,379,380],{},"團隊不應該用任意的指標互相排名。那只會打擊士氣。相對地，指標應該給每個團隊公平競爭的機會。績效會因為團隊自己想要而提升，而不是因為有人在後面推。",[11,382,383],{},[14,384],{"alt":377,"height":385,"loading":44,"src":386,"width":387,"decoding":47},487,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun2.png",525,[11,389,390],{},[51,391,377],{},[26,393,394],{"id":394},"創造公平機會的指標",[11,396,397],{},"以下是四項比較團隊的基本指標。它們衡量每個團隊在公平立足點上競爭的能力，僅此而已。可比較的指標創造公平的機會。",[60,399,400],{"id":400},"成功的衝刺",[11,402,403],{},"如果衝刺只是一個時間框架，那就毫無意義。衝刺是一個里程碑，需要目標。衝刺目標（最重要的一組故事）是較大的里程碑，完成每一個故事則是較小的里程碑。在每個衝刺結束時舉辦跨團隊展示，讓各團隊呈現自己交付了什麼。這種良性競爭會鼓勵團隊完成衝刺目標。人需要看得見的目標才會被激勵。",[11,405,406],{},[14,407],{"alt":408,"height":409,"loading":44,"src":410,"width":411,"decoding":47},"朝目標衝刺",680,"\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Frun1.png",874,[11,413,414],{},[51,415,408],{},[11,417,418,419,423],{},"這會不會變成過度承諾與承諾不足的遊戲？如果團隊承諾不足，展示會讓一切無所遁形：能秀的東西變少了。如果過度承諾，展示就變成",[420,421,422],"strong",{},"又一次失敗的衝刺","。交付團隊所承諾的事，會建立做得更多的動力。團隊會對工作感到滿意。",[60,425,426],{"id":426},"速度穩定性與誠實估算",[11,428,429],{},"這是知識工作，不是生產線作業。如果團隊裡沒有人真正理解某個問題、足以估算它的解法，那代表這個問題沒有事先研究。",[11,431,432],{},"在上一個衝刺安排一個限時的 Spike，接著由團隊檢視研究結果，就能輕鬆把實作拆成更小的故事，妥善估算。對於複雜的工作，寫一份更完整的技術設計文件，列出實作故事。",[11,434,435,436,226],{},"Spike 與設計工作本身就是可以估算的故事。關鍵在於為複雜解法定義工作的結構與順序。與其承諾一個團隊不懂的故事，不如建立一項研究型工作來補上缺口。這樣估算才能",[73,437,438],{"href":145},"以證據為基礎",[60,440,442],{"id":441},"容量可預測性避免意料之外的工作","容量可預測性（避免意料之外的工作）",[11,444,445],{},"研究先行，實作隨後。當研究發現問題，就建立新的工作項目並估算。你接著會對下一個衝刺有更清楚的圖像。已知的工作可以估算與規劃；未知的工作則先取得一個限時的研究工作項目，再進行估算。這項紀律就是把大型工作拆成小而可估算的片段。",[11,447,448,449,226],{},"複雜的工作可以提早開始，即使只是為了發現它需要自己的一組故事。這仍然能降低",[73,450,451],{"href":75},"未知的風險",[11,453,454],{},"支援與生產救火通常以限時的看板流程在衝刺之外進行。在那裡，首次回應時間與 SLA 違約就成了比較指標。",[60,456,458],{"id":457},"團隊可用度投入工作的時間除以衝刺總時間","團隊可用度（投入工作的時間除以衝刺總時間）",[11,460,461],{},"可用度是團隊成員花在已估算工作上的時間比例。如果某個團隊比其他團隊更常被拉去訓練、知識分享或其他內部工作，就要修正這個失衡。維持速度穩定的唯一方法，就是維持可用度穩定。當團隊之間的可用度相等，其他比較指標才會奏效。",[11,463,464],{},"比較團隊不是為了懲罰低績效，而是為了提高動力，以及競爭與交付更多的精神。這也是為什麼這些指標不應該讓個別團隊成員看到：它們是輔導的工具，不是公開的排行榜。透過追蹤這些指標、間接引導 Scrum Master，你就能讓團隊站在平等的立足點上競爭。",{"title":152,"searchDepth":153,"depth":153,"links":466},[467,468],{"id":377,"depth":153,"text":377},{"id":394,"depth":153,"text":394,"children":469},[470,471,472,473],{"id":400,"depth":159,"text":400},{"id":426,"depth":159,"text":426},{"id":441,"depth":159,"text":442},{"id":457,"depth":159,"text":458},"2018-05-04","指標應該創造公平的立足點，而不是排行榜。四種能激勵敏捷團隊、又不會懲罰他們的比較指標。","敏捷團隊的比較指標","\u002Fblog\u002Fcomparison-metrics-for-agile-teams\u002Fcoffee-table-ruler.jpg",[479,480,481,482,483],"敏捷指標","團隊速度","敏捷團隊","Scrum","容量",{},"\u002Fblog\u002Fzh-tw\u002Fcomparison-metrics-for-agile-teams",{"title":362,"description":475},{"loc":485,"images":488,"lastmod":164},[489,490,491],{"loc":371},{"loc":386},{"loc":410},"comparison-metrics-for-agile-teams","blog\u002Fzh-TW\u002Fcomparison-metrics-for-agile-teams","02GYIXumbgYlagHSXkvZT1etbyroF2QAtzOmofeHoE0",{"id":496,"title":497,"author":6,"body":498,"dateModified":164,"datePublished":629,"description":630,"extension":167,"heading":631,"image":632,"imageAlt":504,"keywords":633,"locale":176,"meta":636,"navigation":178,"path":637,"reviewed":178,"seo":638,"sitemap":639,"slug":647,"stem":648,"translationKey":647,"__hash__":649},"blog\u002Fblog\u002Fzh-TW\u002Fsheepherding-story-points.md","羊群式故事點：Planning Poker 中的定錨效應 | AELBOX",{"type":8,"value":499,"toc":620},[500,506,509,512,519,526,530,533,536,539,546,550,553,556,559,564,568,571,574,581,585,588,591,596,600,603,614,617],[11,501,502],{},[14,503],{"alt":504,"height":17,"loading":18,"src":505,"width":20,"fetchPriority":21},"咖啡桌上的一群羊與 Planning Poker 卡片","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.webp",[11,507,508],{},"故事點估算經常被忽略，或是在聊天室與公開會議中進行，每個人都能看到或聽到每一票。知道別人怎麼投，會扭曲結果，產生不準確的估算。反覆不準確的估算會導致有缺陷的計畫，以及延誤或取消的交付。以下是公開投票時會發生的事。",[26,510,511],{"id":511},"投票中的角色",[11,513,514,515,518],{},"公開估算投票裡會出現幾種角色。估算結果取決於誰先投，而且通常離誠實很遠。為什麼順序在公開投票中如此重要？因為",[420,516,517],{},"羊群效應","：一種定錨偏誤，讓其他團隊成員複製第一個估算。",[11,520,521],{},[14,522],{"alt":517,"height":523,"loading":44,"src":524,"width":525,"decoding":47},746,"\u002Fblog\u002Fsheepherding-story-points\u002Fsheep-1.png",1779,[11,527,528],{},[51,529,517],{},[60,531,532],{"id":532},"過度自信的投票者",[11,534,535],{},"每個團隊至少有一位成員認為自己最懂系統。他們通常最先投票，因為答案對他們來說顯而易見。他們常忽略可能讓估算失準的細節。這些細節可以事先被挖掘出來，但前提是有人開啟討論。公開投票時這不可能發生。",[11,537,538],{},"這個人通常投得比誠實估算更低。也許只有他們能那麼快完成這個故事，而且還得靠運氣。",[11,540,541],{},[14,542],{"alt":532,"height":543,"loading":44,"src":544,"width":545,"decoding":47},290,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg7.png",600,[11,547,548],{},[51,549,532],{},[11,551,552],{},"其他人跟著投，於是工作看起來輕鬆，任何人都能在規定時間內完成。實際上，最後通常是別人來做。",[60,554,555],{"id":555},"沉默的投票者",[11,557,558],{},"沉默的投票者通常不只一位，他們害怕先投。他們等別人先投，好照抄。他們很少參與討論，只有被問到才回答。他們第二個投，就在心不在焉的投票者之前。",[11,560,561],{},[14,562],{"alt":555,"height":543,"loading":44,"src":563,"width":545,"decoding":47},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg5.png",[11,565,566],{},[51,567,555],{},[60,569,570],{"id":570},"心不在焉的投票者",[11,572,573],{},"他們在實作期間很難捉摸，但投票時行為很明顯。他們總是最後投，抄別人的估算。如果估算不同，他們就挑最常見的那個。他們不想解釋為什麼選了較低或較高的數字，所以避免在需求梳理時協作，也迴避問題。",[11,575,576],{},[14,577],{"alt":570,"height":578,"loading":44,"src":579,"width":580,"decoding":47},353,"\u002Fblog\u002Fsheepherding-story-points\u002Fimg4.png",758,[11,582,583],{},[51,584,570],{},[60,586,587],{"id":587},"疲倦的投票者",[11,589,590],{},"有些團隊成員無法長時間保持專注，錯過討論的關鍵部分。他們失去脈絡，只能猜，或尋找最常見的票來抄。",[11,592,593],{},[14,594],{"alt":587,"height":543,"loading":44,"src":595,"width":545,"decoding":47},"\u002Fblog\u002Fsheepherding-story-points\u002Fimg6.png",[11,597,598],{},[51,599,587],{},[26,601,602],{"id":602},"如何在估算時保持專注",[11,604,605,606,610,611,613],{},"估算很重要，因為只有誠實的故事點才能",[73,607,609],{"href":608},"\u002Fzh-TW\u002Fblog\u002Fcorrectly-estimating-release-deadline","讓專案朝著發佈日期前進","。誠實估算的關鍵，在於對抗",[420,612,517],{},"，無論你用的是紙牌還是軟體。",[11,615,616],{},"在主持人揭曉之前，團隊成員不應該看到彼此的估算。這樣一來，沉默的投票者開始思考，心不在焉的投票者產生興趣，疲倦的投票者也會醒過來。最該問的問題，尤其是有人與團體意見不同時，是「為什麼你投 X 個故事點？」這會開啟一場關於實際實作問題的對話。「你同意 X 個故事點嗎？」這類封閉式問題，只會換來毫無意義的「同意」。",[11,618,619],{},"好的估算工具能讓需求梳理更有參與感，讓每個人保持警覺、隨時準備討論，即使是複雜的故事也能得到更好的估算。",{"title":152,"searchDepth":153,"depth":153,"links":621},[622,628],{"id":511,"depth":153,"text":511,"children":623},[624,625,626,627],{"id":532,"depth":159,"text":532},{"id":555,"depth":159,"text":555},{"id":570,"depth":159,"text":570},{"id":587,"depth":159,"text":587},{"id":602,"depth":153,"text":602},"2018-04-30","公開投票會讓第一個估算定錨全場。看看羊群效應如何扭曲故事點，以及如何誠實地進行 Planning Poker。","羊群式故事點","\u002Fblog\u002Fsheepherding-story-points\u002Fcoffee-table-sheep.jpg",[174,634,635,517,173],"Planning Poker","定錨偏誤",{},"\u002Fblog\u002Fzh-tw\u002Fsheepherding-story-points",{"title":497,"description":630},{"loc":637,"images":640,"lastmod":164},[641,642,643,644,645,646],{"loc":505},{"loc":524},{"loc":544},{"loc":563},{"loc":579},{"loc":595},"sheepherding-story-points","blog\u002Fzh-TW\u002Fsheepherding-story-points","phQlyJL9VUBC9K6Z0NTvpWsb5BmElopIc_ypWAg0qFg",{"id":651,"title":652,"body":653,"dateModified":836,"datePublished":836,"description":837,"extension":167,"heading":679,"image":838,"imageAlt":679,"keywords":839,"locale":176,"meta":840,"navigation":178,"order":841,"path":842,"section":843,"seo":844,"sitemap":845,"slug":846,"stem":847,"translationKey":848,"__hash__":849},"guide\u002Fguide\u002Fzh-TW\u002Festimation-history.md","估算歷史 | Scrumpy Planning Poker",{"type":8,"value":654,"toc":827},[655,658,661,676,681,684,687,690,693,696,699,702,705,745,751,754,765,769,772,798,801,804,824],[11,656,657],{},"每個已接受的估算都會記錄在估算記錄中，為團隊提供過去 90 天的規模決策記錄。",[26,659,660],{"id":660},"檢視估算歷史",[11,662,663,664,667,668,671,672,675],{},"開啟任一 Jira 工作項目、展開",[420,665,666],{},"活動","區域、開啟",[420,669,670],{},"應用程式","，然後選擇",[420,673,674],{},"估算記錄","。此記錄會顯示工作項目的每個已接受估算，最新者在前，並顯示產生該估算的觀點。當工作項目尚無已接受的估算時，記錄會顯示空白狀態，而不是清單。如果空間設有密碼，記錄會先要求輸入。",[677,678],"docs-figure",{"alt":679,"caption":679,"stem":680},"估算歷史","guide-estimation-log",[11,682,683],{},"Scrumpy 會在顯示歷史之前檢查你能在 Jira 中開啟該工作項目。被 Jira 問題層級安全性對你隱藏的工作項目不會傳回。",[11,685,686],{},"空間管理員可以在空間設定中隱藏工作項目上的 Scrumpy 面板與空間估算頁面。只有當兩者都隱藏時，估算記錄才會隱藏。只要其中一個仍顯示，記錄就會保持可用。",[26,688,689],{"id":689},"分頁與導覽",[11,691,692],{},"估算記錄會分頁，以便瀏覽大量歷史記錄。你可以使用記錄底部的選取器，將每頁筆數調整為 5、10、15 或 20 筆。使用分頁控制項在頁面之間移動。",[26,694,695],{"id":695},"即時更新",[11,697,698],{},"當目前工作項目接受新估算時，估算記錄會自動更新，無須重新整理頁面。如果你在第一頁，新項目會出現在頂端。如果你在後面的頁面，表格會回到第一頁，讓你可以看到新項目。如果空間設有密碼，即時更新只會在輸入密碼後開始。",[26,700,701],{"id":701},"記錄的內容",[11,703,704],{},"每個估算歷史項目會顯示：",[706,707,708,715,721,727,733,739],"ul",{},[709,710,711,714],"li",{},[420,712,713],{},"主持人","：完成估算的主持人，以項目頭像顯示",[709,716,717,720],{},[420,718,719],{},"完成度","：必要投票者中有多少人已投票",[709,722,723,726],{},[420,724,725],{},"觀點","：使用了哪個估算觀點",[709,728,729,732],{},[420,730,731],{},"持續時間","：會話花了多久，顯示為「持續 {duration}」",[709,734,735,738],{},[420,736,737],{},"結果","：最終已接受的估算，以及所有個別投票（以逗號分隔的徽章）與投出這些票的參與者。值會使用觀點的卡片組標籤，因此故事點會附有「sp」後置字元，T恤尺寸會顯示其尺寸，時間觀點則會顯示工作日時長",[709,740,741,744],{},[420,742,743],{},"時間戳記","：估算接受的時間，以你的 Jira 時區顯示",[11,746,747,748,226],{},"結果會顯示在綠色徽章中。如果主持人在接受前設定了不同的值，徽章會是黃色，將游標停留在上面會顯示",[420,749,750],{},"主持人已覆寫",[26,752,753],{"id":753},"保留與刪除",[11,755,756,757,760,761,764],{},"估算歷史項目會保留三個月（90 天）。較舊的項目會每天自動移除。若要一次移除空間的每個項目，請使用空間設定",[420,758,759],{},"儀表板","分頁中的",[420,762,763],{},"刪除估算記錄","；該動作是永久的，無法復原。將規劃會議封存到 Confluence 可將其估算保留為 Confluence 頁面，超過 90 天期間。",[26,766,768],{"id":767},"結果如何流向-jira","結果如何流向 Jira",[11,770,771],{},"當主持人接受估算時：",[773,774,775,778,795],"ol",{},[709,776,777],{},"最終估算會使用觀點的平均方法從所有投票計算",[709,779,780,781],{},"結果會依據觀點的估算目標寫入 Jira：\n",[706,782,783,789],{},[709,784,785,788],{},[420,786,787],{},"預設","：更新看板的估算統計資料（預設為故事點）。對於 T恤卡片，這會使用你為所選卡片設定的故事點值",[709,790,791,794],{},[420,792,793],{},"欄位","：更新已設定的自訂欄位，用於點數、時間或 T恤尺寸。T恤尺寸欄位會收到尺寸標籤",[709,796,797],{},"完整的投票會話會儲存以供參考",[26,799,800],{"id":800},"儀表板分析",[11,802,803],{},"空間儀表板會彙總所有工作項目與觀點的估算歷史，以提供：",[706,805,806,809,812,815,818,821],{},[709,807,808],{},"每日已接受估算數",[709,810,811],{},"依觀點的平均估算",[709,813,814],{},"依觀點的平均投票持續時間",[709,816,817],{},"平均一致性分數",[709,819,820],{},"平均變異分數",[709,822,823],{},"每個會話的平均投票者數",[11,825,826],{},"使用日期範圍選取器專注於最近的衝刺，或比較長期趨勢。",{"title":152,"searchDepth":153,"depth":153,"links":828},[829,830,831,832,833,834,835],{"id":660,"depth":153,"text":660},{"id":689,"depth":153,"text":689},{"id":695,"depth":153,"text":695},{"id":701,"depth":153,"text":701},{"id":753,"depth":153,"text":753},{"id":767,"depth":153,"text":768},{"id":800,"depth":153,"text":800},"2026-11-10","每個已接受的估算都會記錄在估算記錄中，為團隊提供過去 90 天的規模決策記錄。 開啟任一 Jira 工作項目、展開活動區域、開啟應用程式，然後選擇估算記錄。 此記錄會顯示工作項目的每個已接受估算，最新者在前，並顯示產生該估算的觀點。 當工作項目尚無已接受的估算時，記錄會顯示空白狀態，而不是清單。","\u002Fog\u002Fguide-estimation-history.jpg",[],{},9,"\u002Fgetting-started\u002Festimation-history","guide",{"title":652,"description":837},{"loc":842,"lastmod":836},"estimation-history","guide\u002Fzh-TW\u002Festimation-history","guide\u002Festimation-history","AUMwqzv44W2HhjA_u-DB3QCFw2ELE0a_OBPlvRtm5kg",1795345554519]