8 lessons learned from becoming agile

Download 8 lessons learned from becoming agile

Post on 12-May-2015

6.214 views

Category:

Technology

0 download

Embed Size (px)

DESCRIPTION

1.Why do you want to be agile?L1: Set a goal for being agile or you achieve nothingL2: Commit to agile values and principles; your practices will followL3: Piloting is learning. Learning is progress.2.How to reach business agility?L4: Business agility is about having adaptability and predictabilityL5: Create product vision and validate it with customer developmentL6: Find your Minimum Viable Product3.Organization as a people systemL7:Optimize the wholeL8: Build great teams

TRANSCRIPT

  • 1.8 lessons learned
    from becoming agile
    15.5.2010 ESTONIA
    Marko Taipale

2. Visited 13companies
Coached2agile transitions and 10+ teams
Co-founded1Lean startup
Trained over300people
3. Failed enough to tell stories
Succeeded enough to show results
4. 1.Why do you want to be agile?
2. How to reach business agility?
3.Organization as a people system
5. 1.Why do you want to be agile?
(Being = respect the values and principles)
6. 80%
had no goal for being agile
no method to reach the goal
no way to measure if they were getting any better
7. No Goal No chance to Score
8. Lesson #1
Set a goal for being agile, otherwise you achieve nothing
(Its ok to figure it out...)
9. What does method X
say about Y?
10. What does method X
say about Y?
Collaborate!
11. Lesson #2
Commit to agile values and principles; your practices will follow
Craft your own process
12. Pilot,
Scale,
Optimize
13. Pilot,
Scale,
Optimize
14. Pilot,
Scale,
Optimize
OR
Visualize the value stream
Fix the way you manage product development
Continuous Improvement
15. Pilot,
Scale,
Optimize
Multiple ways so whats the point?
OR
Visualize the value stream
Fix the way you manage product development
Continuous Improvement
16. Pilots are not about proving if agile works
Forward motion is often thought as progress
17. Lesson#3
Pilot is about learning
not working software
not about getting results
Continuous Improvement
18. 19. Make the cycle as short as possible
20. A way of learning
5whys
There are no technical problems only human problems
21. Lesson #1
You need to have a SMART goal
Lesson #2
Commit to agile values and principles; your practices will follow
Lesson #3
Progress is about learning
22. 2. How to reach business agility?
23. Agile teams need to value
adaptability over predictability
- Someone in Twitter
24. Lesson #4
Business agility is about having adaptability and predictability
- My experience
25. Where do I get the backlog? what to build
26. 27. No plan survives first contact with the customers
- Steven Blank
28. Customer Development
Customer
Discovery
Customer
Validation
Customer
Creation
Scale
Company
29. Customer Development
Customer
Discovery
Customer
Validation
Customer
Creation
Scale
Company
Hypotheses, experiments,
insights
Data,
feedback,
Insights
Agile
Product
Development
30. Customer Development
Problem Team
Customer
Discovery
Customer
Validation
Customer
Creation
Scale
Company
Hypotheses, experiments,
insights
Solution Team
Data,
feedback,
Insights
Agile
Product
Development
31. Should I do whatever my customers want me to do?
32. Should I do whatever my customers want me to do?
33. Lesson #5
Create product vision and validate it with customer development
Vision
= a boundary for her wishes
34. Is agile about delivering features
as fast as possible?
35. Nr 1 waste =
Unused features
Building a feature maybe the wrong answer
Who cares about velocity?
We can work on highest priority story who cares?
36. It is not about how much but rather how little you can release
Minimum Viable Product
37. Lesson #6
Find your Minimum Viable Product
It should make you feel embarrassed
38. It's the things that are not there that we are most proud of"
39. Lesson #4
Business agility is about having adaptability and predictability
Lesson #5
Create product vision and validate it with customer development
Lesson #6
Find your Minimum Viable Product
40. 3.Organization as a people system
41. We have Scrum but we are still slow!
42. Customer
approval
Internal
approval
Idea
Resourcing
Development
Design
Deployment
43. Customer
approval
Internal
approval
Idea
Resourcing
2h
2h
1d
Development
Design
Deployment
2m
1m
3w
3m
44. Selected
ideas
8
Customer
approval
Internal
approval
Idea
Resourcing
1m
2d
6m
2h
2h
1d
1w
6m
6m
Development
Design
Deployment
2m
1m
3w
15
12
3m
24m
Design
ready
Production
ready
45. Selected
ideas
8
Customer
approval
Internal
approval
Idea
Resourcing
1m
2d
6m
2h
2h
1d
SCRUM!
1w
6m
6m
Development
Design
Deployment
2m
1m
3w
15
12
3m
24m
Design
ready
Production
ready
46. Selected
ideas
8
Customer
approval
Internal
approval
Idea
Resourcing
1m
2d
6m
2h
2h
1d
SCRUM!
1w
6m
6m
Development
Design
Deployment
2m
1m
3w
15
12
3m
24m
Design
ready
Production
ready
47. Lesson #7
Optimize the whole
Beware sub-optimization
Visualize the value stream
Identify bottleneck
Limit WIP on all levels
Incentives are bad!
48. Adoption is about letting problems to surface
Manage the system, remove chance for failure, make it flow
49. 50. Smell: The fear of being vulnerable
Leader: Go First
51. Smell: The desire to preserve artificial harmony
Leader: Mine for Conflict
Smell: The fear of being vulnerable
Leader: Go First
52. Smell: The lack of clarity or buy-in
Leader: Force Clarity and Closure
Smell: The desire to preserve artificial harmony
Leader: Mine for Conflict
Smell: The fear of being vulnerable
Leader: Go First
53. Smell: The need to avoid interpersonal discomfort
Leader: Confront Difficult Issues
Smell: The lack of clarity or buy-in
Leader: Force Clarity and Closure
Smell: The desire to preserve artificial harmony
Leader: Mine for Conflict
Smell: The fear of being vulnerable
Leader: Go First
54. Smell: The pursuit of individual goals and status
Leader: Focus on Collective Outcomes
Smell: The need to avoid interpersonal discomfort
Leader: Confront Difficult Issues
Smell: The lack of clarity or buy-in
Leader: Force Clarity and Closure
Smell: The desire to preserve artificial harmony
Leader: Mine for Conflict
Smell: The fear of being vulnerable
Leader: Go First
55. Lesson #8
Build great teams
56. Marko Taipale
@markotaipale
huitale.blogspot.com
marko.taipale@huitale.com
I help companies to improve by
showing what I have done
how I have done it and
what I have learned about it.
I am a CTO of a lean startup
57. Why do you want to be agile?
L1: Set a goal for being agile or you achieve nothing
L2: Commit to agile values and principles; your practices will follow
L3: Piloting is learning. Learning is progress.
2. How to reach business agility?
L4: Business agility is about having adaptability and predictability
L5: Create product vision and validate it with customer development
L6: Find your Minimum Viable Product
3.Organization as a people system
L7:Optimize the whole
L8: Build great teams
58. Photo credits
Flickr users
http://www.flickr.com/photos/kodomut/
http://www.flickr.com/photos/amagill/
http://www.flickr.com/photos/themarmot/
http://www.flickr.com/photos/unloveable/
http://www.flickr.com/photos/shapourbahrami/
http://www.flickr.com/photos/thatguyfromcchs0
http://www.flickr.com/photos/fxtreme/
http://www.flickr.com/photos/aussiegall
http://www.flickr.com/photos/lululemonathletica
http://www.flickr.com/photos/4yas
http://www.flickr.com/photos/sualk61/
http://www.flickr.com/photos/can3ro55o/
http://www.flickr.com/photos/jwdill/
http://www.flickr.com/photos/minidriver/
http://www.flickr.com/photos/donaldmacleod/
http://www.flickr.com/photos/jburgin/
http://www.flickr.com/photos/jmherrala/