My Customer Won't Accept Smaller Releases
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

My Customer Won't Accept Smaller Releases

on

  • 1,827 views

Ignite talk at Lean Kanban North America 2013 on responding to the argument that customers won't accept smaller releases

Ignite talk at Lean Kanban North America 2013 on responding to the argument that customers won't accept smaller releases

Statistics

Views

Total Views
1,827
Views on SlideShare
1,714
Embed Views
113

Actions

Likes
3
Downloads
10
Comments
0

5 Embeds 113

https://twitter.com 56
http://eventifier.co 39
http://ec2-54-243-189-159.compute-1.amazonaws.com 13
http://eventifier.com 4
http://www.1agile.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Hello my name is Jason Yip, I’m a Principal Consultant at ThoughtWorks. Today I’d like to talk about a common refrain that I’m sure you’ve all heard before. “My customers won’t accept smaller releases.” I will suggest that this is not the real problem.
  • The real problem is that our consumption transaction cost is too high. That phrase might not sound too familiar so left me try to explain. To do that let’s look at something we should be more familiar with.

My Customer Won't Accept Smaller Releases Presentation Transcript

  • 1. “My customers won’t accept smaller releases”Jason Yipjcyip@thoughtworks.comj.c.yip@computer.org@jchyiphttp://jchyip.blogspot.com
  • 2. The real problem is that our consumptiontransaction cost is too high.
  • 3. Overall Costof ReleaseCost of EachReleaseFrequencyof ReleasesReduce this By reducing thisWRONG!
  • 4. Overall Costof ReleaseCost of EachReleaseFrequencyof ReleasesAnd maintainor reduce thisIncreasethisBy reducing thisRIGHT!
  • 5. OverallImpact onCustomersCustomerimpact perreleaseFrequencyof ReleasesReduce this By reducing thisWRONG!
  • 6. Transactioncosts of areleaseProductiontransactioncostsConsumptiontransactioncosts• Cost of testing• Cost of deployment• Cost of management• Cost of fixes
  • 7. ConsumptiontransactioncostThe sum of any costsborne by consumers of aproduct or service tolearn about and/oraccept changes to thatproduct or service
  • 8. ConsumptiontransactioncostCost ofdefectsCost oflearning
  • 9. Defects require users to compensatefor expected functionality that nolonger worksDidn’t auto-saveuse to work?
  • 10. New or modified UI elements orfunctionality impose a learning costWhat’s thisribbonthing?!?
  • 11. Consumption costs can lead toproduction costs (e.g., training)Uh, no one seemsto know how touse our system…No problem! We’ll justdo more training!
  • 12. ConsumptiontransactioncostCost ofdefectsCost oflearningTo reduce thisReducethisReducethisAND
  • 13. Standard defect reduction approachesapplyExploratory testingBuild pipelines
  • 14. http://www.uie.com/articles/magic_escalator/(Aka cost of learning)Reduce this by reducingthe size of the change
  • 15. http://www.uie.com/articles/magic_escalator/(Aka cost of learning)Better interaction designreduces the amount ofknowledge needed to beacquired
  • 16. http://www.uie.com/articles/magic_escalator/(Aka cost of learning)Test the size of this usinguser testing
  • 17. To reduce production transactioncosts: smaller batches, build-in-quality, design for production
  • 18. To reduce consumption transactioncosts: smaller batches, built-in-quality, design for consumption
  • 19. Your customer won’t accept smallerreleases?How might you reduce the cost youimpose on them for receiving it?
  • 20. What are the quality of the releases?How easy is it to learn how to use theproduct or service?