Comments on: Technical Debt: Refactoring vis-a-vis Starting Afresh http://theagileexecutive.com/2009/11/10/technical-debt-refactoring-vis-a-vis-starting-afresh/ Making Agile Work Mon, 16 Jan 2012 14:09:12 +0000 hourly 1 http://wordpress.com/ By: Israel Gat http://theagileexecutive.com/2009/11/10/technical-debt-refactoring-vis-a-vis-starting-afresh/#comment-747 Thu, 12 Nov 2009 13:15:16 +0000 http://theagileexecutive.com/?p=3586#comment-747 No doubt indeed, “you’re starting with the knowledge you’ve learned over the years building and supporting a product in the market.” I would add that you start as well with the ongoing needs of the customer base using your legacy sysyem. The way you cater to (or fail to cater to) their operational and business needs while working on and introducing the new software is your acid test.

Israel

]]> By: Todd Olson http://theagileexecutive.com/2009/11/10/technical-debt-refactoring-vis-a-vis-starting-afresh/#comment-745 Thu, 12 Nov 2009 03:39:14 +0000 http://theagileexecutive.com/?p=3586#comment-745 Nice post. I appreciate that you proposed a model to evaluate this decision.

However, in practice I find that teams and organizations rarely consider starting afresh. It’s often written off as being impossible without any analysis at all.

I encourage teams I work with to evaluate starting afresh even it seems impossible. Of course, you need to be smart about changes like this, but you are never starting completely new. You’re starting with the knowledge you’ve learned over the years building and supporting a product in the market.

]]>