Declan Whelan discusses Agile Coaching and the lessons learnt returning to coding as part of a new lean startup as well Agile Coach Camp, pair coaching and his role on the Agile Alliance board.
Henrik Kniberg discusses the journey to writing his latest book "Lean from the Trenches", the translation of the Agile Manifesto as well as his recent travels and Lean Startup projects.
Alan Shalloway discusses the challenges associated with transitioning companies to Lean and Agile methods on an enterprise scale. The interview discusses how Lean and Kanban can be used to encourage encourage incremental change and ongoing improvement, the cultural factors that can hamper Agile adoption, and why practices that benefit teams can actually harm the organization as a whole.
Recorded at the 10th anniversary of the agile manifesto signing, Jim Highsmith discusses how he works with executive management teams to introduce and integrate agile techniques into enterprise organizations from both the business and IT sides. He defines adaptive leadership and discuses adaptive ALM, continuous delivery, lean and Kanban methods.
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches. Jesper also discusses the benefits of integrating elements of Kanaban into existing Scrum teams and what can be achieved from the team seeing the entire value chain and owning the whole process.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Does success at the team level always result in success at the organization level? Sanjiv Augustine and Arlen Bankston discuss the Seven Deadly Sins that organizations repeatedly make so you can steer clear of them and benefit from a successful Enterprise Agile Adoption.
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.