Advertisement
Every system has an architecture, intentional or accidental, created by an architect, emerging from team decisions, or generated through prompts and agent loops. Too often architecture is reduced to platform technologies. Technology matters, but it is only one architectural concern. Architecture is also too often separated from development, though they are intertwined: what you build influences how you build it, and vice versa.Kevlin Henney’s "Architecture with Agility" explores the relationship between agile development and economically sustainable architecture. It covers agile and lean thinking, organisational structure, AI in codebases and workflows, architectural qualities, legacy systems and future change. The focus is architecture and real agility, not one technology, style, or a narrow certification-driven view of agile based on empty rituals.
Practices and techniques will be applied in group exercises, plus discussion and Q&A. Ideal for developers, architects and technical leaders.
Course contents:
**What is software architecture?
What do we mean by software architecture?
Why architecture is not about blueprints
What makes software architecture good?
The architect’s role and relationship to teams
Architecture as economically significant design
How architecture increases or decreases cost
**Properties of an architecture
Cohesion, coupling and separation of concerns
Simplicity and kinds of complexity
Habitability and developer experience (DX)
Value demand versus failure demand
Requirements and architecture
Cross-functional vs “non-functional” requirements
ISO 25010 characteristics of a software system
**The process of change and development
What you build influences how you build, and vice versa
Planned versus empirical development
The inevitability of iterative development
Incremental development with continuous delivery
Optimising for options and knowledge
Using LLMs to generate and explore options
Architecture as hypothesis formulation and evaluation
PDSA (Plan–Do–Study–Adjust) and empirical architecture
**Software structure and dependencies
Structural elements, relationships and rationale
Services and components: microservices, modules, monoliths and more
Modularity and local context for humans and LLMs
Ports and adaptors / hexagonal architecture
Interfaces as seams and contracts
Assumptions and contexts as dependencies
Reuse: use cases and pitfalls
Published APIs and (un)changeability
OCP and SRP as design smells
Reducing change impact through dependencies and deferred commitment
**Structuring for change and uncertainty
Architecture as the decisions you wish you could get right
The risk of overcommitting to early decisions
Structuring for change instead of predicting the future
Separating layers/components by uncertainty and volatility
Shearing layers and partitioning by rate of change
Inverting modular, packaging and layered relationships by stability
**Capturing design rationale with ADRs
Decision awareness in developer-created and LLM-generated code
Pitfalls of traditional documentation
Patterns as captured knowledge and decisions
ADRs as a lightweight, DX-friendly approach
Capturing design trade-offs
Avoiding ADR smells and pitfalls
Applying ADRs in a simple package-based example
**Models and viewpoints
Models and abstractions
Common modelling pitfalls
Models as artefacts vs modelling as collaboration
Domain-driven design (DDD) and architectural structure
State-based modelling
Tests as specifications and spec-driven development (SDD)
Sharpening SDD with model-based thinking
Architectural viewpoints: 4+1, RM-ODP and C4
**The effect of organisation on architecture
Conway’s law as an organisational force on architecture
Common misunderstandings of Conway’s law
Conway’s law over time, not only in the current organisation
The costs of scaling development headcount
Organisational alignment versus development quality
Feature teams versus component teams
Team topologies
**The causes and effects of technical debt
Definitions and costs of legacy code
Legacy architectural decisions
The technical debt metaphor and its implications
Managed versus unmanaged technical debt
Technical neglect as a driver of unmanaged debt
Positive and negative LLM effects on technical debt
Punctuated versus continuous debt repayment
Prioritising technical work to prevent architectural atrophy
**Agile and lean thinking in architecture
What agile development means beyond brands, in theory and practice
Continuous attention to technical excellence
Development speed versus actual development velocity
Slicing by usable feature rather than architectural artefact
Applying lean thinking to code, architecture and workflows
Roadmaps have more than one road
Walking skeletons, prototypes, spikes and proofs of concept
Architecture as product management, not project management
This workshop is for developers, architects, technical leads and technical managers.
Advertisement
Event venue
Hotel Ramada Iasi City Center, RAMADA by Wyndham-Iasi City Centre, Strada Grigore Ureche, Iași, România, Iasi, Romania
Tickets
Concerts, fests, parties, meetups — all the happenings, one place.
Discover more events by tag
Workshops in IasiEducation in IasiTechnology in IasiArchitecture in IasiArtificial-intelligence in Iasi