Effective Agile Processes: It’s All About People
summary
Argues that effectiveness comes from values not rituals and lists concrete rules: require PMs create user stories and developers create tasks, plan sprints in two meetings (assign stories, break into tasks, reconcile) which typically adjusts scope by about 15–20%, size sprints to 80–90% capacity, classify failures as process-versus-unavoidable, and favor asking for help and small experiments over automating every glitch. These practices aim to reduce burnout and speed delivery of “good” customer-facing software.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:52we deliver good software to customers
- 8:53we are collaborative
- 18:54we put people first
- 20:54we embrace creativity
- 24:39user stories/tasks checks and balances
- 26:59hold two sprint planning sessions
- 28:46process broken" vs. "shit happens
- 30:50resist trying to prevent all the bad
related talks
42mHow Doing the Little Things Well Makes the Big Things Possible
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
34mNative Agile Psychology of Teams and Individuals
40mRegain Benefits from Agile Software Development
46mAgile: principles over practices
34mFor effectiveness, Agile was never the answer
49mAgile is a Dirty Word
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined