Team? What Team?
summary
Examines whether T-shaped people exist in practice and tests Scrum’s claim that teams should cover ~80% of needed skills. Uses real operations, development and application-management teams forming an “application layer,” short-lived product teams (e.g., a two-month mail-server project) and platform guilds; describes automation with configuration tools and treating infrastructure as a product. Finds a persistent “wall of confusion,” notes cross-functional teams improve idea and knowledge sharing, but concludes true full generalists are rare and specialist teams remain sensible at scale.
AI-written summary · about
chapters (17)
- 0:00Team separation history
- 5:00Wall of Confusion origins
- 7:24Dev vs ops effects
- 10:35Operations team roles
- 13:05Application management role
- 16:01Cross-functional teams solution
- 17:25Building cross-functional teams
- 20:42Specialists vs generalists
- 23:00Need for specialist teams
- 26:10Infrastructure team challenges
- 29:07Large infrastructure teams
- 33:06Infrastructure team lifecycle
- 36:14Floating teams for tasks
- 39:08Stable teams and leadership
- 41:17Cultural aspects of teamwork
- 43:07Team ownership
- 45:42Small tasks and on-call
related talks
45mSoftware delivery with skills-based, self organising teams
01h 00mDynamic Teams - Fluidity for the win
39mTuckman was Wrong — Dynamic Teaming
21mAutonomous Teams
48mHow microteams change the way we collaborate. Again.
47mFrameworks for Shaping High-Performing Teams
30mProduct Teams Need A Family Too
46mIt’s XP Stupid!