The document discusses 6 common traps that teams fall into when working in an agile way. These traps are: 1) making decisions too early and locking them in, 2) not having a shared understanding of purpose, 3) long feedback cycles with no validation, 4) being overwhelmed by opportunities, 5) not getting work fully completed ("done"), and 6) treating all work as equally important. For each trap, the document provides examples and proposes solutions like deferring decisions, using user story mapping, employing lean startup principles, limiting work in progress, focusing on completion over features, and prioritizing work. The overall message is that teams need to accelerate learning, deliver value faster, and avoid these traps in order to be
PCA14: Accelerate Learning and Overcome the 6 Traps of Agile
1. Accelerate Learning
and Overcome the 6
Traps of Agile
David Hawks
@austinagile
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
2. David Hawks
Agile Velocity
Agile Coach
david@agilevelocity.com
Role
Name
Company
Please fill out card as follows & pass to front
Years of AgileExperience(if any)
10 yrs
Email Address(If you would like a copy of the
slides & to receive periodic information about agile)
4. 45%$
19%$
16%$
13%$
7%$
Never$
Rarely$
Some5mes$
O8en$
Always$
From: A Standish Group study
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
What causes us to build features which
are rarely or never used?
Feature/function usage in the software industry
Find a Partner and Discuss the
following Question.
5. David Hawks
CEO of Agile Velocity
Agile Trainer and Coach
@austinagile
austinagile.com (blog)
david@agilevelocity.com
Deliver Innovative Products Faster
6. Problem #1
We make tough decisions
too early and lock them in
Image Credit: http://i.qkme.me/3unlv7.jpg
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
7. Smartest Point??Dumbest Point
Accelerate Learning
Defer Decisions to the
last Responsible Moment
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
x
z
9. Problem #2
The team doesn’t have a Shared
Understanding of their purpose
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
10. User Story Mapping
Technique to Learn
about Customer Needs
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
11. A
sample
story
map:
E-‐commerce
site
Search
by
keyword
View
description
&
photo
Filter
by
price
Pay
by
credit
card
Select
item
for
purchase
Enter
shipping
info
Filter
by
brand
Decreasing
priority
Clear
search
criteria
MVP
1
above
this
line
Search
products
Shopping
cart
Create
account
Pay
&
Ship
Compare
products
Detailed
product
specs
Read
product
reviews
Facebook
for
login
Search
by
SKU
Persist
payment
info
Zoom
on
photos
Product-‐
specific
filters Side
by
side
comparison
Pay
by
PayPal
Update
profile
Order
status
View
open
orders
Confirm
payment
&
shipping
info
Remove
from
cart
Estimate
total
w/
tax
shipping
Modify
item
quantity
Select
multiple
items
for
purchase
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
12. Problem #3
Long/ No Feedback or Validation Cycles
http://www.skinit.com/assets/catalog/jumbo_shot/jumbo_shot57479340.jpg
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
13. Lean Startup/ Lean UX
Validated Learning
BuildLearn
Measure
Minimize time
thru the loop
1) What do we
need to
learn?
2) How can we measure it?
3) What is the
simplest thing
to build to
measure it?
(MVP)
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
14. Assume the team was working in value order,
when would you release this product?
What would be the benefit of releasing early?
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
45%$
19%$
16%$
13%$
7%$
Never$
Rarely$
Some5mes$
O8en$
Always$
15. What keeps us from delivering
products faster?
http://www.captivations.com.au/wp-content/uploads/2013/03/Fast-delivery.jpg
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
16. Problem #4
Drowning in a Sea of Opportunity
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
17. Numbers,
Fives,
Alphabet
1, 2, 3, … 15
5, 10, 15, … 50
A, B, C, … Z
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
18. Working
on many
items in
parallel
Working
on items
one at a
time
Lots of WIP slows things down
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
10 20 30 40
19. Problem #5
Not Getting to Done
Image Credit: http://files.smashingmagazine.com/wallpapers/april-13/images/its_not_done_until_it_ships__15.png
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
20. Sprint 1 Sprint 2 Sprint 3 Sprint 4 Hardening
20 Points 20 Points 20 Points 20 Points
}
8 Weeks
1 2 3 4 Hardening
}
8 Weeks
}2 Weeks
}
2 Weeks
}
2 Weeks
}
2 Weeks
}
2 Weeks
Done = Feature Complete and Feature Tested
*But defects were deferred to the end
The Plan:
10 Weeks to Deliver 80 Points
Reality:
16 Weeks to Deliver 80 Points (10 Points per 2 Weeks)
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
21. Done = Feature Complete, Feature Tested, and defects
fixed
Go Slow to Go Fast!
Sprint 1 Sprint 2 Sprint 3 Sprint 4
}
2 Weeks
15 Points 15 Points 15 Points 15 Points
}
2 Weeks
}
2 Weeks
}
2 Weeks
Sprint 5
}
2 Weeks
15 Points
We Delivered 75 Points in 10 Weeks
15 Points per 2 weeks
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
22. Working on
many items in
parallel
Working on
items in value
order
HighestValue
Impact of Change
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
24. Problem #6
Everything is Important
Image Credit: http://d.wildapricot.net/images/newsblog/bigstock-important-very-high-priority-i-46052392.jpg?sfvrsn=0
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
25. How we Normally
Assign Work
Project 1
Project 2
Project 3
Carter
Alex
James
Camryn
Janet
Will
All High Priority
How does Alex decide what to work on next?
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
26. How we should
prioritize work in Agile
Project 1
Project 2
Project 3
Carter
Alex
James
Camryn
Janet
Will
Agile Team
Prioritized
Team Backlog
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary
27. The PSPI is the
Answer
It allows us to:
Deliver Often
Accelerate
Learning
Pivot
It requires:
Focus
Breaking Work
Down
Swarming
28. What can you change so your
product can deliver value faster?
Copyright @ 2014 Agile Velocity, LLC All Rights Reserved. Agile Velocity Proprietary