Two of ThoughtWorks’ finest, Martin Fowler and Jez Humble, talk about the notion of Continuous Delivery, which enables organizations to build software that is production ready at all times. To do this, enterprises automate the build, deployment, and testing process, and improve collaboration between developers, testers, and operations. The duo discusses a variety of related issues.
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.
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.