Moving to flow based softeate development an experience report by j rn ola birkeland bekk consultng
This presentation is the property of its rightful owner.
Sponsored Links
1 / 16

Report: LIU TENG YUAN PowerPoint PPT Presentation


  • 85 Views
  • Uploaded on
  • Presentation posted in: General

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 .

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Moving to flow-basedsofteate developmentAn experience report by Jørn Ola Birkeland, BekkConsultng

Report: LIU TENG YUAN


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


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.


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.


Moving to flow

The revolutionTime box/iteration was eliminatedStand-up meeting changed from team member to work item focusSupport process and bug handling integrated in regular processWork item estimation skippedBurn-down charts droppedA defined workflow was introduced , with clear goals/deliverables in each step

The whiteboard was changed

WIP limits were introduced

The evolution


The whiteboard was changed


WIP limits were introduced





KPI:關鍵績效指標


Summay and Conclusions

Fig 5: Results of a team survey done a few weeks after introducing FSD


Summay and Conclusions

Fig 5: Results of a team survey done a few weeks after introducing FSD


Summay and Conclusions

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


Summay and Conclusions

由上面的問券跟統計bug調查顯示,

移除不必需的程序不僅節省時間

工作者能在一件事情更專一、專一

stand-up meeting對象轉移

這使得目標更明確,造成有效的討論

更在最後的bug數量的結果上有顯著的改善,


Reference

圖片來自於以下作者之投影片與報告

“Moving to flow-based software development” by Jorn Ola Birland


  • Login