研發效能度量核心方法與實踐：落地實施建議

{"type":"doc","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"blockquote","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"研發效能度量的出發點雖然很好，但是如何正確、有效的度量卻是一個頗有難度的技術活兒。近期圍繞如何進行效能度量的討論不絕於耳，但如何構建度量的體系化框架、如何進行度量指標的選取、如何進行度量分析、如何進行落地運營，卻鮮有文章具體闡述。在這一背景下，張樂老師撰寫了《研發效能度量核心方法與實踐》系列文章，對以往經驗進行了總結和提煉，包括以下內容："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"1. "},{"type":"link","attrs":{"href":"https:\/\/www.infoq.cn\/article\/vTucU06GZrOFHSmveuCW","title":null,"type":null},"content":[{"type":"text","text":"效能度量的難點和反模式"}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"2. "},{"type":"link","attrs":{"href":"https:\/\/www.infoq.cn\/article\/kXCDJ0gMEE4cSv05XVNq","title":null,"type":null},"content":[{"type":"text","text":"效能度量的行業案例和關鍵原則"}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"3. "},{"type":"link","attrs":{"href":"https:\/\/www.infoq.cn\/article\/kINcaQBBC0uyvFmVlvzx","title":null,"type":null},"content":[{"type":"text","text":"效能度量的實踐框架和指標體系設計"}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"4. "},{"type":"link","attrs":{"href":"https:\/\/www.infoq.cn\/article\/b7G05ot0VJkFbVWQaLlx","title":null,"type":null},"content":[{"type":"text","text":"效能度量的常用分析方法"}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"5. 效能度量的落地實施建議"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"以上內容將以五篇連載文章的形式發佈，共計超過3萬字，本文是第五篇。"}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"在之前的文章中，我們分別討論了效能度量的難點和誤區、業界案例和關鍵原則、度量實踐框架、度量指標體系設計、度量常用分析方法，但在中大規模企業中成功落地效能度量還有很多因素需要考慮，本篇文章我就結合近期落地經驗，來介紹一下落地過程中具體的實施建議。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"1 系統性建設研發效能度量體系"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"在企業研發效能度量體系建設的初始階段，大家的關注點可能都聚焦在度量什麼樣的指標、如何採集和計算、如何展示報表等問題上，這只是在做一些單點能力的建設，但並沒有形成體系。隨着持續深入的推進，需要更加系統性地思考，對於研發效能度量體系也會有不同的理解。下圖給出了某互聯網大廠效能度量體系的架構圖。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/infoq\/d3\/d3fc0e4e5eaa2f1fc3c0917806c69daa.png","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"在圖中，有以下幾部分內容需要重點關注："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":"度量的用戶場景"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"度量指標是統計出來用來給人來看的，我們首先要找準用戶和場景，沒有目的性的堆砌指標沒有任何價值。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"比如，高層管理者一般關注組織級的效能評估結果，包括整體的研發投入產出、戰略的資源分配和達成情況、業務滿意度、各事業部北極星指標的橫向對比、研發效能月報等，但可能不會關注特別細節的指標數據。團隊級管理者不僅會關注團隊交付效率、交付質量、交付能力等全方位的效能指標，並且希望度量平臺具備問題自動化診斷和分析能力，能夠結合趨勢、下鑽、關聯分析等多種手段幫助識別效能瓶頸。工程師也會關注一些效能指標，用於對個人工作進行需求、任務、代碼、缺陷等維度的統計和反饋。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":"度量的指標體系"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"我們在之前的章節中講到了很多度量指標，但只有指標的定義是不夠的。我們還需要明確指標價值、指標說明、指標公式、指標採集方式、指標優先級、指標健康度等內容。"},{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":"度量的根本要求之一就是數據的準確性"},{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"，那麼度量指標的健康度就顯得尤爲重要了。我們曾經發現在推廣度量體系時，某部門的需求交付週期小於0.1天的佔比爲8.6%（290\/3374），經排查，這些需求通常爲研發完成後補錄，這些數據的存在會影響交付週期度量結果的準確性，需要格外引起重視。另外，指標體系及其詳細說明應當儘量公開透明，這樣用戶在得到指標度量結果的時候也可以更清晰理解其計算口徑和與其他指標的邏輯關係。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":"度量的模型設計"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"模型是對某個實際問題或客觀事物、規律進行抽象後的一種形式化表達方式，一般包括目標、變量和關係。在研發效能度量領域，模型有很多種，比如組織效能模型、產品\/團隊效能模型、工程師效能模型等。效能度量的領域專家可以建立模型，並通過度量平臺屏蔽其複雜性，提供給用戶自助化分析使用。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"一個典型的應用場景是效能度量的體檢模式，即度量平臺根據領域專家總結出來的效能指標和既定模型，對產品線某個時間段的研發過程進行分析體檢並推送體檢報告，相關干係人都可以定期收到報告。在報告中標識了的正常\/異常的研發效能指標項，並帶有初步分析結果和問題改進的建議。然後，如果想對其中的某個指標進行詳細分析，則可以切換到問題診斷模式，這樣可以基於模型對相關的指標及報表組合進行專項分析，包括各種趨勢、下鑽和關聯分析等，幫助排查具體問題。在積累了足夠的歷史數據後，也可以通過模型進行風險預警，當發現某些指標有異常波動或相不好的方向發展的趨勢後，及時給出風險提示。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":"度量的產品建設"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"研發效能度量的過程實際上是要把數據轉化爲信息，然後將信息轉化爲知識，這樣就可以讓用戶自主消費數據，進行分析和洞察。一個優秀的研發效能度量產品要做到自動化的數據採集，自動化的數據聚合，讓用戶可以自助化的查詢和分析，甚至自定義報表，從而獲得研發效能的有效洞察。度量產品應該是可以被整個組織的團隊和管理者訪問到的，效能數據也應當被更加透明地使用，不宜設置過多的數據訪問權限，人爲地製造信息不對稱。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"度量平臺也應該被作爲一個產品而不是項目來運作，包括度量什麼、如何分析、如何對比實驗都是需要持續演進的，而且作爲一個產品我們要多聽取用戶的反饋，這與建設其他產品的過程都是一樣的。另外，度量產品一定要注重易用性，使用平臺的用戶往往不是這個方面的專家，應該避免使用複雜的公式定義和晦澀難懂的專業術語進行描述。例如下圖就是度量平臺對交付週期類指標的一種可視化的展示視圖，用戶可以在頁面上進行點選操作，關於指標範圍、說明都動態展示，讓用戶可以一目瞭然進行快速理解。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/infoq\/36\/36721f440249f3a4d8bdc9a29fa66e57.png","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":"度量的運作模式"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"成功的效能度量落地離不開組織的有力支撐，很多企業會採取虛擬的效能度量委員會來進行度量體系的設計和落地。在度量體系建設的初期，委員會的主要職責就是進行指標的定義和對齊，要考慮各種可能的場景和邊界情況，讓指標明確、有意義、無歧義。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"隨着度量體系的逐步落地發展，委員會成員也會迅速擴充，這些成員就成爲了各個部門推進效能度量的種子選手。當然，在一線落地過程中免不了遇到各種問題，那麼委員會就要進行整體規劃的對齊和疑難問題的決策。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"隨着度量體系逐漸成熟，委員會可以把重心放到效能分析和效能提升的實踐分享上來，形成效能度量指導手冊、效能提升案例庫和專項解決方案知識庫，沉澱過程資產，讓效能的度量、改進和提升成爲日常工作的一部分。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"2 通過自動化降低度量帶來的額外成本"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"研發效能的度量不是免費的，爲了做到準確、有效的度量，各種成本加在一起是很高的。度量的準確性依賴流程的規範性，需要明確研發流程、制定相應規範，並確保相關的活動都在系統中進行及時、完整的記錄。爲了能在減少研發過程中各個角色時間和精力投入的基礎上提升效能度量的準確性，可以通過統一工程效能平臺固化研發流程與活動，並通過自動化的手段減少工程師繁瑣的額外手工操作（如在多個系統進行狀態更新同步等）。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"在研發過程中，我們要同時關注管理側的需求價值流和工程側的研發工作流。管理側的價值流以需求特性爲核心，貫穿就緒、設計、開發、測試、發佈等階段。工程側的研發工作流以代碼提交爲線索，會執行分支創建、代碼提交、編譯、掃描、測試、代碼合併、部署、發佈的等一系列活動。我們可以通過效能工具平臺的建設，讓這兩條流之間實現聯動，自動完成狀態的流轉和信息的同步。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"下圖就是一個自動化狀態流轉和信息同步的案例，部門選用了特性分支開發的分支模型，當特性分支拉出並關聯需求的時候，或者代碼提交Commit信息關聯了需求ID後再進行Push的時候，就會觸發對應需求的狀態更新，從”就緒”更新爲”開發中”。當代碼Merge Request合併到remote\/dev分支時，會觸發對應需求的狀態更新爲”測試中”。當代碼合併到remote\/master分支時，會觸發對應需求的狀態更新爲”發佈中”。直到最終發佈完成後，需求的狀態自動更新爲”已完成”。這種自動化的狀態流轉讓系統中記錄的研發過程元數據更爲準確，也在較低成本的情況下給度量提供了有效的研發基礎數據。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/infoq\/b3\/b31b31171fd09d1331efa14aa952facb.jpeg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"3 避免度量的平均值陷阱"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"平均值陷阱，是指由於參與平均值計算的數據樣本存在較大差異，平均值難以真實反映所有樣本狀態的情況。比如某個需求的交付週期是1天，第二個需求是2天，另外一個需求是96天，那麼這三個需求交付週期的平均值就是33天，這明顯無法反饋出真實的情況。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"在軟件研發領域，從數據統計的角度來看，"},{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":"需求交付週期這類指標通常符合韋伯分佈"},{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"，這是一種連續的概率分佈，類似於一種向左傾斜並帶有長尾的正態分佈。所以，對於需求交付週期，我們推薦的度量方法不是平均值，而建議使用第85百分位數。其原理就是將一組數值從小到大排序，處於85%位置的那個數值，就稱爲第85百分位數。而我們經常說的中位數就是第50百分位數。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/infoq\/d5\/d52d6e6300b5a215ea45f9110431590f.jpeg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"假如需求交付週期的第85百分位數是21天，那麼這意味着，根據經驗證據，任何大小相似的需求（理想情況下，所有需求都可被拆分爲大致相似的顆粒度，並且應較小)，都有85%的概率在21天內完成，這可以成爲我們基於統計規律對開發計劃進行承諾的依據。我們可以定期畫出這張圖表，看看它的形狀是如何變化的。當第85百分位數前移，那麼你就能更快地向客戶交付價值。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"不僅是需求交付週期，我們在多個團隊的效能度量中也應該極力避免平均值陷阱。下圖展示了某個部門在進行效能度量過程中發現的一種情況，即經過了一個季度的效能改進，這個部門的效能度量指標幾乎沒有變化，這就讓管理者非常苦惱，時間花出去了但是看不到任何效果。但是，當我們把度量指標下鑽到團隊中後，發現其實已經有很多團隊的效能獲得了大幅提升，最多的一個團隊甚至提升了18%，而其他的一些團隊由於各種原因，效能度量指標出現了下降，在平均值數據上抵消了高效能團隊積極改進所帶來的成果。這樣，我們就可以分而治之，繼續鞏固先進團隊的效能實踐，排查低效團隊的效能問題，細化的度量可以給每個團隊帶來明確的行動指引。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/infoq\/4e\/4eb783da52d5183cb8a939b07647b5ce.png","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"4 把度量引導到正確的方向上"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"度量組織效能是企業中最敏感的領域之一，經常受到政治和各種職能障礙的影響。此外，由於度量不可避免地涉及到對度量數據的解釋，也會受到認知偏差、溝通問題和組織目標對齊的影響。所以如果度量沒有被引導到正確的方向上或沒有被正確地實現，會導致重大的風險，即度量的結果可能弊大於利。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"我們要避免把度量武器化。根據古德哈特定律，當某個度量變成了目標，它便不再是一個好的度量。所有的度量都可以被操縱，而數字遊戲式的度量會分散員工的注意力並耗費大量時間。把度量指標設置爲KPI進行考覈，只是激勵員工針對度量指標本身進行優化，這通常比他們在度量之前所做的工作效率要更低。度量不是武器，而是指導我們進行效能改進的工具。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"我們也會碰到另一種情況，就是純從數字來看，效能度量指標有了大幅提升，比如交付效率和吞吐量都在提高，但業務部門卻仍不滿意，他們的反饋是：”好像並沒有什麼變化!”那麼這個時候，我們應該相信誰呢，是數據還是業務部門的聲音？正如傑夫·貝佐斯(Jeff Bezos)的名言所說：“我注意到的是，當傳聞和數據不一致時，傳聞通常是正確的”。很可能是你度量的方法有問題，或是數據已經失真，這就需要進一步的檢視和反思了。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"豐田的大野耐一曾經說過：”那些不懂數字的人是糟糕的，而最最糟糕的是那些只盯着數字看的人”。每個數字背後都有一個故事，而這個故事往往包含比數字本身所能傳達的更重要的信息。現場觀察(Gemba)是一個可以與度量結合使用的強大工具，管理者要到實際的研發交付過程中去，觀察需求和價值的流轉過程，看一下團隊是如何滿足客戶需求的。正式的度量和非正式的觀察是相輔相成的，可以對結果進行相互印證。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/infoq\/84\/8490fdf855966b8c40c8824ebe1cd195.png","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"小結"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"在數字化時代，每一家公司都是信息技術公司，研發效能已經成爲核心競爭力。通過正確的效能度量方法，堅持數據驅動和實驗性的精神，可以讓研發效能可量化、可分析、可提升。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"通過研發效能度量方法與實踐的系列文章，相信你已經對爲什麼要做效能度量、如何設計度量指標、如何進行度量分析、如何進行有效落地有了比較深刻的理解，也希望你能在實踐中持續精進，我們一起多多交流，相互學習!"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":"最後，祝你能擁有更高的研發效能！"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}},{"type":"strong"}],"text":"作者介紹："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#494949","name":"user"}}],"text":" "}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"color","attrs":{"color":"#333333","name":"user"}}],"text":"張樂，騰訊 DevOps與研發效能資深專家，曾長期工作於擁有數萬研發的互聯網大廠（百度、京東等），專注于敏捷與DevOps實踐體系、DevOps平臺產品設計、研發效能度量體系建設等方向，歷任資深敏捷教練、DevOps平臺產品總監、集團級研發效能度量標準化聯盟負責人等崗位。長期活躍於技術社區，目前是DevOps起源國際組織DevOpsDays中國區核心組織者，同時也是國內多個技術峯會的聯席主席、DevOps\/研發效能專題出品人、特邀演講嘉賓。EXIN DevOps全系列國際認證授權講師、鳳凰項目DevOps沙盤國際授權教練。歷任埃森哲、惠普等全球五百強企業資深諮詢顧問、技術專家，多年敏捷與DevOps轉型、工程效率提升和大型項目實踐經驗。暢銷書《獨角獸項目：數字化時代的開發傳奇》譯者。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"系列文章推薦閱讀："},{"type":"link","attrs":{"href":"https:\/\/www.infoq.cn\/theme\/107","title":null,"type":null},"content":[{"type":"text","text":"研發效能啓示錄"}],"marks":[{"type":"underline"}]}]}]}