The systemic Scrum Master
summary
Claims that Scrum fails after about six months unless teams are rebuilt around real human factors, not tools; suggests using systems thinking techniques like causal loop diagrams and current reality trees to map causes, and lists seven elements for passionate teams (passion, adaptability, strong vision, strengths focus, independence, oneness, nimbleness). Cites a company study finding top teams use strengths, trust and shared values, and gives SpaceX rocket reuse and Amiga’s late product cycle as concrete success/failure examples.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:17What Does a Good Scrum Master Do When a Scrum Is Already Performing
- 1:32System Thinking
- 3:05The Current Reality Tree
- 4:50Human Interactions over Processes
- 10:26What Can We Do To Get Passionate Teams
- 14:05Microsoft
- 23:33Nimble Team
related talks
02mInterview with
39mWhy Scrum Is So Often 'Failed' and Criticised
11mGuiding self-organising teams
53mA Theory of Scrum Team Effectiveness — The Science Behind the 'Zombie Scrum Survival Guide'
41mYour Scrum Master Is Deceiving You... and You Know It!
46mPeople, Principles and Pragmatism
38mCognitive biases and failure of Agile
48mBetter leaders. Better organizations