Mary Poppendieck examines research and case studies to help understand what a lean mindset is and how it can help a company compete in today's fast moving marketplace.
Joe Campbell and Wally Eggert discuss the tools and approaches used to introduce Continuous Delivery at CIM without having any major disruptions to their existing delivery flow.
Jeremy Edberg shares some of the lessons learned scaling Reddit, advising on pitfalls to avoid.
Nathan Marz shares lessons learned building Storm, an open-source, distributed, real-time computation system.
Jon Tirsen and Douwe Osinga tell Triposo’s story from a small hobby project to the large architecture of today. Triposo is a mobile phone travel guide.
Trevor Lalish-Menagh shares his experience introducing Kanban, what has worked and what hasn’t.
Andrew Godwin tells Lanyrd’s story, covering the technology stack, tricks used, and what they would do differently if they could start afresh.
David Craelius tells the story of Klarna building an online payment system in Erlang and their approach to solving the nightmare of technical debt accumulated during a period of fast expansion.
Jay Kreps discusses the evolution of LinkedIn's architecture and lessons learned scaling from a monolithic application to a distributed set of services, from one database to distributed data stores.
Marc Frons discusses the New York Times’ digital subscription model. Rajiv Pant shares their experiences transitioning to continuous delivery, and using NodeJS, Scala, cloud and big data.
Climbing Out of a Crisis Loop: How a Critical BBC Back-end Team Reigned in a Workflow Crisis-to-crisis Cycle
Rafiq Gemmail and Katherine Kirk tell the story of a BBC team which worked out of a severe crisis loop by bending the Agile 'rules' and combining multiple Agile and JFDI 'methods'.
Benjamin Mitchell shares experiences gained working with teams over the last five years, highlighting mistakes that were made following simplistic guidance and outlining key pragmatic examples that worked.