Scrum And Kanban (for better agile teams)

Presentation copyright © 2009-2011 AccuRev, Inc. May be used with
permission only. Contact dpoole@accurev.com for permission. www.synerzip.com
Scrum & Kanban Like Chocolate and Peanut Butter

Overview
 Why bother?
 Bird’s eye view of Scrum
 Problems with multi-Scrum-team coordination
 Bird’s eye view of Kanban
 One-piece-flow (aka small batch size)
 Applying Kanban basics to Scrum
 Moving away from iterations
 Synchronized Scrum Teams

Who is “The Customer?”
Market
/Customers
Software
Development
Business Unit

Who is “The Customer?”
Market
/Customers
Your offering

Return on Investment
Return
Investment
ROI =
Software
Value

The Time Value of Money
A
A
B
B
C
C
D
D
Cost Value
Who wants to
make some
money?

The Time Value of Money
A
B
C
D
Invested
here
Time
Value
Learning also has value

Continuous flow of
working software
Team
Software Development Nirvana
Customers
$ • Fast
• Small increment
• Maximum value
Done stories as
check points

 Why bother?
 Problems with multi-Scrum-team coordination

permission only. Contact dpoole@accurev.com for permission. www.synerzip.comCustomers
Product
Management

 Why bother?
 Problems with Scrum

permission only. Contact dpoole@accurev.com for permission. www.synerzip.comCustomers
Product
Management
Int

Problems With Multi-Team Synchronization
 Can’t say you are “shippable” until fully integrated
 Hardening/stabilization iterations
 “QA iterations” offset from “Dev iterations”
 Integration iterations
 Visibility into problems is clearest at end of iteration
 Resolution may not come for multiple iterations

3247 – User wants
to combine depots 5
Kanban
4246 – User wants
to unhide a depot 2 3241 – User wants
to hide a depot 2
todo wip coded tested done
3249 – User wants
to copy a depot 3 3236 – User wants
to split a depot 5
3216 – User wants
to remove a depot 1
backlog
3246 – User wants
a list of depots 3
3244 – User wants
to remove a
replica
8
1) Visual system of managing work
2) Limited work in progress
3) Work is pulled through the system
3226 – User wants
to undo a depot
operation
3146 – User wants
to replicate a
depot
5
8
3256 – User wants
to rename a depot 1

Kanban in Action
Customers
Int

What’s in a User Story
3226 – User wants
to undo a depot
operation
5

Features of All Shapes and Sizes
Specify
Design
Code
Integrate
Document
Write tests
Test
S D
C I
W
TD
Gradient or
rhythm?

One Piece Flow
Within an Iteration
DS C
I W T
D
3226 – User
wants to undo a
depot operation
5
Do you remember me?

One Piece Flow
Within an Iteration
DS C
I W T
DDS C I
W T
D
DS C I
W T
D
DS C I W T
D
DS C
I W T
DDS C I
W T
D
DS C I
W T
D
DS C
I W T
DDS C I
W T
D
DS C I
W T
D

Activity vs Achievement

One Piece Flow
DS C I
W
T
D
DS C I
W
T
D
Within an Iteration

One Piece Flow
Within an Iteration
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D

Taskboard/Limited WIP/Pull
3246 – User wants
to create a depot 5
todo wip coded tested done
3246 – User wants
to combine depots 5
3247 – User wants
to combine depots 5
4246 – User wants
to unhide a depot 2 3241 – User wants
to hide a depot 2
3249 – User wants
to copy a depot 3 3236 – User wants
to split a depot 5
3216 – User wants
to remove a depot 1
3246 – User wants
a list of depots 3
3226 – User wants
to undo a depot
operation
3146 – User wants
to replicate a
depot
5
8
3256 – User wants
to rename a depot 1

wip coded tested donetodo
3244 – Surveyor
wants to remove
a question
1
3245 – Surveyor
wants to create a
multiple choice
question
3 3246 – Surveyor
wants to create a
true/false question
2
3247 – Surveyor
wants to add a
freeform question
3
3242 – Surveyor
wants to browse
survey results
3 3241 – User wants
to take a survey 5
3243 – Surveyor
wants to add a
new question
3

wip coded tested donetodo
3244 – Surveyor
wants to remove
a question
1
3245 – Surveyor
wants to create a
multiple choice
question
3 3246 – Surveyor
wants to create a
true/false question
2
3242 – Surveyor
wants to browse
survey results
to take a survey 5
3243 – Surveyor
wants to add a
new question
3
3247 – Surveyor
wants to add a
freeform question
3

todo
3244 – Surveyor
wants to remove
a question
1
3245 – Surveyor
wants to create a
multiple choice
question
3 3246 – Surveyor
wants to create a
true/false question
2
3242 – Surveyor
wants to browse
survey results
to take a survey 5
3243 – Surveyor
wants to add a
new question
3
wip coded tested done
3247 – Surveyor
wants to add a
freeform question
3

