Amr Elssamadisy focuses on the individual and his responsibility to do his best to make things work in the team regarding the learning process, communication, dealing with upsets, ownership, and responsibility.
Matthew Simons and Steven Boswell consider that although distributed software development is hard, it is a strategic capability that a company should consider, presenting a framework and Agile practices that help building a healthy distributed environment.
Andres Kutt discusses his experience as architect at Skype for five years, sharing some of the lessons learned: rules of thumb do not always apply, functionality is important, use simple solutions, buzzwords are dangerous, the architecture needs to fit into the organization, and communication is important.
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.
Alisson Vale presents how Kanban is used by Phidelis in order to make the main elements of a process - the work, the workflow, the communication, time, information, engineering traceability, movements – visible in order to express the understanding of a system.
Tamara Sulaiman presents experiences in implementing Agile in teams across different time zones in large companies. She shares the pleasure and the pain, ideas that worked as well as ideas that didn’t. She also shares the critical success factors in making program level implementations successful and sustaining.
Paul Downey discusses the risks of premature standardisation, unnatural constraints, partial implementations and open extensions, how to avoid cloud computing lock-in, formal activities versus lightweight open processes as exemplified by open source, Microformats, OpenID, OAuth and other Web conventions being ratified through open, lightweight, continuous agreement.
Dan North discusses an example of rearchitecting an application without rewriting it from scratch, and explains general strategies for a holistic rearchitecture such as changing the team culture, removing obsolete technologies, allowing mistakes to be made (and learned from), transitional architectures, introducing bounded contexts, refactoring and emergent simplicity, and rotating through roles.
Agile and distributed development seem to be at odds with each other. One is about close communication and short feedback loops, the other is about being effective with people in a different location. This talk discusses a number of patterns common for setting up Agile Distributed Development and will show the results that can be achieved once you get into a good Fully Distributed Scrum.
Jake Sorofman talks on how to glue together the application development world and the business operations one in an automated, virtualized and cloud computing environment where everything moves faster than ever.
Bob Frankston offers a vision of the Internet that focuses on communication and connection uninhibited by artificial barriers like carrier exclusivity, arbitrary differences in protocols, and vendor constraints. He uses stories as his organizing and presentational metaphor to share a vision of what could be, if we had free reign to follow our imagination.
Kent Beck takes a look at trends and how they affect us. Communication, simplification, unintended consequences, disappearing models, and new approaches of design and tests are examined. Kent takes diverse set of issues that are changing in our world and asks "why are we doing this?"