Benjamin Mitchell advices on carrying team conversations about information presented on Kanban boards helping members to change their thinking and acts in order to achieve evolutionary change.
Ivan Sutherland elaborates on the idea of a “prison” defined by sequential computers that work with sequential character strings making communication expensive and obstructing concurrency.
Jenny Cham teaches how to plan workshops having a technical or scientific audience in order to impress the audience, get feedback and get the best results.
Lyzbelle Strahan shares insurance claims investigation techniques useful for designing the interaction with users during product research.
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 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.
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.