Karthik Dinakar presents the case of his team which attempted to be as agile as possible in order to fulfill the short-term goals but missed the long-term ones because some of the Agile best practices were ignored. He tells the story of how his team finally managed to come back on course and which are the practices that he considers as necessary for success.
Kelley Horton discusses the reasons why her organization transitioned to Lean-Agile, the approach used and the visual tools helping them minimize WIP and track development, concluding that visibility inside an organization leads to success.
Tim Wingfield tells his story moving from Scrum to Kanban, presenting several versions of Kanban boards used over time, including the benefits and drawbacks. He also mentions additional practices used: retrospectives, pair programming, code review, and stand-up meetings.
Experiences and lessons learned facing DevOps problems in the IT trenches (even if they weren’t calling it DevOps!). The good, the bad, the surprises, and ideas for the future.
Christophe Louvion tells the story of an online advertising company which had to give up using Scrum because it did not create enough business value although the development was delivering working software. They chose to use Kanban instead, applying Lean principles at all levels of the organization, resulting in true self organizing teams, accelerated rate of change, and better financial results.
Self-organization is a tricky thing. Agile coaches are challenged with how to motivate/persuade/trick their teams into self-organizing and doing things, without telling them what to do. This tutorial presents an approach utilizing leading-edge research and techniques from social complexity science and team dynamics to change the dynamics of a team with the aim of optimizing their work together.
Agile and distributed development seem to be at odds with each other. One is about close communication and short feedback loops, the other is about being effective with people in a different location. This talk discusses a number of patterns common for setting up Agile Distributed Development and will show the results that can be achieved once you get into a good Fully Distributed Scrum.
This talk summarizes the results of 4 years of industry surveys concerning the adoption and effectiveness of agile techniques. Very often the reality is significantly different than the rhetoric presented in mailing lists, in articles, and even in books. Many myths or ideas around Agile are explored, and some are proven false and some confirmed to be true based on survey results.
This presentation explores how the role of managers changes in Scrum. It helps managers to lead the introduction of Scrum acting as role models. It presents leadership principles that provide concrete guidance such as servant-leadership, empirical management, empowerment and respect, quality-first and continuous improvement.
In this original presentation from the Communitech Agile Event, Jeff Patton, winner of the Agile Alliance’s 2007 Gordon Pask Award, explains why one needs to embrace uncertainty in order to succeed with his/her Agile project and how to avoid some of the common mistakes leading to project failure.
In this presentation filmed during Agile 2008, Jeff Sutherland, co-creator of Scrum, and Guido Schoonheim, CTO of Xebia, present an actual case of reaching hyper-productivity with a large distributed team using XP and Scrum.
Mishkin Berteig presents a situation where he proposed to a software development team, which just started to experiment with Scrum, to accept 2-days iterations. The approach was trying to tackle their organizational lack of prioritization resulting in constant crisis. Their decision led to a bigger crisis which exposed the need for task prioritization.