佣金產品的敏捷交付

{"type":"doc","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"導讀：","attrs":{}}]},{"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","text":"最近幾年，敏捷交付已經滲透到每個產品和項目，我們逐漸摸索出適合我們自有的模式，本文將講解佣金產品的敏捷交付。首先我們說明一下敏捷開發，敏捷開發並沒有定義具體的開發過程，而是起源於一個簡單的理念，那就是《敏捷宣言》。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/62/6278632cf3a175e55e9cef48cbc7725e.png","alt":"圖片","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","text":"而之後的各種方法論，其實都是爲了踐行這個原則。簡單來說敏捷開發是一種應對快速變化的需求進行迭代、循序漸進的開發方法。在敏捷開發中，軟件項目的構建被切分成多個子項目（子任務），各個子項目的成果都經過測試，具備集成和獨立可運行的特徵。敏捷開發並不追求前期完美的設計、完美編碼，而是力求在很短的週期內開發出產品的核心功能，儘早發佈出可用的版本。然後在後續的生產週期內，按照新需求不斷迭代升級，完善產品。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/d8/d8d901d62eb0460c437f79704ff2f3d6.png","alt":"圖片","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}},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"敏捷交付特性","attrs":{}}]},{"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","text":"傳統的項目研發管理首先是做好全面的的規劃，就像登山一樣，首先確定山頂高度；從各個角度設定最佳攀登座標；收集最近天氣變化情況，以及預測未來登山的天氣；提前預備遇到風險以及規避方案，以及登山人力挑選等；一切準備就緒，擇日登山。","attrs":{}}]},{"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","text":"敏捷方式則是以現有的裝備以及人力，立即出發，先登上一個小山峯，然後總結經驗，再繼續下一個山峯，時刻擁抱變化，根據變化隨時調整路線，最終登頂。","attrs":{}}]},{"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","text":"兩種方式目標都是爲了登頂，但敏捷方式會更快、更優，爲什麼？我們需要講一講敏捷交付帶來的特性：","attrs":{}}]},{"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":"strong","attrs":{}}],"text":"持續的集成測試：","attrs":{}},{"type":"text","text":"在以往的一個版本交付週期中，使用敏捷交付可以完成5-6個迭代週期，測試在前期需求調研分析到版本交付持續投入跟蹤，並在每個迭代週期中，完成集成測試；","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"版本迭代變更快：","attrs":{}},{"type":"text","text":"在每一個版本迭代過程中，需求變化得到及時改造，及時的糾正前期需求差異，保障版本需求完整性；","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"降低風險：","attrs":{}},{"type":"text","text":"在週期短的交付中，遇到方案的差異，可以及時糾正，規避了後期整體方案的調整，降低了版本重構的風險；","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"得到用戶早期反饋：","attrs":{}},{"type":"text","text":"用戶可以提早接觸到產品，可以提前體驗產品功能的使用，產品研發側也可以儘早的完善產品功能，保障產品的可用性；","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"提高複用性：","attrs":{}},{"type":"text","text":"快速產出可使用的產品是敏捷的最初理念，在這過程中可以避免重複造輪子，提高功能以及代碼複用能力。","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"zerowidth","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"爲了快速提升佣金產品交付，產品線充分利用敏捷的特性，融合到項目研發過程中，對研發過程進行變革，團隊上下貫徹敏捷交付方法：","attrs":{}}]},{"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":"strong","attrs":{}}],"text":"做對的事情","attrs":{}},{"type":"text","text":" - 擁抱變化、緊密和客戶溝通、敏捷計劃會都可以認爲是保證團隊在做對的事情，適應市場的不斷變化；","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"把事情做對","attrs":{}},{"type":"text","text":" - 確定了產品需求，接下來是把事情做對，通過站立會議、敏捷評審會快速測試來保證；","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"把事情做的有效率","attrs":{}},{"type":"text","text":" - 迭代、story points（用戶故事）、敏捷回顧會屬於這個範疇，只有使用迭代和points才能評價團隊的效率、持續改進團隊內的溝通和工作方法，最終提升團隊整體戰鬥力。","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"敏捷交付實戰","attrs":{}}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"敏捷初體驗-廣西佣金交付","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":"br"}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在以往佣金結算系統上線過程中，從（需求分析->設計->研發->測試->集成測試->版本發佈）一個週期，滿足系統全流程出賬（採集-預處理-揀重-批價-合賬）需要將近兩個月的時間。版本交付到現場，客戶接收測試後經常需要再一次進行需求澄清或是需求變更，進行下一輪的優化改造，基本耗時一個月的時間完成整改，整體耗時需要三個月的時間完成全量版本交付。","attrs":{}}]},{"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","text":"傳統項目研發交付週期長主要體現：","attrs":{}}]},{"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":"strong","attrs":{}}],"text":"需求變更重複研發","attrs":{}},{"type":"text","text":" – 傳統項目研發過程中，大版本交付週期長，客戶對交付的版本功能如果存在需求理解差異時，導致整個需求方案重新研發，進一步拉長交付時間。","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"研發人力投入不集中","attrs":{}},{"type":"text","text":" – 大版本交付過程中，來回耗時週期長，研發人員前期版本研發完成後，在後續交付過程中，可能已投入其他項目，對已交付到現場的版本需求優化以及需求變更的改造，研發又要進一步評估投入，拉長整體項目交付週期。","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"測試交付人員投入太晚 ","attrs":{}},{"type":"text","text":"- 系統研發過程中，大專題需求研發過程中，測試交付人員前期只能投入需求分析以及案例輸出，無法快速投入具體功能迭代測試，對後續整體系統的測試需要消耗大量時間。","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"zerowidth","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"針對以上問題，我們在廣西佣金結算系統上線首次採用敏捷交付試點，對整體系統進行拆分，按流程模塊進行研發、測試、交付，同時每天進行站會，總結當天輸出、風險、需求變化，及時落實到研發團隊。","attrs":{}}]},{"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","text":"在一個月的週期中，完成六次版本迭代交付，保障了客戶第一時間驗收系統功能。","attrs":{}},{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"歷經兩個月的時間完成廣西佣金結算系統的交付上線，比以往傳統交付上線縮短一個月時間。","attrs":{}}]},{"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","text":"敏捷帶來的快速迭代交付，也給研發團隊帶來了很大的考驗，主要體現在：","attrs":{}}]},{"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":"strong","attrs":{}}],"text":"從局部效率到高效交付","attrs":{}},{"type":"text","text":" – 敏捷研發時間壓縮，高頻的小版本交付，對版本研發質量要有保障，需要做到順暢高質量交付。小版本高頻率的驗收測試驅動開發，確保高質量的准入準出。測試團隊從需求分析開始全程投入，前期輸出分析文檔和案例，研發過程中就參與到具體功能模塊中單元測試，保障版本質量。同時測試團隊介入方案技術預研測試，降低需求方案返工率，提升研發效率。在每一次版本迭代發佈後，對該短週期的研發過程問題進行復盤，總結提升要素。持續交付實踐的實施、定期覆盤、反饋分析等，即時發現和解決問題，團隊對外的交付響應能力隨之增強。","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"產品升級頻率成倍增長","attrs":{}},{"type":"text","text":" -敏捷研發帶來的快速迭代交付，小版本高頻率的打包、發佈給測試人員和現場實施人員帶來的重複枯燥的繁瑣升級部署工作。對此，我們對現有系統統一docker化鏡像部署進行改造，系統版本都以鏡像方式自動構建，充分利用了公司ZCM平臺進行自動化持續構建部署，一鍵構建、一鍵發佈、一鍵部署，有效的解決敏捷帶來的小版本迭代高頻率版本交付、升級的問題。","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"zerowidth","attrs":{}}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"敏捷開展-重慶&遼寧佣金交付","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":"br"}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"敏捷交付在廣西佣金結算系統交付體驗過程中，充分展示了快速迭代的優勢，保障項目實施進度。接下來在重慶和遼寧佣金研發過程中，我們進一步完善迭代的計劃會議，總結廣西佣金結算系統在敏捷交付過程的優缺點，逐漸形成了一套更加成熟的佣金產品敏捷開發模型和過程分析：","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/28/28772ee52ede56a7200720dff556d5a3.png","alt":"圖片","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","text":"佣金研發團隊版本研發過程","attrs":{}}]},{"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","attrs":{}}],"text":"◉  第一步：獲取需求","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"佣金產品經理從現場客戶、現場項目經理、佣金研發團隊以及其他使用過佣金系統的干係人處首先獲取到初步的需求，這個時候的需求可能是明確的，也可能是籠統的（可能是佣金系統干係人還沒有想清楚的需求）。","attrs":{}}]},{"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","attrs":{}}],"text":"◉ 第二步：擁抱需求","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"佣金產品經理整理所有的需求並分解需求到Product Backlog（產品需求列表，又可稱作產品待辦事項列表或需求積壓列表）列表中，並對列表中的任務進行優先級排序，開發團隊根據列表中制定的優先級進行研發。其中，最重要的需求顯示在Product Backlog的頂部，確保佣金研發團隊知道這就是要先交付的成果。因此，佣金研發團隊不是按照佣金產品經理規定的節奏開展工作，佣金產品經理也不會是開發團隊完成工作的驅動者。相反，佣金研發團隊根據Product Backlog中的順序推進工作，通過看板的持續改善或scrum的迭代來完成這些需求。","attrs":{}}]},{"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","attrs":{}}],"text":"◉ 第三步：迭代計劃會議","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在迭代計劃會議之前，佣金產品經理會提前將優先級高的、大顆粒的需求細化爲單個迭代可以交付的多個用戶故事。迭代計劃會議前半場一般是由佣金產品經理先講下原型、用戶故事，研發團隊成員提出疑問、細節問題。會議後半場是研發團隊對本次迭代列表中的用戶故事進行工作量評估。最後，佣金研發團隊根據本次迭代任務的複雜度、任務量來決定一個迭代週期。通常，迭代週期在1周到4周，不宜太短也不宜太長。在迭代會議上，佣金研發團隊根據開發功能的優先級定義出本次迭代（比如1周）能完成的任務量，並形成Sprint Backlog（迭代任務：就是本次迭代內應該完成的任務列表）。","attrs":{}}]},{"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","attrs":{}}],"text":"◉ 第四步：每日站會","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"每天早上佣金研發各小組都會開每日站會，每日站會是一個簡短的會。站會開始前，佣金研發團隊成員會更新看板上的任務狀態，開會時每個人都可以看到當前的進展情況。團隊一般會利用15分鐘左右的時間，站在看板前，每個人講述一下昨天任務完成情況，今天的計劃和遇到的問題，在這個過程中察覺和消除潛在的風險。","attrs":{}}]},{"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","attrs":{}}],"text":"◉ 第五步：需求列表不斷更新","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在Product Backlog列表中也會有很多不明確的需求（通常是優先級較低），都會在開發的過程中漸漸清晰，當需求明確後，反過來再查看目前分解任務，就會發現需求變化了，新的需求來了，但是敏捷是擁抱需求，所以我們會把需求更新到Product Backlog（產品需求列表）中，待下一次迭代的時候再進行迭代會議討論、排優先級進行開發。","attrs":{}}]},{"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","attrs":{}}],"text":"◉ 第六步：小版本發佈","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"佣金系統每次迭代的版本功能可以需求不完整、有缺陷，但是必須是可視可運行可操作。佣金研發團隊以小版本發佈的節奏，保證團隊在固定週期對電信客戶有交付，交付不是承諾某功能一定在某天上線，而是確保需求功能按優先級順序開發、測試並在迭代上線日上線。這正是佣金研發團隊利用敏捷中小版本發佈的優勢：","attrs":{}}]},{"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":"strong","attrs":{}}],"text":"總體風險比較少","attrs":{}},{"type":"text","text":"：小版本總是在上一個版本基礎上局部調整和增加，變化小使得技術複雜度低；由於規劃的功能較少，工作量也易於估算，所以其總體風險比較少，常常能如期發佈。","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"提升需求接納能力","attrs":{}},{"type":"text","text":"：由於小版本快速實現併發布測試，然後就進入下一個小版本的週期，這樣新需求一旦提出就能快速進入開發視野和儘快實現。而且在變更大的時候，小版本控制能隨時將程序恢復到以前某一時間點狀態。","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"測試和開發高效協作","attrs":{}},{"type":"text","text":"：小版本能將開發環境與測試環境進行有效的隔離，使得開發和測試可以並行工作。例如，當開發實現第一個版本後，開發人員就進入下一個版本週期；測試人員測試新發布的版本並提交Bug，開發人員就可以在下一個版本結束時修正所有上一輪發現的Bug，然後發佈新版本。如此循環往復，開發和測試實現高效協作。","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"開發進度可控","attrs":{}},{"type":"text","text":"：頻繁的小版本發佈可控制軟件開發的進度，通過小版本發佈能使佣金產品各負責人對整個佣金產品的進度、程序的編寫、修改情況有一個整體的瞭解。","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"zerowidth","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"◉ 第七步：反思會","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"佣金研發團隊在每次迭代週期完成後，會召開簡短的反思會，反思在上一次迭代版本開發中哪些做的好，哪些做的不好，總結經驗教訓，並給出改進計劃，再在下一個迭代中改進。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":"br"}},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"敏捷交付成效","attrs":{}}]},{"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","text":"佣金產品的研發團隊併發多省交付，提前溝通確認的需求故事在團隊中迅速溶解，團隊節奏快而緊湊、推進迅速，一個月內發佈交付最高達到10個版本以上，靈活調配促進了團隊內部、團隊與客戶之間的互動。滿足用戶不斷變化的需求，在每一次迭代週期結束時,都能交付用戶一個可用的、可部署的系統。隨時收集用戶意見和需求，在隨後的迭代週期中，這些意見和需求一起在產品中實現和集成。需求故事的變更也快速落地到版本，和客戶達成共同利益。","attrs":{}}]},{"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","text":"敏捷使得整個佣金產品在忙而有序、從容有度、高質快速的迭代中演進。","attrs":{}}]},{"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","text":"得益於敏捷交付，現在","attrs":{}},{"type":"text","marks":[{"type":"strong","attrs":{}}],"text":"佣金結算3.0產品已經完成8省電信佣金、移動集團12個省份結算、3省移動酬金、1省聯通酬金的上線","attrs":{}},{"type":"text","text":"，未來還有移動集團20+省份，電信佣金2省份上線。","attrs":{}}]}]}