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)

  1. Software Architecture and Agile
  2. Architectural Integrity
  3. Architecture in Product Definition
  4. Designing Systems
  5. Emergent Architecture Elements
  6. Software Debt
  7. Technical Debt
  8. Quality Debt
  9. Executable Specification
  10. Executable Design
  11. Configuration Management Debt
  12. Design Debt
  13. Platform Experience Debt
  14. Evaluating Technology Products
  15. Evolutionary Technology Evaluations
  16. Disruptive Technology Evaluations
  17. Managing Third Party Integrations

Author

Chris Sterling picture

Chris Sterling

Blog: http://chrissterling.gettingagile.com/

About: http://chrissterling.gettingagile.com/about/