Top Banner
lessons learned rom becoming agile 15.5.2010 ESTONIA Marko Taipale
58

8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Dec 17, 2015

Download

Documents

Barbra Richards
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

8 lessons learnedfrom becoming agile

15.5.2010 ESTONIAMarko Taipale

Page 2: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Visited 13 companies

Coached 2 agile transitions and

10+ teams

Co-founded 1 Lean startup

Trained over 300 people

Page 3: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Failed enough to tell stories

Succeeded enough to show results

Page 4: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

1. Why do you want to be

agile?

2. How to reach business agility?

3. Organization as a people system

Page 5: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

1. Why do you want to be

agile? (Being = respect the values and principles)

Page 6: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

80% had no goal for being agile

no method to reach the goal …

no way to measure if they were getting any better

Page 7: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

No Goal – No chance to Score

Page 8: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #1Set a goal for being agile, otherwise you

achieve nothing

(It’s ok to figure it out...)

Page 9: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

“What does method X say about Y?”

Page 10: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

“What does method X say about Y?”

Collaborate!

Page 11: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #2Commit to agile values and

principles; your practices will follow

Craft your own process

Page 12: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Pilot, Scale, Optimize

Page 13: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Pilot, Scale, Optimize

Page 14: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Pilot, Scale, Optimize

OR 1) Visualize the value stream 2) Fix the way you manage product

development3) Continuous Improvement

Page 15: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Pilot, Scale, Optimize

OR 1) Visualize the value stream 2) Fix the way you manage product

development3) Continuous Improvement

Multiple ways so what’s the point?

Page 16: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Pilots are not about proving if agile works

Forward motion is often thought as progress

Page 17: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #3Pilot is about learning

…not “working software”… not about getting results

Continuous Improvement

Page 18: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.
Page 19: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Make the cycle as short as possible

Page 20: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

A way of learning

5 whys

There are no technical problems only human problems

Page 21: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #1You need to have a SMART goal

Lesson #2Commit to agile values and principles; your practices will follow

Lesson #3Progress is about learning

Page 22: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

2. How to reach business agility?

Page 23: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

”Agile teams need to value adaptability over predictability”- Someone in Twitter

Page 24: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #4Business agility is about having adaptability and predictability- My experience

Page 25: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

” Where do I get the backlog?” what to build

Page 26: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.
Page 27: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

“No plan survives first contact with the customers”- Steven Blank

Page 28: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

CustomerDiscovery

CustomerValidation

CustomerCreation

ScaleCompany

Customer Development

Page 29: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

CustomerDiscovery

CustomerValidation

CustomerCreation

ScaleCompany

AgileProduct

Development

Data, feedback,

Insights

Hypotheses, experiments,

insights

Customer Development

Page 30: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

CustomerDiscovery

CustomerValidation

CustomerCreation

ScaleCompany

AgileProduct

Development

Data, feedback,

Insights

Hypotheses, experiments,

insights

Customer Development

Problem Team

Solution Team

Page 31: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

“Should I do whatever my customers want me to do?”

Page 32: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

“Should I do whatever my customers want me to do?”

Page 33: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #5Create product vision and validate it with customer development

Vision = a boundary for her wishes

Page 34: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Is agile about delivering features as fast as possible?

Page 35: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Who cares about velocity?We can work on highest priority story – who cares?

Nr 1 waste = Unused features

Building a feature maybe the wrong answer

Page 36: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

It is not about how much but rather how little you can release

Minimum Viable Product

Page 37: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #6Find your Minimum Viable Product

It should make you feel embarrassed

Page 38: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

“It's the things that are not there that we are most proud of"

Page 39: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #4Business agility is about having adaptability and predictability

Lesson #5Create product vision and validate it with customer development

Lesson #6Find your Minimum Viable Product

Page 40: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

3. Organization as a people system

Page 41: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

”We have Scrum but we are still slow!”

Page 42: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

DevelopmentDesign

Customerapproval

Internalapproval

Idea Resourcing

Deployment

Page 43: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Development

2m

Design

1m

Customerapproval

2h

Internalapproval

2h

Idea Resourcing

1d

Deployment

3w

3m

Page 44: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Development

2m15

Designready

6m

1w

Design

1m

1m

Customerapproval

2h2d

Internalapproval

2h

Idea6m

Resourcing

1d

8

Selected ideas

Deployment

3w12

Productionready

6m

3m24m

Page 45: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Development

2m15

Designready

6m

1w

Design

1m

1m

Customerapproval

2h2d

Internalapproval

2h

Idea6m

Resourcing

1d

8

Selected ideas

Deployment

3w12

Productionready

6m

SCRUM!

3m24m

Page 46: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Development

2m15

Designready

6m

1w

Design

1m

1m

Customerapproval

2h2d

Internalapproval

2h

Idea6m

Resourcing

1d

8

Selected ideas

Deployment

3w12

Productionready

6m

SCRUM!

3m24m

Page 47: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Optimize the whole

Lesson #7

Beware sub-optimization Visualize the value streamIdentify bottleneckLimit WIP on all levelsIncentives are bad!

Page 48: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Adoption is about letting problems to surface

Manage the system, remove chance for failure, make it flow

Page 49: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.
Page 50: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Smell: The fear of being vulnerable Leader: Go First

Page 51: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Smell: The fear of being vulnerable Leader: Go First

Smell: The desire to preserve artificial harmony Leader: Mine for Conflict

Page 52: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Smell: The fear of being vulnerable Leader: Go First

Smell: The desire to preserve artificial harmony Leader: Mine for Conflict

Smell: The lack of clarity or buy-in Leader: Force Clarity and Closure

Page 53: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Smell: The fear of being vulnerable Leader: Go First

Smell: The desire to preserve artificial harmony Leader: Mine for Conflict

Smell: The lack of clarity or buy-in Leader: Force Clarity and Closure

Smell: The need to avoid interpersonal discomfortLeader: Confront Difficult Issues

Page 54: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Smell: The fear of being vulnerable Leader: Go First

Smell: The desire to preserve artificial harmony Leader: Mine for Conflict

Smell: The lack of clarity or buy-in Leader: Force Clarity and Closure

Smell: The need to avoid interpersonal discomfortLeader: Confront Difficult Issues

Smell: The pursuit of individual goals and statusLeader: Focus on Collective Outcomes

Page 55: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Lesson #8Build great teams

Page 56: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

I help companies to improve by showing what I have donehow I have done it and what I have learned about it.

I am a CTO of a lean startup

Marko Taipale

@markotaipale

huitale.blogspot.com

[email protected]

Page 57: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

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 Product

3. Organization as a people systemL7: Optimize the wholeL8: Build great teams

Page 58: 8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Photo creditsFlickr 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/