We have 4875 guests and 8 members online

Agile Sponsors

HP


CollabNet


TechWell

Home > Articles > Columns > Editors Note > Tool Integration Challenges & Benefits - August 2006

Tool Integration Challenges & Benefits - August 2006

E-mail
Written by Liz Barnett   
Thursday, 03 August 2006 05:11
The Agile Manifesto begins by stressing the value of "individuals and interactions over processes and tools." While it's true that the emphasis on people and collaboration makes all the difference on an Agile project, there is no question that tools are a necessary component of success. I've noted many times over the past six years that I have never seen a successful Agile project that did not, at the very least, have a strong software configuration management and build environment in place. This is particularly true for those organizations looking to scale their Agile efforts to enterprise-wide initiatives and distributed Agile projects.


This month, we look at the benefits and challenges of using integrated tools to assist with Agile projects. Kirk Knoernschild discusses how automating processes with supporting tools can "activate" the agile lifecycle. Kevin Parker shows how poorly many companies do in supporting tool integrations, and how significant the impact of failure can be. That said, Ross Pettit argues that "while the tools make the [Agile] practices more efficient, they do not themselves provide value without fundamental practices in place."

Taking this one step further, Venkatesh Krishnamurthy shares his experiences using tools on geographically distributed Agile teams. And we'll learn how Shopzilla, a leading shopping search engine company, has leveraged tools alongside Agile practices to support its rapidly growing business.

Agile teams value individuals, interactions, collaboration and responsiveness over traditional tooling and documentation. But as Agile teams grow (in size, number of locations, number of companies on a teams, etc.) it will be critical that they invest in a strong underlying environment. Strong doesn't mean rigid. Strong doesn't mean plan-driven. But strong does mean scalable, if we are to support teams building business-critical applications in today's economy.

What's your take? What tools have become necessities to your Agile teams? Please let us know what you think. And, if you would like to contribute an article on this or another upcoming topic, go to the "Letters to the Editor" in the forum at AgileJournal.com.

 

Liz Barnett
Editor in Chief
editor@agilejournal.com

Trackback(0)

Comments (0)Add Comment


Write comment

security code
Write the displayed characters


busy
Last Updated on Saturday, 11 November 2006 22:57
 
Cialis

Agile Marketplace - Announcements and Special Offers

Upcoming Webcasts
Sponsored by Urbancode - On Demand
Mastering Complex Application Deployment
Sponsored by CollabNet - Wednesday, August 24, 2011
Closing the Agile Loop: Continuous Integration, Continuous Information

ScrumWorks Pro – The World’s Best Agile Project Management Tool
Simply put, CollabNet’s ScrumWorks Pro is the best Agile project management solution on the market, bar none. More than 150,000 Agile professionals rely on the power and simplicity of ScrumWorks every day.  But don’t take our word for it – try it yourself for free. CollabNet is now providing the first 10 users of ScrumWorks Pro at no charge!
Download ScrumWorks Pro today!

The Business Case for ALM Transformation
Are legacy systems holding your company back?  Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper