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.
Dana Caulder discusses how to improve team communication and delivery, aligning processes and tooling for iterative improvement, processes to mitigate team member turnover and speed-up onboarding.
Astrid Claessen discusses retrospectives: the Derby and Larsen models, how gamestorming helps, and techniques explained through example by involving the audience.
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.
Arjan van Leeuwen overviews code reviews advantages and disadvantages, how much can be done in a code review, types of critiques, how to handle critiques and conflicts that might arise from them.
Graham Brooks explores internal measurements used in a continuous delivery feedback mechanism in order to improve a system's design.
Sam Aaron promotes the benefits of Live Programming using interactive editors, REPL sessions, real-time visuals and sound, live documentation and on-the-fly-compilation.
Chris Dagenais considers that offering and receiving peer feedback is an essential part of communication within a healthy team. He discusses some of the obstacles and solutions for better feedback.
Adrian Howard addresses misconceptions that may affect the designer-developer relationship, detailing 6 principles helping UX designers better integrate into Agile teams.
Aino Corry argues for retrospectives, emphasizing their importance and providing advice on creating useful reflections on past activities.
Scott Hanselman advices on dealing with information overload: audit and sort info sources, schedule work sprints, turn off distractions, triaging the inbox, having a personal toolbox.
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.