Aino Corry’s message is that if we skip retrospectives there will be problems that we don’t understand where they come from nor what to do to solve them.
Jenny Cham teaches how to plan workshops having a technical or scientific audience in order to impress the audience, get feedback and get the best results.
Barry emphasizes the need to continue thinking critically about the processes and practices we embrace, accounting for the context in which they exist, and the importance of reflection and refinement at both the organizational and personal levels.
In this presentation Don Reinertsen examines some key lean methods including queue management, batch size reduction, WIP constraints, and cadence. He also discusses the governing economic tradeoffs and how these methods can be exploited by product developers.
Ainsley Nies explains how to perform a personal retrospective: Clarify the Purpose, Assess Decision-making Influences, Gather Data, Distill the Learning and Transform Leaning into Plans.
Jason Gorman presents how developers can learn TDD to the point of transforming the knowledge acquired into habits by exercising a number of practices over a period of 4-6 months followed by evaluation done by fellow co-workers.
In the nature vs. nurture debate, researchers have declared nurture the winner. People who excel are the ones who work the hardest; it takes ten+ years of deliberate practice to become an expert. Deliberate practice is not about putting in hours, it’s about working to improve performance. It does not mean doing what you are good at; it means challenging yourself under the guidance of a teacher.
In this presentation filmed during Agile 2008, Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away. Tim has a personal perspective on Agile practices and shares from his own experience.
In this presentation filmed during QCon London 2007, Martin Fowler and Dan North talk about the communication gap existing between the developers and the customers or users. Closing this gap is extremely important in order to create successful software.
In this presentation filmed during QCon London 2007, Boris Gloger speaks about retrospectives. Agile development teams learn and improve by inspecting and adapting. High performing teams inspect and adapt not only their code and tests, but also their methods and interactions.