|
For Application Development & Program Management Professionals
(Length: 16 pages)
July 10, 2009 Balance Architecture And Agility To Sustain Value DeliveryThe Role And Value Of Architecture In Agile Software Developmentby Dave West with Mike Gilpin, Gene Leganza, David D'Silva Executive Summary (This is a document excerpt)Enterprise architects often criticize Agile methods because they perceive them as lacking architectural control or governance. This lack of control and governance arguably leads to systems that have higher operational costs and become increasingly difficult to maintain and support in the future. Conversely, Agile teams often perceive architecture-centric approaches as too heavy and plan-driven, insufficiently focused on business results, and delivering systems that align with standards that are obsolete in the context of today's business challenges. There is some truth in both viewpoints; therefore, it is important to blend architecture with Agile delivery in a hybrid approach that balances long-term architecture priorities with the short-term, business-driven requirements of Agile delivery. The most-successful Agile teams achieve this balance by integrating a pragmatic architectural approach into their Agile work practices. The result? These Agile teams can better sustain their ability to quickly deliver value over time and across multiple releases. Buy Risk-FreeDownload and print PDF immediately. Price: US $499 Our Money-Back Guarantee: If you are not completely satisfied, return it for a full refund within three weeks of your online purchase. Already a Forrester Client?
|
Archived Teleconference:
How Lean Software Will Help App Dev Better Serve The Business
Original air date: Thursday, November 12, 2009
|
||||||||||||||||
|
| |||||||||||||||||