Aino Corry discusses various aspects of Agile Retrospectives: how to get them accepted, core principles, length, frequency, structure, techniques for handling problems, and much more.
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.
Ron Bodkin of Big Data Analytics discusses early adoption of Hadoop, NoSQL and big data technologies. He discusses common patterns and explains how developers can write low-level primitives to optimize MapReduce function. Other topics include Hive, Pig, multi tenancy, and security.
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.
Funding models and portfolio management approaches need to account for increasing levels of uncertainty, change and competition by compressing planning horizons, speeding time to market and recalibrating frequently. In short, organizations should apply real options and Agile methods for project approval, planning and oversight, not just for execution.
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.
Chet Hendrickson was interviewed at Agile 2011. He discusses the need to get back to basics, to the ideas that made agile successful in the first place - small teams working closely with empowered product owners and using good technical practices. He describes the Agile Sweet Spot and talks about how organizations can work towards achieving it.
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.