Emmanuel Gaillot and Jonathan Perret perform a pair programming parody on stage, showing how not to do it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
Fred George discusses Programmer Anarchy, a development process where programmers are not just empowered to act but the driving force behind a product, leading to substantial increase in results.
Jason Gorman presents how developers can learn TDD to the point of transforming the knowledge acquired into habits by exercising a number of practices followed by peer evaluation.
Glenn Saqui and Jon Mullen present the process used at Sky.com: recruitment, work area, continuous integration, tools, pairing, weekly and daily process, story cards, and the production environment.
Brian Spears shares his company's experience adopting and evolving extreme programming over 9 years.
This session surveys emerging evidence that we can measure the effect of the technical practices of Agile development, and explores what we might be able to do about it to our benefit.
In this video recorded during QCon London 2008, Pete Goodliffe presents two Linux-based audio products with a complete different outcome, software design making the difference.
Neal Ford, an architect at ThoughtWorks, shows 10 ways to write better code. This is practical advice for developers, but application architects can benefit from it too.
Kent Beck shows the synergies between business and Agile development. The reason Agile is becoming more popular every day is because it responds to the business needs as they evolve.
Jeff Patton explains why one needs to embrace uncertainty in order to succeed with his/her Agile project and how to avoid some of the common mistakes leading to project failure.