Scrum & Kanban Introduction
- 1. Agile Development : Scrum & Kanban Introduction Sai Li @ Yowoo Tech. 2016/02/15 2017/03/29
- 2. Agenda • Software Development • What is Agile? • Scrum • Kansan • Comparison
- 3. Software Dev. Life Cycle • Requirement • Implementation • Deployment
- 4. Software Dev. • Waterfall • Agile • Extreme Programming • Scrum • Kanban • …
- 6. Waterfall Problems • Very long iteration • Delay • Too much time for useless features • Uncertain Progress completion(%) 0 25 50 75 100 V1.0 Feature A B C D
- 7. Agile Dev. 1st Roundcompletion(%) 0 25 50 75 100 V1.0 Features A B C D
- 8. Agile Dev. 2nd Roundcompletion(%) 0 25 50 75 100 V1.0 Features A B C D
- 9. Agile Dev. 3rd Roundcompletion(%) 0 25 50 75 100 V1.0 Features A B C D
- 10. Agile Dev. 4th Roundcompletion(%) 0 25 50 75 100 V1.0 Features A B C D
- 11. Life’s too short to build something nobody wants - Ash Maurya, <Running Lean> needs(value)
- 12. Manifesto for Agile Software Development Manifesto principle
- 13. Agile Dev. • Value Driven: WHAT to do ? • Incremental • Improve workflow, reduce waste • Iterative
- 17. Agile Dev. • It might take a while to unravel deep assumptions, but that unraveling may open the door to the next round of improvement. by Kent Beck
- 18. Scrum
- 19. What’s Scrum? http://www.usctrojanrugby.org/wp-content/uploads/2014/01/byu-scrum.jpg
- 20. Scrum • Roles: Product Owner, Scrum Master, Team Members • Time Boxing: 1 ~ 4 weeks release a viable product • Cross-functional team • Planning Meeting at the beginning • Demo & Retrospective Meeting at the end • Getting feedback every round
- 21. Product Owner • Build the right thing • Product spec • Priority • Take the responsibility
- 22. Scrum Master • Build it faster • Assistant, improve workflow • Remove impedances
- 23. Team Members • Build the things right • cross-functional team
- 26. Sprint
- 29. What is Story? • End-to-end • Value driven • This app is written in Java • This database will be build on AWS
- 30. What is Story? Template: • As Someone, I can do something, so the value is… Ex: • As an User, I can view items in shop • As an Administrator, I can edit users’ profile • As an User, I can save items to cart
- 31. Story Card • Goal • Importance • How to Demo • Estimate change password How to demo Importance Points 30 20 Login How to demo Importance Points 100 15
- 33. Planning Meeting 1. PO explain Story, choose stories with highest priority 2. divide story in tasks, estimation 3. Communication confirmation compromise 4. What to do? How to do? 5. How to demo? Output: Sprint Backlog
- 34. Choose Story
- 35. Estimation change password How to demo Importance Points 30 20
- 36. Estimation 3 0 13 3 3 3 5 5
- 38. Daily Scrum Meeting • Fixed place, fixed < 15 mins • Standing 1. Tasks Yesterday 2. Tasks Today 3. Any Impedance? http://www.xqa.com.ar/visualmanagement/wp-content/uploads/standup2.jpg
- 39. Task Board Sprint #1 6/1 ~ 6/14
- 40. Burndown Chart transparent visualize tool
- 43. Retrospective Meeting • What worked well? • What can be improved? • Stop doing something • Suggestion
- 45. Product backlog refinement meeting • Grooming backlog • Pick Stories
- 46. Scrum Myth 1. Scrum won’t solve problems 2. Scrum is not silver bullet 3. For Flexibility not speed 4. Conservation of Work
- 47. Kanban
- 48. Toyota Production System Just in time
- 51. Push vs. Pull
- 52. Kanban Method 1. Visualize 2. Limit Work In Progress (WIP) 3. Manage Flow 4. Make policies explicit 5. Implement feedback loops 6. Improve collaboratively, evolve experimentally
- 53. Visualize
- 55. Limit WIP stop finishing, start finishing prevent context switching
- 60. Manage Workflow cycle time lead time
- 61. Kansan Method 4. Make policies explicit 5. Implement feedback loops 6. Improve collaboratively, evolve experimentally
- 62. Comparison
- 63. Scrum Kanban prescriptive > role 3 0 timeboxed iteration V X empirical O O
- 64. WIP
- 65. Change within an iteration
- 66. Backlog items
- 67. • • •
- 69. References • • Kanban Roadmap • http://www.slideshare.net/ihower/scrum-kanban-scrum-lean-startup
- 70. Q & A