Emergent Design: Leveraging Agile Retrospectives to Evolve Your Architecture |
 |
| Tuesday, 08 April 2008 12:01 |
 Technological
debt is mistakenly thought of as a technical problem, but when system design
cannot change according to the needs of the business, it becomes a business
problem. Big Design Up-Front leads to
technological debt. Architecture must be
allowed to emerge according to the needs of the product and the business. We know iterative, emergent development
works; iterative, emergent design is no different. Agile teams should use Retrospectives as a
tool to determine current needs and enable emergent design.
Technological
debt is mistakenly thought of as a technical problem, but when system design
cannot change according to the needs of the business, it becomes a business
problem. Big Design Up-Front leads to
technological debt. Architecture must be
allowed to emerge according to the needs of the product and the business. We know iterative, emergent development
works; iterative, emergent design is no different. Agile teams should use Retrospectives as a
tool to determine current needs and enable emergent design.
Read more >>
Set as favorite
Bookmark
Email this
Hits: 1183 Trackback(0)Comments (0)
|
TrackBack URI for this entry
Subscribe to this comment's feed