Every system has an architecture, whether accidental or intentional, and regardless of whether it was put in place by a nominated architect or whether it emerged from the decisions and discussions of a team. All too often the focus of what is often described as architecture is centred around a specific set of platform technologies, which forms only one part of the set of concerns an architecture should address. And all too often architecture is seen as a separate concern from the development process, whereas the two are intertwined — what you build is influenced by how you build it, and vice versa.
Kevlin Henney’s Architecture with Agility training looks at the relationship between agile processes and sustainable architecture, taking in agile and lean thinking, organisational structure, good architectural qualities and addressing the legacy of the past with future change. A number of practices and techniques will be presented and applied in group exercises There will also be time for discussion and Q&A.

Structure:

• What is meant by software architecture?
• The relationship between architecture and development process
• What does agile development mean in theory and in practice?
• Applying lean thinking to code, architecture and workflow
• The difference between development speed and actual development velocity
• Prioritising technical work on products
•  Reducing impact of change through dependency management and deferred
  commitment
• PDSA (Plan–Do–Study–Act) and employing an empirical approach to guide
  architecture
• Capturing architectural rationale and evolution through architecture decision records (ADRs)
• Responding to technical debt and legacy code
• How does team type and organisational structure influence architecture
• Structuring a system with respect to change and uncertainty

Materials:

Course slides (PDF) are made available to course attendees during and after
the course · Slides are updated as the course progresses, including new
material created in response to questions