1 / 16

Report: LIU TENG YUAN

Moving to flow-based softeate development An experience report by Jørn Ola Birkeland , Bekk Consultng. Report: LIU TENG YUAN. Background. The iteration S hort iteration (two weeks) generalist developers v.s domain experts. Fig 1: Day one of the iteration. Looking good .

peta
Download Presentation

Report: LIU TENG YUAN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Moving to flow-basedsofteate developmentAn experience report by Jørn Ola Birkeland, BekkConsultng Report: LIU TENG YUAN

  2. Background The iteration Short iteration (two weeks) generalist developers v.s domain experts Fig 1: Day one of the iteration. Looking good Fig 2: Last day of the iteration. Not exactly what we’d planned

  3. Background The iteration Burn-down charts by ScrumMaster Retrospective (valuable , but suggestions ?) Fig 3. The burn-down at day one. Expected worst case best case and average case added. In this case the team had planned a little more than could be expected in the average case. Fig 4: The actual burn-down after the iteration. The team did pretty well, but was far from delivering all that had been planned. Scope change is very visible.

  4. Background The release cycle three 2-week iterations( test week , stage week ,development) test week: regression testing , user stories stage week: more regression testing , no errors , final verification problem: 1.test week was very stressful 2. 3rd deployment had to be carried out idea: next release cycle started in the stage week of the previous one.

  5. Moving to flow The revolution Time box/iteration was eliminated Stand-up meeting changed from team member to work item focus Support process and bug handling integrated in regular process Work item estimation skipped Burn-down charts dropped A defined workflow was introduced , with clear goals/deliverables in each step The whiteboard was changed WIP limits were introduced The evolution

  6. The whiteboard was changed

  7. WIP limits were introduced

  8. ＊

  9. ＊

  10. ＊

  11. KPI:關鍵績效指標

  12. Summay and Conclusions Fig 5: Results of a team survey done a few weeks after introducing FSD

  13. Summay and Conclusions Fig 5: Results of a team survey done a few weeks after introducing FSD

  14. Summay and Conclusions Fig:6 Bugs reported in various environments for each release. FSD introduced after 20090508

  15. Summay and Conclusions 由上面的問券跟統計bug調查顯示, 移除不必需的程序不僅節省時間 工作者能在一件事情更專一、專一 stand-up meeting對象轉移 這使得目標更明確,造成有效的討論 更在最後的bug數量的結果上有顯著的改善,

  16. Reference 圖片來自於以下作者之投影片與報告 “Moving to flow-based software development” by Jorn Ola Birland

More Related