a brief introduction about Scrum

1. Agile Dev. : Scrum Introduction
Chihyang Li @ Yo-woo Tech.
2016/02/15

2. Software Dev. Life Cycle
• Requirement
• Implementation
• Deployment

3. Software Dev Types
• Waterfall
• Agile:
• Scrum
• Extreme Programming
• Kanban
• …

4. Waterfall
300+ …

5. Waterfall Problems
•
• Delay
•
•
0
25
50
75
100
1.0
Feature A Feature B Feature C Feature D
waterfall

6. Agile Dev. 1st Round
0
25
50
75
100
1.0
Feature A Feature B Feature C Feature D

7. Agile Dev. 2nd Round
0
25
50
75
100
1.0
Feature A Feature B Feature C Feature D

8. Agile Dev. 3rd Round
0
25
50
75
100
1.0
Feature A Feature B Feature C Feature D

9. Agile Dev. 4th Round
0
25
50
75
100
1.0
Feature A Feature B Feature C Feature D

10. Life’s too short to build something
nobody wants
- Ash Maurya, <Running Lean>
needs

12. Agile Dev.
• Value Driven:
•
•
•

13. Plan Driven vs. Value Driven
http://lh5.ggpht.com/-Fu8RjG2Tw-Y/UNQBp6fVa4I/AAAAAAAAWD0/mXPfKkY41m8/s1600-h/Image.png

14. Waterfall vs. Agile
Time
Changing
Cost
Waterfall
Agile

15. Waterfall vs. Agile
Agile
Waterfall
http://www.hemantlodha.com/wp-content/uploads/2014/11/image11.jpg

16. Incremental Development

17. What’s Scrum?
http://www.usctrojanrugby.org/wp-content/uploads/2014/01/byu-scrum.jpg

18. Scrum
• Roles: Product Owner, Scrum Master, Team
Members
• Time Boxing: 1 ~ 4 weeks release a viable product
• Planning Meeting at the beginning
• Demo & Retrospective Meeting at the end
• Getting feedback every round

19. Scrum Team

20. Product Owner
• Build the right thing
•
•
•

21. Scrum Master
• Build it faster
• & Scrum
•

22. Team Members
• Build the things right
• cross-functional team

23. Scrum Flow

24. Scrum Flow

25. Scrum Flow
Sprint

26. Scrum Flow

27. What is Story?
• End-to-end
• Value driven
• This app is written in Java
• This database will be build on AWS

28. 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

29. Story Card
• Goal
• Importance
• How to Demo
• Estimate
change password
How to demo
Importance
Estimate
30
20
Login
How to demo
Importance
Estimate
100
15

30. Scrum Flow

31. Scrum Planning Meeting
1. PO Story Story
2. Story Task
3.
4. What to do? How to do?
5. How to demo?
Output: Sprint Backlog

32. Choose Story

33. Time Estimation
change password
How to demo
Importance
Estimate
30
20
UI iOS API Android iOSWeb

34. Time Estimation
20 3 30
20 18 23
20
20

35. Scrum Flow

36. 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

37. Scrum Task Board
Sprint #1 6/1 ~ 6/14

38. Burn Down Chart

39. Burn Down Chart
• Task, Story, Release
• Goal: transparent visualization tool
• Difference between sprint planning meeting and real
world
• Sense of achievement

40. Scrum Flow

41. Sprint Review Meeting
• Demo Product
• New Story

42. Scrum Flow

43. Retrospective Meeting
• What worked well?
• What can be improved?
• Stop doing something
• Suggestion

44. Scrum Flow
backlog refinement

45. Product backlog refinement meeting
• Grooming backlog
• Pick Stories

46. Scrum Myth
1. Scrum
2. Scrum
3. Scrum
4. For Flexibility not speed
5.

47. 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

48. References
• http://www.slideshare.net/ihower/scrum-kanban-scrum-lean-startup
• http://teddy-chen-tw.blogspot.tw/

49. Q & A