Architecture makes Agile Processes Scalable

re: Architecture makes Agile Processes Scalable

Akshyadeep Raghav — Wed, 20 May 2009 16:29:35 GMT

Nick... nice thoughts and article, I wanna put loads of comment on this one, will probabily write whenver gets time.

You loves architecture :)

re: Architecture makes Agile Processes Scalable

Dave Sammut — Mon, 25 May 2009 11:11:23 GMT

Good insight, we've had a similar experience where Domain Driven Design techniques were applied to achieve an agile 'friendly' architecture.

re: Architecture makes Agile Processes Scalable

byjujoy — Tue, 26 May 2009 21:59:25 GMT

...a convincing example on benefits of decoupling and implementing web service/contracts. Good article.

But how about the code we inherited? Is it worth refactoring spending again around 5-20% of original effort? A stitch in time saves nine. Probably it is too late to re-architect the inherited/legacy code. However this sure will work cool with newish applications. Unfortunately we still need to maintain old code, and release weekends are horrifying.

re: Architecture makes Agile Processes Scalable

NickMalik — Thu, 28 May 2009 19:26:02 GMT

Hi Byjujoy,

>>Is it worth refactoring spending again around 5-20%..."<<

You tell me. Is there a specific business problem you can solve by adding architecture? If you are not adding architecture, are you adding test cases? (Two different things, for two different, complimentary, reasons).

If you cannot solve a business problem by refactoring the code, then perhaps you don't. You say that "release weekends" are horrifying... are they unsustainable? Does quality suffer? Do your customers suffer? If so, go back to the business and ask them if they want to reduce those impacts. If they say yes, then add JUST ENOUGH architecture (and test case coverage) to solve that problem.

I wouldn't add architecture if it is not needed to solve a problem.

--- N