The final date for session proposals for the Agile 2011 conference is February 14, 2011. With less than one week left now is the time put the finishing touches on proposals and get them into the submission system.
The Working with Customers stage at Agile 2011 is looking for stories and submissions from customers of agile teams. The stage explores the interactions between the customer community and Agile development teams, focusing on the non-technology functions as well as the Agile development teams themselves. In this item the stage producers answer questions and appeal to real world customers.
A personal time management approach known as "The Pomodoro Technique" is becoming quite popular with agile practitioners. Pomodoro includes a number of practices similar to those used by an agile team: time-boxing, frequent opportunities to inspect-and-adapt, estimation, a preference for low-tech tools, and an emphasis on maintaining a sustainable pace.
A group of people interested in improving the state of the art in Automated Functional Test Tools gathered for an annual workshop the Sunday before Agile 2009. Among the topics covered: Lightening Talk demos of various tools, Porting Cucumber to .NET, Documenting existing functional test tool capabilities in a spreadsheet and the limits of Capture/Playback tools.
The Project Management Institute (PMI) officially launched their Agile Community of Practice at the Agile2009 conference. The group's stated mission is: "To equip PMI Members with Agile skills and knowledge" Mike Griffiths has been credited with getting things moving when he issued a challenge at Agile 2007 that PMI form an Agile Specific Interest Group.
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”.
On Monday at the first day of Agile 2009 Liz Keogh ran a workshop and Effective Feedback.
Several InfoQ editors will be attending the Agile conference this week and reporting on the sessions. Stay tuned to InfoQ to read the latest about the happenings at the conference and get reports about the most interesting and provoking sessions.
Bas Vodde describes strategies for large teams with legacy software to adopt Scrum successfully. Bas discusses communication problems found in most component teams and why and how teams - especially large ones - should make the change to feature teams and how that change affects organizational structure.
While Scott Ambler, Ross Pettit and others continue to pursue the creation of a maturity model for agile, David Starr has looked at how and why an organization might want to measure things like: agility, craftsmanship, and organizational success. He found craftsmanship relatively easy to measure, while agility was the most difficult to measure in a useful way.
The Agile Alliance's Agile2009 conference program has been announced, again organized by theme, not job description. It will be held this year in Chicago from Aug. 24-28. New: Coaching, Manifesting Agility. Back again: Open Jam, Programming w. the Stars, Live Aid, Muzic Masti, AAFTT (Testing) Workshop. Immediately followed this year the PLoP conference, also in Chicago.
In this interview with Jeff Patton at Agile 2008, he talks about three strategies that can help product owners do their job more effectively by embracing the inherent uncertainty in all software development. Namely they are understanding the ultimate goals of the project, delaying decisions until the last responsible moment, and scaling up by building quality.
Robin Dymond gives an overview of Lean, how it can help take Agile to the 'next level' and why organizations that fail to change will not have successful Agile teams. Robin describes an organizational mismatch between traditional hierarchies and team structures. He believes that organizations will need to reorganize around teams to get the most out of Agile.
Pollyanna Pixton tells us that within a culture of trust leaders must stand back and if they don't then they are hampering and restricting the productivity and the creativity and the innovation of teams. She discusses how leaders can foster a culture of trust and what they must do to get the most out of Agile teams.
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.