This half hour presentation looks at a Fortune 500 company's effort to achieve faster time to market by transitioning from RUP to Agile. Hussman & Stenstad reveal the gradual process from readiness assessment and chartering through education and practice to the creation of an adaptive culture with a "living plan", sharing lessons learned along the way.
Agile teams seem to be meeting more resistance, as they scale up and move from "early adopter" territory into the mainstream. Does this mean Agile can't work in more traditional organisations? Not necessarily, say coaches Michael Spayd and Joe Little, in a new InfoQ interview: what's needed now is an awareness of the need to facilitate organizational change.
Adopting Agile practices requires a shift in the organisation on many different levels, but can making such a change lead to serious trouble?
The Agile Manifesto is six years old. Many have become disillusioned with Agile as it has spread and (inevitably?) been diluted. Post-agilism has been discussed even before Agile has become truly mainstream. Some have suggested that we have learned much over these years and the Agile Manifesto needs to be updated.
Trailridge Consulting's independent survey looked at the adoption of agile practices globally, and the characteristics of the agile companies included in the survey, including demographics and Agile methodologies in use. It went on further to examine the tools which support Agile Project Management and delivery, from spreadhsheets to full blown integrated Agile PM tools.
Agile coach and practitioner David Hussman talked to InfoQ about his approach to helping teams and organizations adopting Agile, including his ideas about customizing it without compromising the common denominators required to make Agile really work. He talked about "story tests", addressing manager fears as their team self-organizes, and building a vibrant development community.
A new article in CIO magazine spells out the ABCs of agile software development for managers.
An old post on "The Physics of Passion" resonates today, as the methodology argument continues: is Agile an approach worth embracing? Or just the latest flavour of corporate Kool-Aid? Kathy Sierra wrote that being accused of "drinking the Kool-Aid" can be a good thing: a sign that we're developing passionate proponents - and opponents.
"Better quality, plenty of features, fewer nights and weekends: what's not to like?" wrote Mary Branscombe in an interview with CS3 co-architect Russell Williams. Adobe has successfully adopted an iterative development process, leaving waterfall behind. This time they benefitted from a champion, who had successfully adopted iterative processes elsewhere, helping them over the rough spots.
Teams can get sidetracked by process when implementing Agile: they spin, trying to figure out which practices to start with, unsure which will have the biggest impact, or how they fit together. In their InfoQ case study, Amr Elssamadisy and John Mufarrige develop a customized adoption approach to help a team decide where to focus first - an alternative to adoption of pre-packaged methodologies.
Reginald Braithwaite describes how the art of selling can be applied by those seeking the adoption of agile development practices.
When transitioning to agile, success requires a true change in behavior and outlook. Daffyd Rees shares advice on "Cultivating Agile Attitudes" in this excerpt from the Agile Alliance's Agile Development Journal, including "Growing Agile Developers," "Creating Agile Coaches," and "Weeding out Hidden Problems."
In this conference talk Andrew Scotland tells how BBC's New Media division, characterized by a lot of uncertainty and emergent software process, decided to use Scrum to more effectively deliver software amidst all that change and uncertainty. Three years later - the difference is significant, and the journey was worthwhile.
In his recently published "Scrum and XP From the Trenches," Henrik Kniberg gives a comprehensive description of how he implemented a mix of Scrum and XP practices for a development team of 40 people.
Garlik, a UK based identify-fraud security company shared some of their recent success with Agile in an article on computer weekly. They built their main product, Datapatrol, from concept to completion in just 9 months and attributed their success to Agile practices and having a skilled dev team.