By Francis Lash
One of the mantras of Agile development teams is to do “just good enough” to get the job done. This is what drives the creation of architecture that meets the bare minimum requirements to function. But the “just good enough” mindset is an easy way to incur technical debt.
This is what the post, Architecture Technical Debt: The Curse of Agile?, addresses. The challenge of Agile teams, since they follow the “good enough” mantra, is to have well-planned technical debt that is manageable in the future so that they can continue being Agile. But here we run into a conflict in the mindset of Agile teams. The “just good enough” attitude makes architecture messy, which inherently means you are avoiding any planning of architecture technical debt, and actually taking the time to have well-planned technical debt goes further than “just good enough” architecture – and this is seen as not Agile.
Read the entire article at http://www.ontechnicaldebt.com/uncategorized/meta-architecture-the-solution-to-architecture-technical-debt/.
Image source: LendingMemo