Stuart Williams shares from experience how his company implemented Kanban, what worked for them in handling maintenance, support and a number of small projects.
Lynne Cazaly shares insight on how to start a high impact meeting or workshop, the process, the agenda, and the tools that can help facilitate such an event.
Michael Seifert shares lessons learned working on various design projects and the process of changing the tools while doing it.
Andrea Burbank discusses the risks, benefits, and lessons from running a single huge experiment with hundreds of moving parts, and with long-term engagement as the metric of success.
Randy Shoup tells war stories from Google and eBay focusing on how to scale code, infrastructure, performance, and operations, along with hard-won lessons learned in scaling them.
Geoff Bones, Luke Drury share the lessons learned setting up code kata programs in several companies, what has worked and hasn’t.
Michael Bryzek shares lessons learned from startup to a leading ecommerce companies, starting with behavioral psychology and reflecting on the decisions made and tradeoffs considered as they scaled.
Jeff French shares from his experience how to convince organizations to implement Agile methodologies.
Martin Thompson discusses the major steps in the evolution of Java and how it contrasts to alternative technologies, and the challenges of pushing the limits of performance.
Darren Hobbs shares lessons learned building polyglot systems, the technology choices made. mitigating risk and delivering value.
Francois Mazoudier shares some of the stories he came across while building businesses from scratch to IPO, academic models he developed and several real life examples.
Deepak Nadig, Praveen Alavilli present how PayPal redesigned its APIs based on lessons learnt developing their services in over 14 years, and the principles, patterns and anti-patterns used.