I skimmed the video by listening to 20 or so seconds every few minutes of the video, so forgive me if my take away missed out on something. This is what I got f

I skimmed the video by listening to 20 or so seconds every few minutes of the video, so forgive me if my take away missed out on something. This is what I got from it: Change workflow from string (Person A takes Issue A, Person B takes Issue B, Person C takes Issue C) to a "swarm" (Issue A taken by People [A-C], Issue B taken by People [D-F]) Multiple eyes pass the code = more bugs caught. Social pressure to be working on the project (group of 4-5 people). If things fall too far behind, revert to "string" method of each person working on an individual issue. Results in less time wasting (FB/Twitter) due to social pressure. Some study said a pair of 2 is the most productive, but they feel the social pressure is too high in that scenario, hence group of 4-5 to relieve social pressure while maintaining the benefits of collaborative work. Not worth the time. Not all that interesting. Mostly saying stuff that many "lean startups" have learned. That pair coding increases productivity. They just applied this to their queue instead of only new features or something.