Stakeholders of an Agile project often seek the help of a seasoned Agile coach to gauge the effectiveness of the Agile process and practices that their team is following. The intention is to plug the holes and make the team more effective. Recently, on the Scrum Development group, Scott Killen started a thread on how to do an audit on an Agile team.
Rashina Hoda is a PhD researcher who has been examining how self-organization actually happens on teams. She has studied teams in New Zealand and India and identified six distinct roles that emerge when teams effectively self-organize. She spoke to InfoQ about her research, which will be published at the International Conference on Software Engineering (ICSE2010) to be held in Cape Town in May.
The Agile community is developing consensus around three important areas of practice: requirements gathering, agile coaching, and open space formats for group learning. At the recent Scrum Gathering, these topics were prominent topics of discussion on Day 1, Day 2, and Day 3 of the event. InfoQ explored each of these further to gain a better understanding of their place in Agile.
March 19 - 21, agile coaches will gather in Durham, North Carolina to share, learn, and improve their skills. Registration for this event costs no money, but each participant must write a position paper in order to qualify. The event will have no preset agenda of sessions. Instead, the Open Space approach will be used, and participants will create the agenda at the event itself.
Discussions about agile's "decline and fall" have been a somewhat recurring theme here on the AgileQ, and in the community in general, centering around sentiments that people aren't adopting agile effectively, that they're doing it wrong and screwing it up. Kevin Schlabach poses the idea that the agile community itself, by not growing new leaders, has a hand in causing this.
Rachel Davies and Liz Sedley, co-authors of the book Agile Coaching, gave a fun session “Top Ten Tips for Agile Coaches”. The session could well have been called “Top Ten Things that Many Agile Coaches get Wrong”.
Increasingly there are reports of initial success followed by failures with Agile adoption. Sometimes these problems are inadvertently caused by Agile coaches.
Ruby on Rails has been around for about 5 years and in those years developers have created a lot of applications. Many of those applications were created while learning Ruby and Ruby on Rails and may not have used the best practices but yet made it into production web sites. These web applications can be problematical but a new book focused on the solution is available.