Steve Ross-Talbot discusses the what, why and how of describing things, in particular requirements, along with a set of tools serving that purpose and called Zero Deviation Lifecyle.
Michael Feathers overviews a number of patterns he has seen in various projects which provide a good indication that major changes are to be undertaken in the system’s future.
Kellan Elliott-McCrea discusses the technological and process changes Etsy has been going through the last two years in order to make the website more resilient.
Susan Standiford discusses the social psychology, culture and team dynamics challenges faced while moving RueLaLa to a new platform.
Sam Hamilton discusses the technological, architectural and organizational changes an organization goes through in the process of upgrading its software stack without interrupting daily business.
Jodi Moran discusses achieving sustainable speed through: iterate and automate, use commodity technology, analyze and improve, build services, create a high-speed culture.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Jurgen Appelo discusses introducing change inside organizations by viewing them as adaptive systems and social networks and using the Change Management 3.0 model.
Mike Malone discusses principles of good and bad (software) architecture determining SimpleGeo’s architecture: deal with change, embrace failure, phased adoption, balanced security, and others.
Allen Wirfs-Brock discusses the various computing eras and the change we are currently going through, leaving the PC era and entering a new one characterized by mobility, clouds, HTML and content.
Siraj Sirajuddin talks about the Influencer’s (Change Agent) role in introducing Lean and Kanban in large organizations by understanding the philosophy of the Lean process improvement, the forces related to Lean and Kanban adoption, and their dynamics.
Based on real-life cases from the financial industry, Michael Poulin shows how to use 7 service oriented principles, Composability, Autonomy, Contracts, Abstraction, Loose Coupling, Reusability, and Discoverability, to handle service behavior in the execution context and UI changes, and how to prepare for unexpected changes.