{"id":21012,"date":"2019-08-19T08:58:46","date_gmt":"2019-08-19T13:58:46","guid":{"rendered":"https:\/\/blog.planview.com\/the-flow-framework-defects-as-warranty-costs\/"},"modified":"2019-08-19T08:58:46","modified_gmt":"2019-08-19T13:58:46","slug":"the-flow-framework-defects-as-warranty-costs","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/the-flow-framework-defects-as-warranty-costs\/","title":{"rendered":"The Flow Framework\u2122 \u2013 Defects as Warranty Costs"},"content":{"rendered":"
\n
\"The<\/div>\n<\/figure>\n

In my previous posts, I’ve talked about two flow Items from the Flow Framework™<\/a> and how they are analogous to other types of financial transactions. Tech debt is similar to financial debt<\/a> and risk items are similar to security costs<\/a>. Today, I’m going to discuss how defects are similar to warranty costs. <\/span><\/p>\n

Why<\/span> do we spend time fixing defects? It’s obvious why customers want defects fixed, but what’s in it for the software company? <\/span><\/p>\n

Software vendors fix defects because if they didn’t their customers would leave. That may not be so bad in the old days when you’d pay one time and buy software off the shelf, but now that software is priced as-a-service, you expect ongoing enhancements and fixes. Even back when software was sold in shrink-wrapped boxes, you’d still be able to get patches to download. <\/span><\/p>\n

In a SaaS (Software as a Service)<\/a> model, renewals are king. If customers get fed up and don’t renew, the metrics look bad, investors put their money elsewhere, and analysts decide to recommend other companies. <\/span>Which is where defect fixes come in. <\/span><\/p>\n

So in this financial modeling analogy, defect fixes are analogous to warranty costs. <\/span><\/p>\n

When a physical product goes out the door, it often has a warranty associated with it. The manufacturer promises to fix anything that fails within the first 30 days, 90 days or even the first year. Now, you’ve paid one time for the product, but the company realizes that you may want to buy from them again at some point, so they’re willing to lose a bit of money on you after your purchase. <\/span><\/p>\n

With software, you’re paying monthly or annually and in some respect, you’re never out of warranty. <\/span><\/p>\n

When the software ships, or gets pushed to the cloud servers, the vendor has either implicitly or explicitly made claims about what the software can do. Either way, when a flaw in the software is found, the vendor should make good on that promise and fix the defect.<\/span><\/p>\n

This warranty cost can also be thought of as customer retention cost. <\/span><\/p>\n

When it comes to trying to figure out how much capacity should go towards features vs. defects, the overarching goals of the business should be taken into account.<\/span><\/p>\n