Keynote: Decision-making for Software Development Teams
summary
Outlines a reproducible decision workflow: map stakeholders with an interest–power map, pick 4–6 prioritized non‑functional requirements via DOT voting, and capture them in an architecture compass chart so every choice ties to a defined fitness function. Uses a weighted ranking spreadsheet to compare options, recommends small POCs, and highlights lifecycle fit (explore vs expand vs extract) with a startling datapoint: roughly 90% failure in explore phase that argues against early heavy investment in quality.
AI-written summary · about
chapters (35)
- 0:00Intro
- 1:27Why
- 1:42Scenario
- 2:15Examples
- 4:00Do you have a practice
- 4:43Critical technical decision
- 5:12Shared process
- 6:07Adapt to organizational needs
- 6:41Visual content
- 7:50Meet your neighbors
- 8:25Interest power map
- 9:02Focus on impact
- 9:21Change a framework
- 9:52Data
- 11:05Elevator of Pitch
- 14:01Tradeoff Slider
- 15:49Freaks Model
- 17:28Explore Phase
- 19:00Skills
- 21:20UX Research
- 24:18Nonfunctional Requirement
- 24:41Function Requirement
- 25:02Nonfunctional Requirements
- 28:35Exercise
- 30:40Define an Ubiquitous Language
- 30:53Effectiveness
- 31:33Compass
- 34:28Visual comparison
- 36:06Weighted ranking
- 39:35Decisionmaking process
- 39:49Delegation board
- 41:03Map your decision
- 41:50Agree level
- 42:13Book
- 42:46Francesco
related talks
42mDecision-making for developers
32mThe Art of Technical Decision Making
39mThe Art of Technical Decision Making
20mFast, informed, impactful: How to master decision-making
19mHow to make technical decisions?
47mBottega IL: Team decisions making methods
53mKeynote: Value Driven Development - Maximum Impact, Maximum Speed
26mThe choice is yours – or is it?