In this interview Jez Humble discusses the concept of continuous delivery, which implies that software should always be production ready throughout its lifecycle. That means that every build could be released into production and run effectively. Continuous delivery involves build and deployment automation, continuous integration, test automation, managing infrastructure and environments and more.
In this interview Ellen Gottesdiener and Mary Gorman of EBG Consulting discus the process of getting teams to collaborate and to think and work in an Agile manner. They also talk about their involvement with the International Institute of Business Analysis (IIBA) and their efforts to extend business analysis with Agile methods. They also are working on a new book on the subject.
Ashley Johnson shares his views on Agile development, in particular the move toward “Personal Agility.” Johnson says it is not possible to have an Agile organization of any scale without having the individuals behave in an Agile manner. Part of Personal Agility is about taking responsibility and approaching others as humans rather than obstacles. Johnson also discussed the Scrum vs. Kanban debate.
In this interview, Joshua Kerievsky, founder of Industrial Logic, discusses the need for developer performance metrics to enable organizations to determine the capabilities of developers. He also discusses his project known as the Limited Red Society. The goal of the Limited Red Society is to help developers limit the amount of time their code is in the red.
Arlo Belshee and James Shore, both Gordan Pask Award winners, discuss their experiences and thoughts regarding continuous flow (i.e. without iterations) agile development practices and techniques. They discuss many well known and not-so-well known practices such as naked planning, kanban, the detective's blackboard, and MMFs and provide insight into how these practices affect success.
David Anderson discusses using the Kanban concept to make software development more efficient, the use of Kanban in both a large enterprise organization and as a consultant, how Kanban (in association with related systems such as CONWIP and Drum-Buffer-Rope) is catching on in the industry and helping developers improve predictability of their software, and the Lean Software and Systems Consortium.
Mary and Tom discuss the history of Lean, and what they feel are the most important things for software teams and organizations to thrive.Results are not the point, the point is growing your people, converting them into effective problem solvers who are relentlessly improving. If everybody in the organization is a problem solver, you'll get steadily better and better.
Jim Coplien, co-creator of Data, Context and Interaction (DCI) architecture, covers a variety of topics including DCI, the importance of language support for DCI and the state of Agile development. Coplien has championed the DCI architecture with Trygve ReensKaug, the inventor of the Model-View-Controller (MVC) architecture, which separates data and its processing from presentation.
Mary Poppendieck talks about her last book "Leading Lean Software Development", a book for the product, program and all C-level managers, showing them how to apply agile principles and practices starting from the realization that development teams are not successful if they are not in the same boat with their managers.
Henrik Kniberg discusses the differences among different Agile processes such as Scrum, XP, and Kanban. He shares the thought that processes wars are meaningless and we need to see each process as a tool; there are no bad tools; just tools used for the wrong purpose.
In this interview at Agile 2009, Joshua Kerievsky describes how his team was able to transform their software development project once they found and used an appropriate system metaphor. Joshua also shares how his development team has let go of many traditional practices and continues to refine their skills such that they are delivering more value regularly.
Robin Dymond gives an overview of Lean, how it can help take Agile to the 'next level' and why organizations that fail to change will not have successful Agile teams. Robin describes an organizational mismatch between traditional hierarchies and team structures. He believes that organizations will need to reorganize around teams to get the most out of Agile.