Agile Dev. : Scrum Introduction

Chihyang Li @ Yo-woo Tech. 2016/02/15

Software Dev. Life Cycle

• Requirement

• Implementation

• Deployment

Software Dev Types

• Waterfall

• Agile:

• Scrum

• Extreme Programming

• Kanban

• …

Waterfall

300+ …

Waterfall Problems•

• Delay

•

•

0

25

50

75

100

1.0

Feature A Feature B Feature C Feature D

waterfall

Agile Dev. 1st Round

0

25

50

75

100

1.0

Feature A Feature B Feature C Feature D

Agile Dev. 2nd Round

0

25

50

75

100

1.0

Feature A Feature B Feature C Feature D

Agile Dev. 3rd Round

0

25

50

75

100

1.0

Feature A Feature B Feature C Feature D

Agile Dev. 4th Round

0

25

50

75

100

1.0

Feature A Feature B Feature C Feature D

Life’s too short to build something nobody wants

- Ash Maurya, <Running Lean>

needs

Agile Dev.

• Value Driven:

•

•

•

Plan Driven vs. Value Driven

http://lh5.ggpht.com/-Fu8RjG2Tw-Y/UNQBp6fVa4I/AAAAAAAAWD0/mXPfKkY41m8/s1600-h/Image.png

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

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• Planning Meeting at the beginning• Demo & Retrospective Meeting at the end• Getting feedback every round

Scrum Team

Product Owner

• Build the right thing

•

•

•

Scrum Master

• Build it faster

• & Scrum

•

Team Members

• Build the things right• cross-functional team

Scrum Flow

Scrum Flow

Scrum FlowSprint

Scrum Flow

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

Estimate

30

20

Login

How to demo

Importance

Estimate

100

15

Scrum Flow

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

Choose Story

Time Estimation

change password

How to demo

Importance

Estimate

30

20

UI iOS API Android iOSWeb

Time Estimation

20 3 30

20 18 23

20

20

Scrum Flow

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

Scrum Task BoardSprint #1 6/1 ~ 6/14

Burn Down Chart

Burn Down Chart

• Task, Story, Release

• Goal: transparent visualization tool

• Difference between sprint planning meeting and real

world• Sense of achievement

Scrum Flow

Sprint Review Meeting

• Demo Product• New Story

Scrum Flow

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

Scrum Flow

backlog refinement

Product backlog refinement meeting

• Grooming backlog• Pick Stories

Scrum Myth

1. Scrum

2. Scrum

3. Scrum

4. For Flexibility not speed

5.

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

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

Q & A