Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Forrester have recently released the results of their November 2011 Global Agile Software Application Development Online Survey in a report entitled "Survey Results: How Agile Is Your Organization?" It contains a number of interesting findings around how organisations that have adopted Agile are dealing with their implementation.
A recent post by Paul Dolman-Darrall on the Value, Flow, Quality blog proposed a list of the 20 most influential people in the Agile community.
The Agile community has a great tradition of making fun of itself and April Fools Day 2012 was no exception. Here is a wrap up of some of the best gags from this year that you may have missed.

Naresh Jain won the Gordan Pask award in 2007. He writes about the need to adapt our processes and build on top of agile practices, one size doesn't fit all and processes must evolve as we tackle more and more complex problems. He examines some of the key elements from the Lean Startup movement and shows how they are the logical next step for many agile implementations.

Jay Fields takes a look at pair programming from an adoption perspective. This article is for you if you already know what pair programming is and guidance on how to get to the point of successfully practicing pair programming. Jay goes over everything from an optimal seating arrangement, to effective coaching techniques, to calling out common mistakes to avoid.
Mark Levison observed that, after solid classroom training, teams in larger companies still struggle to adopt TDD. To better understand the problem he surveyed team members. In this article he shares the problems he uncovered and his own comprehensive strategy, designed to help anyone introducing TDD into an organization.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
Fred George discusses Programmer Anarchy, a development process where programmers are not just empowered to act but the driving force behind a product, leading to substantial increase in results.

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.
For those getting started with Agile, this book offers a detailed first-person account of how one Swedish company implemented Scrum and XP with a distributed team of 40 people, and how they continuously improved their process over a year’s time.