Software Architecture Without an End State

Most software architecture efforts have a strong waterfall nature to them. Software architects create an end-state vision with a multi-year plan to achieve it. Of course, the business and technological contexts both change long before that can be achieved. The result is a series of half-finished, very expensive, enterprise architecture initiatives. Instead, we should create architecture that is specifically optimized for change, with principles about where to place certain decisions and how to adapt over time.

Watch this video on Oredev.org