If you ask “what is the ROI of context-driven testing” it is the same as asking:
- What is the value proposition of providing information to the stakeholders?
- Will management and customers pay for information?
Let me tell you a story: Just today I finally got around to changing tires on my car. Three months ago I bought a campaign voucher for a cheap switch of winter tires to summer tires – so it was about time. I booked a time and went to the shop with the summer tires in the trunk. BUT then … the front tires where out of shape due to wrong “tracing”, brake cables and other stuff worn and empty for lubrication. sigh!
So … the shop had to repair those critical defects (yeah, the vouchers a good business generator, #I’mOKwithThat). They gave me the keys to a replacement car for the day for free. And we discussed fixing some other stuff – the tricky ignition was Deffered/FixedUpStream but the defective brake lights added to the work order (New bug raised due to a hunch). I got an estimate and went for the day. The quote was pretty close, the repair on time and the requirements verified on the release bill.
And then they provides me with a list of a few things they noticed along the way.
- I probably paid for an automated test and configuration of a “trace” balancing – I assumed it there.
- We did discuss scope, price, schedule and timing – along with bug triage
- The shop did provide me with enough information and estimation up front to base my decisions on
- As the product owner I did not pay directly for the list of test ideas not covered – but I appreciated it!
The shop could have just swapped the tires for the voucher cost – and noticed nothing else. They could have chosen not to tell me about the additional bugs. They could not have offered me a replacement car for the day. They probably where more expensive than a moonlighting garage dude – I known now what the difference can be.
I value that they provide information to aid my business decision-making – besides just swapping the stupid tires. They will probably get repeat business from me – directly or indirectly. 🙂 And yes, Scott, they did have free coffee
5 thoughts on “Value of Information for Decisions”
[…] When the cost of more explicit testing activities is less than the information that testing can offer – then testing happens. Then more explicit testing activities have a positive ROI of information. […]
[…] I have experienced that attending conferences was a perk for “top brass” and “managers pets” (and that might have been me too *). But this post is not about me going again. No – I will get most of the buzzing through twitter and blogs anyhow, but the contacts on twitter et. al helps me to get a better ROI of information. […]
[…] Value of Information for Decisions […]
[…] for Minimum Viable Testing, Without Timing – Quality, Schedule and Cost is nothing, Value of Information for Decisions , 16 points that may rock the boat, When do testing happen? Are you looking […]
[…] The team expected testing to be checking the requirements, we worked for testing to support critical decision making […]