Update 2016-12-27-discovery.md

[KrisSaxton]

• fixes some small typos
  Comments:
  +1 for the Top 8 fails :)
  Can you add an example of an assumption?
  I think it would be helpful to include references for how you determine Cost and Value (e.g. Art of Business Value)

[scottcolfer]

Cheers Kris.

Top 8 fails
I'll add this in.

Example of an assumption
I'm trying to figure out how to include examples that flesh this out without the post becoming too epic in length.
I've identified the key assumptions that are made (problem, user and solution), are you looking for real examples to better explain each of the categories. I could draw out the Cloud Platform assumption that devs wanted lots of options and features, when in reality they wanted simplicity, sensible defaults and self-service.

Cost and value
I've not read that book, is it good?

Value is interesting to figure out in public sector. Cloud Platform has often been pretty simple (migrating hosting to AWS saves 70% costs; centralising tools has reduced the number of WebOps per product). Lots of other products are looking at the value of saving time, e.g. HQ & ALB apps may not have been updated for years; without updates, you might have 500 users wasting 15 minutes per day because of work arounds which that's a cost of 125 hours every day or (assuming 200 working days per year) 25000 hours per year. Let's randomly guess an average salary of £30K (ish) per year (?), that's approx. £15 per hour. So we can estimate that the value of running updates is 2500015 or £375,000. So, the cost of running updates needs to be significantly less than £375,000 to go ahead. A conservative rule of thumb I've heard is five times less, to ensure a high likelihood of return on investment.*
/\ These are a couple of very specific examples but I guess you're looking for more general categories of cost and value into which these would fall?

[KrisSaxton]

Think your suggested assumption is a really good one. Yeah, Art of Business Value is good (and short too) K

…

On 12 Jan 2017, at 19:34, Scott ***@***.***> wrote: Cheers Kris. Top 8 fails I'll add this in. Example of an assumption I'm trying to figure out how to include examples that flesh this out without the post becoming too epic in length. I could draw out the Cloud Platform assumption that devs wanted lots of options and features, when in reality they wanted simplicity, sensible defaults and self-service. Cost and value I've not read that book, is it good? Value is interesting to figure out in public sector. Cloud Platform has often been pretty simple (migrating hosting to AWS saves 70% costs; centralising tools has reduced the number of WebOps per product). Lots of other products are looking at the value of saving time, e.g. HQ & ALB apps may not have been updated for years; without updates, you might have 500 users wasting 15 minutes per day because of work arounds which that's a cost of 125 hours every day or (assuming 200 working days per year) 25000 hours per year. Let's randomly guess an average salary of £30K (ish) per year (?), that's approx. £15 per hour. So we can estimate that the value of running updates is 2500015 or £375,000. So, the cost of running updates needs to be significantly less than £375,000 to go ahead. A conservative rule of thumb I've heard is five times less, to ensure a high likelihood of return on investment.* /\ These are a couple of very specific examples but I guess you're looking for more general categories of cost and value into which these would fall? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.