In Agile, adoption and transformation are typically viewed as one big event. Mike Cottmeyer provides a holistic perspective that looks as adoption as the implementation of practices, and transformation along two dimensions, organizational and personal. Mike discusses how they are a means to an end, and how to avoid the trap of focusing on practice adoption as a goal.
Ten Years after the Agile Manifesto Jeff Sutherland muses the question of whether Agile teams are truly Agile. You’re not Agile if you’re not producing product at the end of each sprint. Jeff discusses doing scrum well, velocity and production measurements and the next big challenge for Agile leaders.
In this interview, Lyssa Adkins and Michael Spayd, cofounders of the Agile Coaching Institute, discuss the role of the Agile Coach and the competencies (i.e. facilitation, mentoring, teaching, and coaching) necessary to become effective in that role. Also discussed are ways an Agile coach can transform teams and organizations while reinforcing behaviors that will endure after the coach leaves.
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.
Linda Cook, a well-known agilist, and board member of both the Agile Alliance and the Agile Leadership Network, discusses the agile coaching profession. Among other things, she covers servant leadership, being as a role model, types of individuals appropriate for the profession, and the differences between being an external coach versus being an internal employee in the coach role.
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.
On the 10th anniversary of the Agile Manifesto, Ward Cunningham discusses software craftsmanship, pair programming, and the changes in Agile over the last ten years. He explains how his original ideas have become diluted, and shares his latest project, based on ideas originating from his work with HyperCard, to create federated documents.
Founding members of the ICAgile Consortium, Ahmed Sidky and Alistair Cockburn, discuss IC Agile, along with Bob Payne, a consultant, coach and trainer. They explain why ICAgile was created, how it fits in with popular certifications like the Certified ScrumMaster, how organizations that deliver training can fit their courses into the ICAgile road map and how individuals can collect knowledge.
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.
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.
Brian Marick discusses what he means by micro-scale-retro-futurist-anachro-syndicalism and why we should go back to the roots of Agile. He talks about what he thinks were the mistakes in the Agile Manifesto, how it has lead to the state of the Agile community today, and how we can build better systems by making them so that they are much more easily tested.