Dennis Stevens discusses the theory of Agile, providing references for using Agile in the enterprise along with a competency model, and overviewing an enterprise Agile transformation.
Jean Tabaka discusses using design thinking and complexity theory in order to balance and Agile adoption.
Barry emphasizes the need to continue thinking critically about the processes and practices we embrace, accounting for the context in which they exist, and the importance of reflection and refinement at both the organizational and personal levels.
Joel Semeniuk shares some of the lessons he learned managing development teams, how he got into Kanban and why its principles are helpful.
In this presentation Don Reinertsen examines some key lean methods including queue management, batch size reduction, WIP constraints, and cadence. He also discusses the governing economic tradeoffs and how these methods can be exploited by product developers.
Karl Scotland on Kanban as a way of creating a model improving a business’ capability to meet its purpose based on systems thinking, workflow, visualization, work in process, cadence, and learning.
Simon Ogle, Alexander Kikhtenko, and Peter Thomas present a case study of a development team transitioning from a waterfall approach to 15 offshore Agile teams over a period of 5 years.
Chris O'Connor tells the successful story of a team’s transition to Agile in the middle of a major product release, mentioning the difficulties encountered and how they tackled them.
Nanjangud C Narendra presents a case study of an enterprise Agile project in the light of Lehman’s laws of software evolution, along with observations on Agile practices used and their outcome.
Craig Larman presents practices and tips related to adoption, structure, requirements, contracts, architecture and design, offshore, multisite development, and coordination with large Scrum teams.
Tim Wagner discusses how the Visual Studio team at Microsoft uses customer feedback to improve the development process, testing and productivity of a 50 MLOC product.
Eric Jan Malotaux presents a way of implementing SOA in small iterative steps, each step delivering value to stakeholders, higher than the costs involved, using feedback from previous steps to adjust the requirements and design accordingly.