By fdiotalevi
via infoq.com
Published: Jun 13 2008 / 16:31
Architecture is perceived as a heavy-weight activity which does not fit well into an Agile process, so many teams start without it, just to find themselves re-doing the software later because the code structure was not good enough to support maintainability and growth. Because the domain was not understood in the first place, the code that reflects it needs to be changed beyond the point of refactoring, and when that happens some architectural decisions are to be made. That defers the initial software design to a later point, introducing unnecessary delays and costs in the project.
Add your comment
Voters For This Link (15)
-
fdiotalevi -
jsugrue -
mlevison -
zis -
h3rald -
ckeene -
Edward_Culberson -
kristine_barta -
mswatcher -
judithsanderlin -
brianboles -
pt93903 -
Claire_Boyle -
sergo -
davneter




