Joe Kuemerle introduces the developer to the business side of development starting from the premise that it is not enough to be technologically savvy to be successful in a software organization.
John Allspaw presents technical, cultural, and process related lessons learned at Flickr and Etsy.com from the collaboration between the operations and development teams.
Amr Elssamadisy focuses on the individual and his responsibility 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 distributed software development is a strategic capability for a company, presenting a framework and Agile practices for building such an environment.
Andres Kutt shares lessons learned at Skype: rules of thumb don’t always apply, functionality is important, simple solutions, buzzwords are dangerous, and communication is important.
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.
Alisson Vale presents how Kanban is used to express the understanding of a system by making the work, the workflow, communication, time, information, engineering traceability, and movements visible.
Paul Downey covers the risks of premature standardisation, partial implementations and open extensions, cloud computing lock-in, and formal activities vs lightweight open processes like open source.
Dan North discusses an example of rearchitecting an application without rewriting it from scratch, and explains general strategies for a holistic rearchitecture.
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.
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
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.