Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

35
roliina Luoto · Scan Agile 2017 March 2, 15:00, Track 2 Why agile customers become monsters? And how can they be helped?

Transcript of Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Page 1: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Karoliina Luoto · Scan Agile 2017 March 2, 15:00, Track 2

Why agile customers become monsters?And how can they be helped?

Page 2: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Karoliina Luoto + CodentoConsultant and Coach for Agile Lean development Focus: product leadershipBefore: systems agilist, collaboration specialist, product owner

Change agent’s right handin lean software development

Page 3: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Let me tell youA story

[email protected] · @totoroki · +358 40 765 8504

Page 4: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Photo: Sam Howzit, FlickrPicture: Malabooboo, Flickr

Monsters Inc.Wanted to develop an e-child-scarer

Picture: © Disney Pixar

Page 5: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

The productmanager team had heard about this Scrum thing and wanted to try it out

Picture: © Disney Pixar

Page 6: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Photo: Sam Howzit, FlickrPicture: Malabooboo, Flickr

A company called Monsters Inc.Wanted to develop an e-child-scarer

Picture: © Disney Pixar

The project boardWas a bit suspicious about agile

Picture: © Disney Pixar

Page 7: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Photo: Sam Howzit, FlickrPicture: Malabooboo, Flickr

A company called Monsters Inc.Wanted to develop an e-child-scarer

Picture: © Disney Pixar

But the e-scarer had potential- So they found the money

Page 8: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

The brand new Product Owner was super happy about how Scrum seemed

”We don’t need to plan, we’ll just find a team, start developing and see what happens!”

Picture: © Disney Pixar

Page 9: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Picture: © Disney Pixar

The Development Team Was talented and visionated

Page 10: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Picture: © Disney Pixar

The Product Manager TeamWorked their arses off

Page 11: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Picture: © Disney Pixar

Writing and prioritizingBacklog items

Page 12: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

And the team really got Sprint goals completed

Page 13: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

And the team really got Sprint goals completedOften Sprint ReviewsWere revelations for POs

Picture: © Disney Pixar

Page 14: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

So this is the kind of productWe are building! Seems Excellent!

Picture: © Disney Pixar

Page 15: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

POs got loads of user feedbackAnd tried to answer it all

Picture: © Disney Pixar

Page 16: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Time flied, project board tiredWhen do we get the results?

Picture: © Disney Pixar

Page 17: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

The Scrum Team did greatBut nobody seemed to understand

Picture: © Disney Pixar

Page 18: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Finally the PO burnoutedIt seemed impossible to succeed

Picture: © Disney Pixar

Page 19: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

The project was shut down:”Agile is not for us”

Picture: © Disney Pixar

Page 20: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Picture: © Disney Pixar

Page 21: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Picture: © Disney Pixar

It’s easy to loose the visionIn the middle of everything

Page 22: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Monsters returned to The old manual scaring system

Picture: © Disney Pixar

Page 23: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

*The dev team was baffledWhat had gone wrong?

The team and others were baffledWhat had gone wrong?

The team was baffledWhat had they done wrong?

Page 24: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

So how could theDevelopment Team have helped?

Page 25: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Agile Client Hand-Holder Testfor Scrum Masters and Dev Teams1. Have you had a liftoff (kickoff) for both methods AND

product vision?

Test by: Karoliina Luoto

2. Have you asked for project management vision on the value of the product? Vision document? Lean canvas?

3. Does your Product Owner have an overall product plan, like a user story map?

8. Have you told the Product Owner what you feel is worth focusing on? 9. Are you focusing on 20 % solutions that can fulfill 80 % of the need?

6. Are the decision-makers attending reviews?

4. Are you asking the PO to test – early and often?

7. Is your Product Owner attending retrospectives?

5. Is someone tracking user value over sprints?

Page 26: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Tools forHelping out the client

Picture: © Disney Pixar

Page 27: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Make them doA vision canvas

It forces to check all the basics are thought throughIf the vision is clear, it will only take them an hourFocus on the validations – how are the assumptions verified?

Picture: © Disney Pixar

Page 28: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters
Page 29: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Make them doA product map

Free-choice technique,essential to see the whole productHelps planning for Minimum Lovable Product

Picture: © Disney Pixar

Helps inspection of progress

Page 30: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Users (described with personas)

Activities e.g. ”cookinglunch”

Stepse.g. ”making the sauce”

Details e.g. ”adding wine”

Releaseslice

User Story Mapping

Model by: Jeff Patton

Page 31: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Get value feedbackFrom Users in Sprints

”Would you recommend this to a friend?”

Get the feedback to the board

Light protos, open betas, A/B testing…Do not trust the loud minority

Picture: © Disney Pixar

Page 32: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Picture: gdsteam, Flickr

Page 33: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

It’s about value managementAnd you can help!

Picture: © Disney Pixar

Page 34: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

The End Codento.com

Karoliina Luoto · @totoroki · +358 40 765 8504

Page 35: Karoliina Luoto, Scan Agile 17: Why agile customers become monsters

Further tools and readingGreetings to your Product Owner • Karoliina Luoto: Tuoteomistajan Scrum-pikaopas

http://content.codento.fi/download/tuoteomistajan-scrum-pikaopas

• Downloadable vision canvas in Finnish: http://www.codento.fi/lataa-lean-visiolakana-ohjelmistoprojektiisi/

• Downloadable vision canvas in English: http://www.codento.fi/en/service/agile-methodologies-and-lean/

• Jeff Patton: User Story mappinghttp://jpattonassociates.com/user-story-mapping/