In this interview, Jeff Patton discusses the Product Owner role and points out that Agile has never been very focused on the customer. While Agile development excels at “delivery”, it struggles to support “discovery” (i.e. defining what the customer really needs). Also discussed are techniques such as Lean Startup and story maps and the importance of defining business value in an Agile context.
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.
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.
Mik Kersten discusses the role of Mylyn and Tasktop in Agile development and how these tools return control to developers. Also: how Mylyn streamlines development in Eclipse.
Joe Armstrong and Dave Thomas take a look back on the evolution of software and progress that has been made. They make some observations about the actual state of the industry and highlight problems that prevent it from delivering quality software. They try to identify reasons of these issues and suggest craftsmanship as possible solution.
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.
Dave Hoover tells his story of becoming a software developer why he wrote Apprenticeship Patterns for those new to the development world. He gives a couple of examples of the patterns in his books and how he sees readers benefiting from the information in the book.
Nathaniel Talbott discusses the concept of Experiment Driven Design.
Brian and dave discuss what it might mean to be a true craftsman and why the idea of craft has become so popular of late. Other issues discussed include the question of why craft seems to be focused almost exclusively on programming and why everyone does not aspire to be a craftsman? Programming as performance art, programs as literary artifacts, and code "habitability" round out the discussion.
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 filmed during RubyFringe 2008, Luke Francl explains his position towards testing. While supporting unit testing, he thinks testing is not going to reveal all application defects. Development teams should also practice code reviews and usability tests which are likely to discover bugs not visible though other methods.
In this interview made by InfoQ’s Deborah Hartmann during Agile 2008, Rebecca Wirfs-Brock talks about software design, the need for good design and the technical debt that might accumulate slowing down the development process. The conclusion is that agile developers should not disregard design.