|
| The Agile April 2007 edition of the Agile Journal Focuses on Tools For Agile Projects. Tools play important roles on Agile projects. The Agile Manifesto cites the value of individuals and interactions over processes and tools, but this does not mean that individuals and interactions must replace processes
and tools. Over the past few years, I have written about the need for
appropriate tools on Agile projects. Even two years ago, this was a
fairly controversial position. "True" Agile developers eschewed the
need for tools, instead opting for manual techniques and interactions
to produce their software products. It's fair to say that Agile teams
in 2007 recognize the value that tools can play to support their
collaborative team efforts - and the necessity for tools on global
Agile projects. Our contributors to this month's Agile Journal share a
wide range of experiences and perspectives on the value of tools to
assist on Agile projects. >> Read the entire issue at http://www.agilejournal.com  processes and tools, but this does not mean that individuals and interactions must replace processes
and tools. Over the past few years, I have written about the need for
appropriate tools on Agile projects. Even two years ago, this was a
fairly controversial position. "True" Agile developers eschewed the
need for tools, instead opting for manual techniques and interactions
to produce their software products. It's fair to say that Agile teams
in 2007 recognize the value that tools can play to support their
collaborative team efforts - and the necessity for tools on global
Agile projects. Our contributors to this month's Agile Journal share a
wide range of experiences and perspectives on the value of tools to
assist on Agile projects.
But the tools question does still exist. To see both sides of the issue, Ryan Martens and Ron Jeffries debate the merits and weaknesses of using tools on Agile projects. Jim Ruehlin stresses the importance of collaboration, especially for Agile teams. John Scumniotales looks at the bigger picture: the necessity of processes and tools to support enterprise Agile initiatives. There are, of course, a wide range of tools from which to choose. David Hoehn contends that low-tech tools are and should be sufficient for Agile projects, particularly for initial forays into Agile development. Steve Mahoney shares his experiences using Microsoft tools on Agile projects. John Graham-Cunning advocates for the build manager, the person most affected by Agile techniques, and explains how automated builds can become the "heartbeat" of an Agile environment. And Tracy Ragan discusses the merits of a community developed approach to managing the continuous build. Hands-on experiences always give new perspectives. Mike Zwicker shares his experiences with Agile development at Lockheed Martin. And Kirk Knoernschild emphasizes the value of executable artifacts created by tools, and the impact they can have on software quality and delivery. What tools do you (or don't you) use on your Agile projects? Please feel free to share your experiences with the Agile Journal community. Send us your suggestions for new themes or issues to cover. And, if you'd like to contribute an article on this or another upcoming topic, go to the "Letters to the Editor" in the forum at AgileJournal.com and send us your ideas. Read all the articles in this issue at http://www.agilejournal.com
Set as favorite
Bookmark
Email this
Hits: 1356 Trackback(0)Comments (0)
|
TrackBack URI for this entry
Subscribe to this comment's feed