How to Iterate Together
summary
Advocates treating team workflows like software iteration by naming four actionable practices: respect each other’s skills and pair using driver/navigator roles, build trust via a concrete clean agreements format that specifies who what when, add support through active listening and swapping work during on‑call, and shorten feedback loops by giving candid feedback early and often. Practical proof includes partnering to level up CSS and backend skills and a concrete commitment to implement automated testing with Cypress by the next release, with renegotiation for hotfixes.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:47Who is Rukia
- 1:16Fun Fact
- 1:37What I learned
- 2:05Where it works
- 3:23Respect each others skills
- 5:37Focus on your own weaknesses
- 7:10Trust
- 8:04Clean Agreements
- 9:30Revisiting Clean Agreements
- 10:08Increased Trust
- 11:37Words of Encouragement
- 11:49Listening
- 12:10Rubber Duck
- 13:28Listen More Than You Speak
- 17:00Provide Feedback Early Often
- 17:51Feedback Tips
- 18:33Code Reviews
- 24:51Summary
- 26:06More about my company
- 26:29Thank you
related talks
56mHow to really work as a team- from sleepy to strong pair programming
58mLet's Work Together!
27mTheory to action: Architecting and implementing your team operating system
32mBuild Teams as an Engineer
49mAll Aboard: Tools and Tactics for Building Team Consensus.
11mLeading without committing: Managing teams outside your tech stack
32mHow to work as a team, sleepy to strong pair programming
57mFocus. Deliver. Learn. Repeat