Why We Need Architects and Architecture on Agile Projects

Explore the importance of architects and architecture in agile projects through this insightful conference talk. Learn why good architecture requires ongoing attention and stewardship, especially in complex software development. Discover techniques and architectural activities useful for agile projects, and understand how an agile architect's role differs from traditional software architects. Delve into topics such as agile design values, myths, stewardship, project criticality, and sustainable development. Examine the differences between small and large project architecture practices, including design spikes, technical debt management, and architecture backlog. Gain valuable insights on managing architectural tasks, creating product landing zones, and understanding the agile architecture landscape. Understand the key differences between agile and traditional architecture approaches, and explore the values important to agile architects.

Intro
Why We Need Architects (and Architecture) on Agile Projects
Three Questions...
Astronaut Architect?
Seagull Architect?
Incompetent Fools?
Agile Design Values
Some Agile Myths
Steward Architect
Stewardship
How Much Architecting Do You Need? Project Criticality
Qualities of Any Good Architecture
Small v. Large Projects
Small Project Architecture Practices
Design "Spikes"
Experiment on Branches
Manage Technical Debt
Keep Architecture in Mind
Sustainable Development
Strike a Balance
Types of Project Risks
Architecture Debt
Product Landing Zones
Good Acceptance Criteria
What's Different?
Landing Zones on Agile Projects
Architecture Spikes
XP Design Spike
What You Do In an Architecture Spike
Criteria for an Architecture Spike: Actionable Results
3 Ways To Manage Architectural Tasks
What Can Go On An Architecture Backlog?
The Agile Architecture Landscape
Differences Between Agile and Traditional Architecture
Values Important to Agile Architects