Comments on: Part Three – A Response to “Traps & Pitfalls of Agile Development – A Non-Contrarian View” http://lostechies.com/christaylor/2009/02/10/part-three-a-response-to-traps-amp-pitfalls-of-agile-development-a-non-contrarian-view/ Just another LosTechies site Sat, 17 Jul 2010 12:12:07 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Chris Taylor http://lostechies.com/christaylor/2009/02/10/part-three-a-response-to-traps-amp-pitfalls-of-agile-development-a-non-contrarian-view/#comment-17 Chris Taylor Wed, 11 Feb 2009 15:03:19 +0000 /blogs/agilecruz/archive/2009/02/10/part-three-a-response-to-traps-amp-pitfalls-of-agile-development-a-non-contrarian-view.aspx#comment-17 Thank you, Louis! And yours is a very good point. I have seen DDD help with exactly this pitfall. Sometimes, though, there are bound to be issues that fall through the cracks despite our best efforts. I rely heavily on TDD and Continuous Integration to assist with refactoring exercises that occur when our understanding of business concepts undergo refinement. All in my humble opinion... Thanks for your comment! Thank you, Louis!

And yours is a very good point. I have seen DDD help with exactly this pitfall.

Sometimes, though, there are bound to be issues that fall through the cracks despite our best efforts. I rely heavily on TDD and Continuous Integration to assist with refactoring exercises that occur when our understanding of business concepts undergo refinement.

All in my humble opinion…

Thanks for your comment!

]]> By: Louis Salin http://lostechies.com/christaylor/2009/02/10/part-three-a-response-to-traps-amp-pitfalls-of-agile-development-a-non-contrarian-view/#comment-16 Louis Salin Tue, 10 Feb 2009 19:13:57 +0000 /blogs/agilecruz/archive/2009/02/10/part-three-a-response-to-traps-amp-pitfalls-of-agile-development-a-non-contrarian-view.aspx#comment-16 Great post! I think the YAGNI pitfall can be mitigated by using some form of DDD. If you have a proper domain model, then it could be easier to detect if you are going to need this or that. Great post!
I think the YAGNI pitfall can be mitigated by using some form of DDD. If you have a proper domain model, then it could be easier to detect if you are going to need this or that.

]]>