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.
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.
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.
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.
Linda Rising talks about patterns and interacting with customers, the need for a better interaction between developers and customers, how she arrived at these patterns, teaching others how to teach.
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, 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 Amr Elssamadisy talks about the practice of Agile software development and why it works. Elssamadisy said Agile processes work because developers are able to learn from their successes. Indeed, Elssamadisy said developers learn from both their mistakes/failures, as well as from their successes. Moreover, developers need to learn how to work with teams and to handle confrontation.
Jeff Patton describes the different ways Agile teams deal with users and then digs in deep into story mapping. Jeff says: "For me, the story mapping thing is going back to using the story as a genuine conversation to actually drive understanding of the system, not as what I've seen it become – molecular conversation about the details of a particular feature and how we're going to test it.
Dan describes the importance of group relations to Agile adoption and how an awareness of group dynamics can help keep energy focused on the task at hand. He also suggests how Agile games can be used to prepare for an upcoming agile adoption by revealing an individual's willingness to participate fully. Finally, hshares his views on the new PMI-Agile community.
In this interview with Jeff Patton at Agile 2008, he talks about three strategies that can help product owners do their job more effectively by embracing the inherent uncertainty in all software development. Namely they are understanding the ultimate goals of the project, delaying decisions until the last responsible moment, and scaling up by building quality.