About the Book
One of the twelve principles behind the Agile Manifesto is “The best architectures, requirements, and designs emerge from self-organizing teams”. It is clear the way architecture is employed in an agile software development organization is different than traditional approaches through this one statement alone. The methods by which architecture is described, socialized, maintained, accepted, and emerging will often seem chaotic from an outsiders viewpoint not familiar with agile software development techniques. As more large enterprises begin their adoption of agile software development processes such as Scrum and Extreme Programming (XP) it is imperative that enterprise level concerns are addressed. Architecture in an Agile Organization will give these organizations tools they can use to effectively address the enterprise.
Table of Contents (may change)
- Software Architecture and Agile
- Architectural Integrity
- Architecture in Product Definition
- Designing Systems
- Emergent Architecture Elements
- Software Debt
- Technical Debt
- Quality Debt
- Executable Specification
- Executable Design
- Configuration Management Debt
- Design Debt
- Platform Experience Debt
- Evaluating Technology Products
- Evolutionary Technology Evaluations
- Disruptive Technology Evaluations
- Managing Third Party Integrations
Author

Chris Sterling
