Agile Tools: The good, the bad, the ugly |
|
|
|
| Written by Richard | |||
|
This White paper addresses a dilemma that faces many Agile teams that are trying to decide on the best tools to use in their daily practices.
|
Agile Marketplace - Announcements and Special Offers
Complimentary Webinar w Forrester Analysts on Agile and Lean ALM
Complimentary webinar with Forrester Analysts Jeffrey Hammond and Dave West. Learn about Lean ALM Development, optimizing processes, cutting costs and compliance by design.
Read More
Agile CMMI – The Best of Both Worlds
Shares how a leading financial institution gains CMMI level 3 compliance and supports Agile practices.
Register for CollabNet webinar May 21
Requirements-based testing (RBT) can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage. Download the Requirements-Based Testing whitepaper





Agile software development adoption spreads over the world. According to the latest surveys, about 70% of organizations adopt agile practices and stick with it. During the last 10 years, agile methods jumped from nowhere to the peak. Such rapid revolution demands new tools. There are many developers-focused tools appearing including JUnit, Eclipse, Cruise Control, etc. However, the project management community is less self-sufficient and unable to create new tools for the new methodology in their spare time. As a result, most companies are still using old-fashioned project management tools like MS Project or generic tools like spreadsheets for project planning and tracking.