todo
3244 – Surveyor
wants to remove
a question
1
3245 – Surveyor
wants to create a
multiple choice
question
3 3246 – Surveyor
wants to create a
true/false question
2
3247 – Surveyor
wants to add a
freeform question
3
3242 – Surveyor
wants to browse
survey results
to take a survey 5
3243 – Surveyor
wants to add a
new question
3
wip coded tested done

?
✔
✔
✔
✔
✔
✔
✔
?
✔
✔
✔
✔
✔
✔
✔
Done
Retrospective
Iteration Review
Backlog grooming
Story estimation
Choose stories
✔
?

? ?
✔
✔
✔ ✔
✔
✔
✔ ✔
✔
✔
✔
✔
✔✔
✔

Trailing 4 Week Burnup
Trailing 4 weeks
4 Week Burnup
5
10
15
20
0
StoryPoints

Calculating Velocity
Iteration Velocity
10
20
30
40
0
StoryPoints
Iterations
4 Week Velocity
10
20
30
40
0
StoryPoints Iterations
Trailing 4 weeks
Per iteration

Decoupling Commitment
 Or else what?
 New Scrum Guide replaces commitment with
forecast
 Scrum Commitment
• Team will get all committed stories to ‘done’
• Everybody else will leave the team alone
 Trust is the flip side of commitment
 Trust is a two way street and requires flexibility
 Handling the unexpected requires negotiation

?
✔
✔
✔
✔ ✔
✔
✔
✔ ✔
✔ ✔
✔✔
✔ ✔
?
✔

permission only. Contact dpoole@accurev.com for permission.
“Pure” Scrum An Example Mix
Self Organizing Team Self Organizing Team
Team Member Team Member
Product Owner Product Owner
Scrum Master Scrum Master
Sprint Planning Weekly Story Estimation
Daily Standup Daily Standup
Sprint Review Monthly Review
Retrospective Weekly Retrospective
Product Backlog Product Backlog
Sprint Backlog Selected Stories Column
Burndown Trailing 4 week burnup
Daily Cycle Daily Cycle
Sprints
Releases Releases
Scrum of Scrums Stop the Line
Kanban Board
One piece flow
WIP limits
Multi-Stage Continuous Integration

Product
Management
Int
Customers

Product
Management
Int
Int
Int
Customers

Product
Management
Customers
Individuals and Interactions

Product
Management
Customers
Agile Project Management

Product
Management
Customers
SCM (Version Control)
Int
Int
Int
Web
Mobile
DB
Server

Product
Management
Customers
Continuous Integration
Int
Int
Int
Web
Mobile
DB
Server

Product
Management
Int
Int
Int
Customers
 Whole product
touch point after
every story
 Working software
after ever story is
complete
 Scales up
Continuous Delivery
$

Product
Management
Int
Int
Int
Customers
Continuous Touch Points
What
does that
mean?
You want
what!?
Why can’t
we finish
this?Why
won’t this
integrate?
Why is this
unshippable?

Resources/Q&A
 Do It Yourself Agile – Damon Poole
http://damonpoole.blogspot.com
 Don Reinertsen’s Books
 Lean Software Development, Mary Poppendieck and
Tom Poppendieck
 Scrumban - Essays on Kanban Systems for Lean
Software Development, Corey Ladas
 Kanban and Scrum – Making the Most of Both,
Henrik Kniberg & Mattias Skarin
 Agile Software Development with Scrum, Ken
Schwaber & Mike Beedle

The Lean Startup Model

Product
Management
Int
Int
Int
Customers
 Flow continues
around any
problems
Continuous Delivery
$

Product
Management
Int
Int
Int
Customers
 Rebalance as
needed
Continuous Delivery
$
Help!

Q&A Time
1-800-383-8170 or
+1-781-861-8700
sales@accurev.com
www.accurev.com
blog.accurev.com
www.synerzip.com
Hemant Elhence
hemant@synerzip.com
469.322.0349
Agile Software Product Development Partner

Synerzip in a Nut-shell
1. Software product development partner for small/mid-sized
technology companies
 Exclusive focus on small/mid-sized technology companies, typically venture-
backed companies in growth phase
 By definition, all Synerzip work is the IP of its respective clients
 Deep experience in full SDLC – design, dev, QA/testing, deployment
2. Dedicated team of high caliber software professionals for each
client
 Seamlessly extends client’s local team, offering full transparency
 Stable teams with very low turn-over
 NOT just “staff augmentation”, but provide full mgmt support
3. Actually reduces risk of development/delivery
 Experienced team - uses appropriate level of engineering discipline
 Practices Agile development – responsive, yet disciplined
4. Reduces cost – dual-shore team, 50% cost advantage
5. Offers long term flexibility – allows (facilitates) taking offshore
team captive – aka “BOT” option

Synerzip Clients

Scrum And Kanban (for better agile teams)

More Related Content

Similar to Scrum And Kanban (for better agile teams) (20)

More from Synerzip (20)

Recently uploaded (20)

Scrum And Kanban (for better agile teams)