Forrester: - Making Leaders Successful Every Day |
Search Forrester.com |
|||||||||||
Global Navigation
Local Navigation |
||||||||||||
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
![]() |
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 |
Average: 10
(4 ratings)
|
This is an 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.
This is an excerpt
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client?
Log in to read this document.
Application Development, Architecture & Technology Strategy, Application Development Processes & Tools, Enterprise Architecture, Enterprise Architecture Domains