Using Class of Service to Manage Product Risk

1,622 views
1,527 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,622
On SlideShare
0
From Embeds
0
Number of Embeds
109
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Using Class of Service to Manage Product Risk

  1. 1. Using Class Of Service To Manage Product Risk Siddharta Govindaraj [email_address] Sreekanth Tadipatri [email_address]
  2. 2. This webinar is being recorded Slides will be made available Use #enterprisekanban to tag your tweets
  3. 3. Siddharta Govindaraj Director, Silver Stripe Software Pvt Ltd Email: [email_address] Twitter: @toolsforagile Sreekanth Tadipatri Senior Consultant, DeccanTech Email: [email_address] Twitter: @bugbasher
  4. 4. Silver Catalyst A tool for distributed agile development teams Supports Scrum and Kanban Silver Stories A tool for cross-team product management Currently in beta Supports user story mapping and enterprise kanban
  5. 5. Agenda Introduction Types of Product Risk Three Types of Features Cost of Delay Model Using Class of Service
  6. 6. Agenda Introduction Types of Product Risk Three Types of Features Cost of Delay Model Using Class of Service
  7. 7. <ul>Companies Hoping to Do Well Have Little Choice but to Produce Radically Improved Products </ul>
  8. 8. New Product Continuum Discontinuous (New to the world) New consumption pattern Radio, TV Continuous (Incremental) Same consumption pattern Coffee to Decaf
  9. 9. <ul>The degree of product Newness </ul><ul>Newness to the Company </ul><ul>Newness to the target customers </ul><ul>New-to-the-world </ul><ul>High </ul><ul>Low </ul><ul>Reduced Costs </ul><ul>Product </ul><ul>Repositioning </ul><ul>to Existing Product Lines </ul><ul>Products </ul><ul>20% </ul><ul>26% </ul><ul>10% </ul><ul>7% </ul><ul>26% </ul><ul>Low </ul><ul>High </ul><ul>11% </ul><ul>New </ul><ul>Product </ul><ul>Lines </ul><ul>Revisions / Improvements </ul>
  10. 10. Agenda Introduction Types of Product Risk Three Types of Features Cost of Delay Model Using Class of Service
  11. 11. Functionality Well Understood High Uncertainty Commodity Market Risk Tech Risk
  12. 12. Commodity Market Risk Tech Risk
  13. 13. For commodity projects, we need to focus on business value
  14. 14. For commodity projects, we need to focus on business value For strategic projects, we need to focus on risk mitigation
  15. 15. To mitigate product risk, focus on learning Market Risk: Make cheap prototypes and validate them with your target market Technology Risk: Spike early to understand technical challenges Don't (yet) worry about quality or delivering every sprint
  16. 16. Jeff Patton's Chess Analogy © Jeff Patton
  17. 17. Agenda Introduction Types of Product Risk Three Types of Features Cost of Delay Model Using Class of Service
  18. 19. Basic Performance Excitement Take pictures, browse and delete pictures, autofocus File formats, camera modes, pre-set settings Image quality, resolution, changable lens, underwater use
  19. 20. Agenda Introduction Types of Product Risk Three Types of Features Cost of Delay Model Using Class of Service
  20. 22. Agenda Introduction Types of Product Risk Three Types of Features Cost of Delay Model Using Class of Service
  21. 23. Expedite
  22. 24. Class of Service Criteria Expedite Emergency bug fixes that need to be fixed and deployed in a few days Fixed Date Features that have a fixed deadline High Uncertainty Features exposed to market or technical risk. Basic Basic features from the Kano model High Value Differentiating features from the Kano model Slack Intangible, long term improvements, to be picked up during times of slack Normal Everything else
  23. 25. Expedite * Only for emergency bug fixes * Moves to the head of backlog and all queues * Can override work in progress limits * Team members stop whatever they are working on and swarm to complete this work item
  24. 26. High Uncertainty * High market or technology risk * Skip automated test stage
  25. 27. High Value * Requires user experience stage * Requires additional automated tests * Requires additional manual exploratory tests
  26. 28. Benefits Better business – development alignment Risk oriented view of the backlog
  27. 29. Risk oriented view What if you have many high uncertainty items on the backlog?
  28. 30. Risk oriented view What is the mixture of basic, linear and differentiating work items?
  29. 31. Risk oriented view Can we amortize highly risky features over a period of time by breaking them down into smaller pieces and tackle them one by one?
  30. 32. Risk oriented view Should we balance a release containing a high uncertainty feature with well understood basic features?
  31. 33. Risk oriented view What is the long term impact of having too many expedite requests?
  32. 34. Questions? Siddharta Govindaraj Director, Silver Stripe Software Pvt Ltd Email: [email_address] Twitter: @toolsforagile Sreekanth Tadipatri Senior Consultant, DeccanTech Email: [email_address] Twitter: @bugbasher

×