In this interview at Agile 2011, Jez Humble discusses continuous delivery and the deployment pipeline, emphasizing the importance of feedback and automating tests at every level to validate deployments. Gone are the days of massive acceptance test scripts. He also talks about the evils of feature branching, and speaks on the DevOps practices to collaborate all the way through the delivery cycle.
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.
Brian Marick discusses the difficulties met trying to maintain tests that are vital to a project’s success, and how mocking frameworks can help, providing advice on writing unit and integration tests
In this interview Elisabeth Hendrickson talks about the Agile Alliance Functional Testing Tools (AA-FTT) group, a discussion group related to advances in functional testing tools for Agile projects. She says this Yahoo group focuses on automated functional testing as an integral and essential part of Agile development. She also discusses the maturity of the state of functional testing tools.
In this interview, Cyndi Mitchell talks about ThoughtWorks’ concept of “Continuous Delivery,” which focuses on the last mile of software delivery. Mitchell also discusses the “adaptive” in ThoughtWorks Studios’ Adaptive ALM (Application Lifecycle Management) strategy, in which Agile solutions must be adaptive to users’ needs. And Mitchell describes ThoughtWorks Studios tools: Mingle, Go and Twist.
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.
Dan North discusses the roots of BDD and what it is today. Dan reviews the early history of BDD and then dives into the details of BDD; what it is, how it relates to teamwork, functional and non-functional requirements, and legacy code.
Michael Feathers interviews Steve Freeman in an informal setting about current design techniques and the evolution of the software development community. They focus on the role of design in the community, how it has evolved, and where they think it needs to go.
Nathaniel Talbott discusses the concept of Experiment Driven Design.
Tobias Mayer talks about the philosophy behind WelfareCSM, unbounded vs bounded creativity, the application of Scrum outside of software development, Kanban vs Scrum, the benefits of fast-failing, software development as an artitistic endeavour, software craftsmanship and XP, test-driven development, and the done state.
In this interview with Sadek Drobi, Michael Feathers explores working with legacy code, working with different programming languages, the right scope/size of modules, and the importance of readability of code regardless of the programming language.