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.
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.
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?"
This session takes a comprehensive look the "Web as Platform," implications for software architecture and innovations and ideas that are just now being fully appreciated. Changing concepts of system design and the discipline and practice of software architecture, that architects and technical leads must know today are addressed in this far ranging discussion.
Scott Shaw, Director of Services at ThoughtWorks, and Martin Fowler, Chief Scientist at ThoughtWorks, talk about the need for a new relationship between the business department and the IT department. Studies have constantly shown that the main culprit for unsuccessful projects lies in miscommunication between the business people and the IT ones.
In this presentation filmed during QCon London 2007, Martin Fowler and Dan North talk about the communication gap existing between the developers and the customers or users. Closing this gap is extremely important in order to create successful software.