Chris Smith provides practical advice for sprint retrospectives, gathering information and identifying root causes of both problems and successes, and addressing issues from a different perspective.
Michael Sahota discusses top 10 Agile gotchas: when release is ready, sprint meetings take too long, no retrospectives, people aren’t working together, getting new stories, stand-ups are boring, etc.
Astrid Claessen discusses retrospectives: the Derby and Larsen models, how gamestorming helps, and techniques explained through example by involving the audience.
Aino Corry argues for retrospectives, emphasizing their importance and providing advice on creating useful reflections on past activities.
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.
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 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, 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.