Allan Kelly introduces Xanpan, a mixture of Kanban, XP, Lean and economics, focusing on teams not projects, allowing for planned and unplanned work within iterations and levels flow.
Neil Killick proposes ways to reduce risk and uncertainty, calculate a product’s price, determine delivery dates and roadmap, do Scrum and XP without using estimates.
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 over a period of 4-6 months followed by evaluation done by fellow co-workers.
Glenn Saqui and Jon Mullen present the details of the development environment and the process they are using at Sky.com: selecting team members, work area, dealing with continuous integration, tools, how they pair, weekly and daily process, story cards and how they are used, and the production environment.
Brian Spears shares his company's adoption of extreme programming nine years ago and how his teams have evolved the process to suit their context. He shares the underlying keys to their success including management backing, the role and importance of a coach, and the eventual adaptation of XP with more experience. He also shares the non-XP practices and roles that evolved over the years.
It is possible to measure certain properties of code, and on the one hand, correlate them with project factors known to have economic merit and on the other, with programmer-pleasing practices. 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.
In this presentation recorded during QCon SF 2008, 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.