Why You Should Focus on Collaboration Rather Than Roles
summary
Claim: switching from fixed job descriptions to accountabilities not roles improves new-team performance. Evidence: run workshops on expectations to list who owns what, add a psychological-safety session, and rebalance people into five cross‑functional teams so domain and tech knowledge spreads. Tools and practices: introduce CI/CD and track cycle time. Outcome: dependencies drop, teams self‑manage, role descriptions become irrelevant and delivery momentum increases.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:06Role confusion in new teams
- 3:13From dungeon master to agile coach
- 8:08Leadership styles in agile
- 16:58Choosing leadership approach
- 19:03Change curve and adaptation
- 23:42Leadership in crisis
- 26:16Pitfalls of forced styles
- 29:48Leadership in Scrum
- 30:31Workshops for role expectations
- 35:16Reorganizing teams for balance
- 37:23Beyond role descriptions
- 39:55Fixed roles impact
- 41:00Conclusion
- 41:22Q&A: Scrum master needed?
- 42:03Q&A: Measuring success
related talks
01h 10mAgile Cross Team Collaboration How Tos
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
39mUsing Agile Techniques to Build a More Inclusive Team
01h 18mLeading teams to collaborate-when they really don't want to.
49mHow to Make People Work Together?
32mBuild Teams as an Engineer
49mBuilding a High-Performance Team is Everyone's Job
39mThe Key To High-Performing Teams Based On Trust