InfoQ sits down with Andrew Hunt, one of the original Agile Manifesto signatories, to discuss how Agile has diverged from the original vision and how pragmatic programming has evolved. Andy discusses CoffesScript, Arduino, and HTML5 and he shares his views on the effectiveness of pair programming, Agile testing methods and other practices.
M Dwyer of BigVisible Solutions talks about the process of transforming businesses to agility, including the concept of Agile localization in global efforts. Dwyer says that with distributed teams across multiple time zones and cultures it is good to establish a group of Agile missionaries to go forth and train people on Agile. He also discusses how to transfer Agile skills to the next generation.
Laurie Williams, who heads the Software Engineering Research group at North Carolina State University, discusses her research into Agile principles and practices. Williams also talks about Comparative Agility, which is a tool to show teams where they stand in terms of the adoption of Agile practices. Comparative Agility was launched in 2007 and since that time over 400 people have used it.
In this interview, Agile management expert Johanna Rothman talks about the process of managing in Agile environments, particularly for distributed teams. Rothman also helps to distinguish between self-directed, self-organized and self-managed teams. And she stresses the importance of clear communication amongst team members, as well as the ability for managers to learn new skills.
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.
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.