software architecture and agile development
summary
Argues that agile is pushing architecture beyond team boundaries by using devops automation and infrastructure-as-code to make business and ops more experimentable, and that architects must maintain a living plan by staying engaged with teams, listening to contextual feedback, and trusting teams to decide. Warns against ivory-tower disengagement. Mentions local innovation hubs like 1871 and advocacy work such as Shift Women as examples of community-level change.
AI-written summary · about
chapters (4)
- 0:00Relationship between agile development and software architecture
- 2:22Does architecture apply to agile
- 4:02What software architects can do to thrive
- 5:35What mistakes should software architects avoid
related talks
49mAgile and Architecture: a meeting of the undead
51mWhy We Need Architects (and Architecture) on Agile Projects
47mAgile and Architecture: a meeting of the undead
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
41mAgile and Architecture: a meeting of the undead
45mDemocratising Software Architecture
41mSoftware Architecture in a DevOps World