Knee-Deep In Tech Live @ SQL Bits
summary
Argument: frameworks become a ritual unless teams set a clear long‑term goal, run 2–4 week sprints with daily standups, act on retrospectives and hold blameless postmortems. Tools cited include following patterns from the DevOps Handbook, using code-driven ops and cloud cost tracking, and appointing a listening Scrum Master who removes blockers. Small-team experiments prove value and scale slowly; heavy top‑down rollouts usually fail without psychological safety and executive sponsorship.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 3:02Hosts and context
- 4:29Agile scrum defined
- 8:44Scrum implementation challenges
- 11:37Frameworks: hindrance or help
- 14:54Audience perspectives
- 18:54Retrospectives and improvement
- 21:21Scrum masters and coaches
- 25:01People processes and safety
- 28:36Proving agile value
- 32:39Final thoughts and Q&A
related talks
57mFocus. Deliver. Learn. Repeat
39mStop Focusing on Tech Debt
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
41mA Selectio of Lightning Talks
01h 13mScrum for Executives, Leaders, and Your Boss
43mSweat the Small Stuff
34mBuilding a Culture For Developer Productivity
44mMoving Beyond Agile? Modern Methodologies for Technology Development
