Alex Baldwin explains the exercises used in the 5 phases of a Design Sprint: Build, Diverge, Converge, Prototype, and Test.
Bill Liao keynotes on the scale-free self-organizing systems implemented by CoderDojo and how they can be used by other consumer software organizations that wants to achieve significant reach.
Giovanni Asproni suggests that teams should not blindly embrace a methodology but rather create their own suiting their specific needs by using an approach based on patterns and pattern languages.
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.
Angel Medinilla advises on hiring and evolving a great Scrum master along with resources on psychology, coaching, motivational science, communication skills, corporate culture or change management.
Peter Stevens teaches the basics of Scrum starting from its principles, explaining why it works and how team can use it to be effective.
Chris Farrell, Shawn Button help workshop participants to see the problems of self-organization and learn using BEGIN -Boundaries, Empowerment, Goals, Ingredients, Nurture- to empower their team.
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.
Steffan Surdek introduces key Tribal Leadership models for Scrum Masters, Project Managers, Development managers or anyone else interested in a better understanding the teams they are working with.
Gerry Kirk introduces the 7 levels of delegation by playing Delegation Poker, a game to make clear who’s responsible for what and on what level, useful to make decision making process explicit.
Neil Killick proposes ways to reduce risk and uncertainty, calculate a product’s price, determine delivery dates and roadmap, do Scrum and XP without using estimates.
Tim Berglund shares the vision of an organization without product managers with its implications and boundaries, provoking the listener to take a bold step into that direction.