Ángel Medinilla outlines the basic steps he recommends to make for product success: product vision, business model, test assumptions, iterative and incremental development, use metrics, and keep it simple.
Hans Dockter discusses build systems from a declarative vs. imperative perspective, the importance of a rich execution model and problems with POM, providing examples from Gradle, Maven and Ant.
Sandy Mamoli explains how to avoid multi-tasking by using personal Kanban and other Agile practices applied at the individual level.
Rachel Laycock advises on designing systems for rapid deployment, avoiding delivering pitfalls by using micro services and evolutionary architecture.
Dianne Marsh presents the open source tools used by Netflix to keep the continuous delivery wheels spinning.
Floyd Marinescu shares how the virtual teams behind InfoQ.com and QCon are run; Processes, tools, & mindset needed to succeed in a completely virtual work environment that delivers happiness and alignment. Each practice is explained in the context of how it fosters purpose, autonomy, mastery, and a sense of progress.
Bill Yetman and Jeremy Pollack discuss using several Agile techniques -start simple, get going, iterate- and the “measure everything” principle to create the architecture behind the Family History website.
Peter Niederwieser discusses building a continuous delivery pipeline with Gradle and Jenkins.
Ted Tencza shares lessons learned innovating at Atlassian and Bigcommerce, including programs that worked (FedEx/ShipIt/Hackathons, 20% time) and programs that failed (dedicated Innovation Team).
Ken Collier discusses Agile Analytics, a combination of sophisticated analytics techniques, lean learning principles, agile delivery methods, and "big data" technologies.
Gareth Rushgrove provides reasons for avoiding a big bang release and what to do to make it work in case that’s the only option.
Do Agile Methods Contain the Seeds of Their Own Destruction? (Safety and Our Ability to Learn from Failure)
Amr Elssamadisy explores the link between safety and success of agile methods, explaining what can be done to change the culture of an organization to create a base where agile methods can flourish.