Comments on: Sacrificing Quality should be an Executive Management Decision http://adams.id.au/blog/2006/07/sacrificing-quality-should-be-an-executive-management-decision/ Technology, mountain biking, politics & music. Thu, 09 Sep 2010 04:44:25 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Eva private blog http://adams.id.au/blog/2006/07/sacrificing-quality-should-be-an-executive-management-decision/comment-page-1/#comment-10 Eva private blog Sat, 04 Aug 2007 07:16:13 +0000 http://adams.id.au/blog/2006/07/sacrificing-quality-should-be-an-executive-management-decision/#comment-10 <strong>Eva...</strong> i like it :)... Eva…

i like it :)…

]]> By: Marc Loxton http://adams.id.au/blog/2006/07/sacrificing-quality-should-be-an-executive-management-decision/comment-page-1/#comment-9 Marc Loxton Tue, 17 Oct 2006 21:27:13 +0000 http://adams.id.au/blog/2006/07/sacrificing-quality-should-be-an-executive-management-decision/#comment-9 This is something I've been struggling with lately. The thing is are executive manager aware of the consequences of sacrificing quality? Can they make any kind of informed decision in this area? The project I'm on called for some big changes to the thin and useless domain model it had so I had begun a rewrite as part of new features I was implementing. Of course this took time though it is the right thing to do in terms of quality: fixing previous bad design decisions. Increasing "management" pressureto see tangable results pushed me to cut corners in the implementation thinking it's isolated behind the interface so that way I can fix it later without affecting much else ... should this kind of thing be a management decision? How much of it should we try and explain to them? This is something I’ve been struggling with lately. The thing is are executive manager aware of the consequences of sacrificing quality? Can they make any kind of informed decision in this area? The project I’m on called for some big changes to the thin and useless domain model it had so I had begun a rewrite as part of new features I was implementing. Of course this took time though it is the right thing to do in terms of quality: fixing previous bad design decisions. Increasing “management” pressureto see tangable results pushed me to cut corners in the implementation thinking it’s isolated behind the interface so that way I can fix it later without affecting much else … should this kind of thing be a management decision? How much of it should we try and explain to them?

]]>