scrum & kanban introduction
TRANSCRIPT
Agile Development : Scrum & Kanban
Introduction
Sai Li @ Yowoo Tech. 2016/02/15 2017/03/29
Agenda• Software Development
• What is Agile?
• Scrum
• Kansan
• Comparison
Software Dev. Life Cycle
• Requirement
• Implementation
• Deployment
Software Dev.• Waterfall• Agile
• Extreme Programming • Scrum • Kanban • …
Waterfall
300+ …
Waterfall Problems• Very long iteration
• Delay
• Too much time for useless features
• Uncertain Progressco
mpl
etio
n(%
)
0
25
50
75
100
V1.0 Feature A B C D
Agile Dev. 1st Roundco
mpl
etio
n(%
)
0
25
50
75
100
V1.0 FeaturesA B C D
Agile Dev. 2nd Roundco
mpl
etio
n(%
)
0
25
50
75
100
V1.0 FeaturesA B C D
Agile Dev. 3rd Roundco
mpl
etio
n(%
)
0
25
50
75
100
V1.0 FeaturesA B C D
Agile Dev. 4th Roundco
mpl
etio
n(%
)
0
25
50
75
100
V1.0 FeaturesA B C D
Life’s too short to build something nobody wants
- Ash Maurya, <Running Lean>
needs(value)
Manifesto for Agile Software Development
Manifesto
principle
Agile Dev.
• Value Driven: WHAT to do ?
• Incremental
• Improve workflow, reduce waste
• Iterative
Waterfall vs. Agile
Time
Changing Cost
Waterfall
Agile
Waterfall vs. Agile
Agile
Waterfall
http://www.hemantlodha.com/wp-content/uploads/2014/11/image11.jpg
Incremental Development
http://herdingcats.typepad.com/.a/6a00d8341ca4d953ef01a511e114a3970c-pi
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
Scrum
What’s Scrum?
http://www.usctrojanrugby.org/wp-content/uploads/2014/01/byu-scrum.jpg
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
Product Owner
• Build the right thing
• Product spec
• Priority
• Take the responsibility
Scrum Master
• Build it faster
• Assistant, improve workflow
• Remove impedances
Team Members
• Build the things right
• cross-functional team
Scrum Flow
http://www.quotium.com/content/uploads/2014/06/060714_1811_Comparisono2.png
Sprint
https-//media.giphy.com/media/ZwiWfeISh9e7e/giphy-downsized-large
What is Story?
• End-to-end
• Value driven
• This app is written in Java
• This database will be build on AWS
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
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
Planning Meeting1. 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
Choose Story
Estimation
change password
How to demo
Importance
Points
30
20
Estimation3 0 13
3 3 3
5
5
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
Task BoardSprint #1 6/1 ~ 6/14
Burndown Chart transparent visualize tool
Sprint Review Meeting
Retrospective Meeting
Retrospective Meeting
• What worked well? • What can be improved? • Stop doing something • Suggestion
backlog refinement
Product backlog refinement meeting
• Grooming backlog
• Pick Stories
Scrum Myth
1. Scrum won’t solve problems
2. Scrum is not silver bullet
3. For Flexibility not speed
4. Conservation of Work
Kanban
Toyota Production System
Just in time
Toyota Production System
Toyota Production System
Push vs. Pull
Kanban Method1. Visualize
2. Limit Work In Progress (WIP)
3. Manage Flow
4. Make policies explicit
5. Implement feedback loops
6. Improve collaboratively, evolve experimentally
Visualize
Work In Progress(Process)
https-//ae01.alicdn.com/kf/HTB1lPHbOpXXXXcraXXXq6xXFXXXx/Guitar-DIY-semi-finished-Tele-22-product-electric-guitar-neck-Birds-eye-maple-fingerboard-xylophone-neck.jpg_640x640
Limit WIP
stop finishing, start finishing
prevent context switching
Manage Workflow
cycle time
lead time
Kansan Method
4. Make policies explicit
5. Implement feedback loops
6. Improve collaboratively, evolve experimentally
Comparison
Scrum Kanban
prescriptive >
role 3 0timeboxediteration V X
empirical O O
WIP
Change within an iteration
Backlog items
•
•
•
References•
• Kanban Roadmap • http://www.slideshare.net/ihower/scrum-kanban-scrum-lean-startup
Q & A