Agile Architecture

Al Shalloway is presenting Agile Architecture at the monthly meeting of the Northwest C++ Users’ Group. Visit their site for details of timing and location.


Never has architecture been more important than now. Scrum acknowledges the need for quality code but gives no advice on how to achieve Agile architecture. The Kanban Method ignores it completely. But as Agile moves into larger organizations we cannot continue to ignore it.

This talk discusses why Agile architecture is so important. It then discusses what Agile architecture needs to accomplish and provides some methods in how to achieve this. This seminar will touch on the why, what and how as summarized here:

Why: Architecture, whether Agile or otherwise, needs to provide the following:

  • A vision
  • Enable extensions to the system
  • Enable new ways of implementing existing concepts
  • Foster testability throughout the system
  • De-couple systems from the application
  • Facilitate reuse of common functions across teams

How: To build Agile architectures, one must be able to:

  • Do Emergent design
  • Do Testing at the behavior and functional level
  • Understand the different perspectives of conceptual Vs specification; creation from using; and system architecture from application architecture

What: Agile architectures will then enable us to:

  • Inject new concepts with little to no rework
  • Add new implementations of existing concepts with only minimally affecting the existing system
  • Change the system with little risk of introducing errors and full confidence that if you do you will detect them

All the Details

May. 22, 2014 2:00am PDT
Cost: Free
Questions or problems with registration or directions? Contact Mike Shalloway for assistance.

Share This Event