Jim Benson develops the idea that software is not engineered, and it is better done collaboratively by a communicative team using Agile and Kanban methodology and tools.
Sue McKinney discusses the roles of managers and developers within an organization where everyone owns delivery and is accountable.
Jeff Patton presents a work style where everyone takes ownership of products, being involved in identifying and solving problems, and shares practices for collaboratively designing solutions.
Phil Hagelberg advises on starting and maintaining user groups doing swarm coding, a form of interactive development in an informal setting.
David Hussman, David Laribee, Jeff Patton, Richard Sheridan and Susan Standiford discuss forming and building successful teams: hiring new people, pairing, combining people of different levels, etc.
Stephen Burton discusses how the people, processes, collaboration and tools employed in Formula 1 can be used to manage performance and reliability and ultimately achieve success by DevOps.
Craig Larman presents practices and tips related to adoption, structure, requirements, contracts, architecture and design, offshore, multisite development, and coordination with large Scrum teams.
Stephen Nelson-Smith’s presentation is a case study and lessons learned by implementing Agile and Lean practices by both the development and operations team in an attempt to overhaul the entire development, testing, staging, and production process of a UK governmental website.
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.
Julian Simpson recommends practices to bring together development and operations, like: collaboration, don’t use email for internal communication, respect everyone, have lunch with the other team, discuss problems, joined retrospectives and stand-up meetings, co-locate sysadmins and developers, teach sysadmin to use VC, use CI and continues deployment, separate binaries and configuration files.
Roy Osherove discusses principles and practices that make teams more effective, successful and happy. Team topics covered: automating everything possible, buying/using/discarding tools, getting quick feedback, communicating without using meetings, building by feature not layer, code & tests reviewing. Lead topics: bottleneck ninja, integrity, removing obstacles.