Description changed:
There’s often a tension between agile software teams and the architecture function, a tension that is usually rooted in simple misunderstanding, rather than any intrinsic contradictions between them. Like so many apparent conflicts, their resolution requires us to consider the opposing views from the perspective of a shared context – in this case, that of the software development process.
This workshop will explore the theory that underpins agile architecture and throw it into sharp relief using a series of practical exercises and animated discussions. We’ll cover many thorny topics, including:
What diagrams to draw (lines and boxes)?
When is design actually architecture (or vice versa)?
How much architecture is enough (and when it should be done)?
Should an architect write code (or developers do architecture)?
Target Audience
Developers, architects, designers, team leads, testers – in fact anyone with a technical role in software delivery