Cross-functional Teams
summary
Dmytro Kononov explains how he built cross-functional engineering teams from scratch at appflame to address business problems that hiring alone didn’t fix. He covers the initial problems and need for restructuring, team formation process, risks and challenges, timelines, metrics (including velocity), implementation details and outcomes, followed by conclusions and a Q&A.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:38Hily
- 1:58How did it all start? What were the problems?
- 7:54What goals did we set? How did we work toward them?
- 11:52How did we form teams? Risks
- 17:51What were the results? Velocity
- 22:22Conclusions
- 27:27Q&A
related talks
52mCross functional teams are great - but what about the business?
46mArchitecture for Cross-Functional Teams
22mThe Rise and Fall of Feature Teams
51mHow to build cross-functional, hybrid teams that Get Stuff Done
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
46mWhy Cross-Functional Teams Build Better Microservices
26mThe Rise and Fall of Feature Teams
09mScaling Frontend Teams
