Introduction to Architectural Katas
summary
Shows how short, repeatable workshops teach architectural thinking by forcing decisions from fuzzy requirements — typically three-person teams working in 1–2 hour timeboxes to produce an architecture vision, present it and get peer critique. Uses concrete tools: whiteboard-driven prototyping, use-case sticky notes, the C4 zoomable diagrams and event storming. Claims 20–30 kata prompts exist; recommends planning a few throwaway iterations rather than heavy up-front design. Good if wanting hands-on methods to learn questioning, tradeoffs and rapid architecture validation.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:27Disclaimer
- 2:23Software Architecture
- 4:44Coding
- 6:22Planning
- 7:26Working Together
- 9:03Frederick Brooks
- 12:37Explanation
- 12:55What is a Code Kata
- 15:01How long is a Code Kata
- 16:32Two Scenarios
- 19:22How it works
- 24:25Cutters
- 25:15Example
- 29:07Decision Making
- 32:54Cutoffs
- 37:28Throwing away
- 38:51Flipcharts
- 41:29UML
- 45:34Whiteboard
- 46:56Diagrams
- 47:50Lowkey
- 49:00Event storming
- 50:05Wrap up
related talks
15mImproving Skills and Infrastructure with Architecture Katas
40mThe (too) many faces of architecture
56mEssential Architectural Thinking – Why, What, How, When and How Much?
02h 37m[Workshop] How to Document Your Decisions
34mShortening the Architectural Feedback Loop
51mWhy We Need Architects (and Architecture) on Agile Projects
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
45mThinking about Systems using Bytesize Architecture Sessions