Dave Farley looks at a history littered with inefficient processes resulting in poor quality and failed projects, wondering how we got here, what can be done and what does good really look like?
Dave Farley discusses the problems raised by inefficient processes creating poor quality output, too late to capitalise on the expected business value, and proposes solutions to them.
Ian Barber discusses the importance of behavior, domains and clarity of the names used when writing software or building systems.
Donald Belcham presents design patterns and development concepts that protects one’s code from external systems that may change in uncontrollable ways.
Tom Gilb keynotes on 10 key Agile principles: Control projects by quantified critical-few results, Give developers freedom, Estimate the impacts of your designs, Involve the stakeholders, etc.
Baruch Sadogursky and Fred Simon discuss the Groovy version of the epic Java Puzzlers.
Adam Tornhill teaches how to predict bugs, detect architectural decay and find the code that is most expensive to maintain, how to evaluate knowledge drain in a codebase, and much more.
Chad Fowler attempts to convince people that keeping things "tiny" –small iterations, small methods, small teams - is the best thing one can do for himself and his team.
Ellie Kenwood discusses some of the challenges of integrating user experience into an Agile delivery model, including a case study.
Mike Atherton keynotes on aligning work with values to get most benefits from it, to be proud of the results and to make a difference.
Martin Fowler keynotes on the need for refactoring and different ways to approach it. You can view here part 2 of this presentation: http://www.infoq.com/presentations/healthy-social-environment.
Chad Fowler keynotes on his career, the passion, the mistakes and good choices he made, and how that can help others learn the craft of software engineering.