"Must Have," "Should Have," And "Nice To Have" Tools For Agile Processes
by Liz Barnett, Carey Schwaber
Average:
9
(1 rating)
This is an excerpt
Executive Summary
Agile development processes explicitly de-emphasize tools, but tools are nonetheless crucial to Agile projects' success. Tools for software configuration management (SCM), unit testing, and software builds and build management are key success factors on Agile projects. Other tools are less crucial but can still add value. As more IT shops begin using Agile practices, the demand for tools that support these practices — notably refactoring, test-driven development, automated testing, continuous integration, collective code ownership, and management — will increase. Only lightweight solutions need apply for Agile shops' dollars, and even those will have to compete against open source solutions, which Agile teams largely prefer at present. There is no standard tool set for Agile teams; each team must carefully examine its particular situation to determine what tools to adopt.
TABLE OF CONTENTS
What Tools Are Right For Agile Processes?
"Must Have" Agile Tools
"Should Have" Agile Tools
"Nice To Have" Agile Tools
The Future Of Agile Tools
RECOMMENDATIONS
Tools Add Value To Agile Projects But Won't Ensure Success
Supplemental Material
Related Research Documents
This is an excerpt
Buy Risk-Free
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client? Log in to read this document.