What your mother never told you about agile development
summary
Memo about agile reality: history from XP to Scrum shows practices alone fail without values and technical investment. Concrete claims: custom pair programming tables existed; many orgs keep long‑lived branches instead of merging to trunk; CI is still missing in some shops. Metrics: 45% reach basic fluency, 35% gain team technical skills, 5% hit optimizing, <1% reach cultural strengthening. Priorities: short feedback cycles, true stakeholder feedback, automated test suites and CI/CD, small stable teams (not 26 people or 17 competing products).
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 2:05Historical context of agile
- 4:29First principles of agile
- 7:17Common misconceptions and hate
- 11:00Skill acquisition and expertise
- 14:27The importance of feedback cycles
- 16:59Overcoming organizational barriers
- 20:52Agile fluency and technical debt
- 26:34Technical practices and CI/CD
- 29:10Reflection and conclusion
- 32:45Q&A session
