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