Comments on: The Organizational Impact of Poor Software Quality http://saasinterrupted.com/2010/02/01/the-organizational-impact-of-poor-software-quality/ -- A blog by Ashish Soni. Wed, 03 Nov 2010 23:57:46 +0000 hourly 1 http://wordpress.com/ By: Nathan Mc http://saasinterrupted.com/2010/02/01/the-organizational-impact-of-poor-software-quality/#comment-143 Sun, 18 Apr 2010 15:50:27 +0000 http://saasinterrupted.com/?p=63#comment-143 And let’s not forget the cumulative effect of outages for operations. Assuming you’re not a large corporation with one team handling system issues and another devoted to project work, all production project work is going to slip. This invariably cascades backward through engineering, professional services, sales, you name it.

Not to mention the fact that your ops team is going to be exhausted, irritable and accident-prone for AT LEAST one day per outage.

99.999 percent uptime isn’t just for customers.

]]> By: Henry M http://saasinterrupted.com/2010/02/01/the-organizational-impact-of-poor-software-quality/#comment-68 Tue, 02 Feb 2010 13:16:33 +0000 http://saasinterrupted.com/?p=63#comment-68 Right on. SaaS providers need to focus on QoE – Quality of Experience since it’s way too easy for customers to simply google-click-and-switch. Start outside and see what matters to customers first, then move inside to fix that.

]]> By: Anonymous http://saasinterrupted.com/2010/02/01/the-organizational-impact-of-poor-software-quality/#comment-58 Tue, 02 Feb 2010 01:26:42 +0000 http://saasinterrupted.com/?p=63#comment-58 I hate to say it, but you are so right with this article. I work in a company that releases poor software, poor UI, and the manager of the dev team is clueless. This effects every part of the organization (billing [issues with invoices/reports], sales, marketing, etc).

It has been slowing us down immensely over the last year.

]]>