Martin Harbolt discusses Agile leadership practices promoting self organized teams and finding the proper rhythm for completing Agile projects with success.
Chris Nodder shares tips for getting a product vision, a high-level design, and a plan for the first sprints of a new product in one week.
Simon Brown discusses the role of the software architect, challenging some of the current assumptions and trying to redefine it in the context of Agile development.
Rafael Maranzato tells the story of a team who initially failed to adopt Scrum, but they tried again, successfully adopting it and moving to Scrum of Scrums within one year.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
Joel Semeniuk shares some of the lessons he learned managing development teams, how he got into Kanban and why its principles are helpful.
Janne Jul Jensen presents the development process of a mobile banking application from prototyping to the actual product including SCRUM sessions, sprint evaluations, UI designing, and user feedback.
Craig Larman presents practices and tips related to adoption, structure, requirements, contracts, architecture and design, offshore, multisite development, and coordination with large Scrum teams.
Leonardo Mattiazzi considers that Scrum and XP are not enough, and complementary Lean principles and practices are necessary to create an Agile culture across the entire enterprise in order to succeed
Karthik Dinakar presents a case study showing that trying to reach short-term goals by ignoring some practices can lead to long-term failures, how they recovered and recommends some best practices.
Kelley Horton discusses the reasons why her organization transitioned to Lean-Agile, the approach used and the visual tools helping them minimize WIP, concluding that visibility leads to success.
Tim Wingfield tells his story moving from Scrum to Kanban, presenting several versions of Kanban boards used, and some practices: retrospectives, pair programming, code review, and stand-up meetings.