For Application Development & Program Management Professionals

Primary Analyst Photo	Document Information	Rate this Document
	July 10, 2009 Balance Architecture And Agility To Sustain Value Delivery The Role And Value Of Architecture In Agile Software Development by Dave West with Mike Gilpin, Gene Leganza, David D'Silva	Average: 10  (3 ratings)

This is an excerpt

Executive Summary

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.

Keywords

• Agile
• Agile delivery
• architecture
• high cost

TABLE OF CONTENTS

• Don't Believe The Myths: Agile And Architecture
• Agile Developers Need Architecture, Too
• Balancing Architecture And Agility Is Crucial To Long-

RECOMMENDATIONS

• Make Architecture Part Of Agile Development

WHAT IT MEANS

• Agile Architects Support Lean Enterprises
• Related Research Documents

This is an excerpt