InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Simple Tools Preferred in the Agile Tools Space

Posted by Vikas Hazrati on Sep 07, 2010

Sections
Process & Practices,
Architecture & Design,
Development
Topics
Survey ,
Tools ,
Agile
Tags
Productivity

Agile does not necessarily mandate or recommend the use of tools. Ideally, the development could also be done on a command line interface with requirements present on index cards. However, in the last few years, several tools have emerged and have acted as a catalyst to successful Agile development. Migan and Gaia recently conducted a survey to find out the use of such tools in the Agile space.

According to them one of the reasons for them to conduct the survey was to evaluate the reason Agile teams would like to work with simple tools.

A large percentage of companies are still using traditional project management tools, such as MS Project, and spreadsheets (MS Excel) for their agile development. After having interviewed some companies, we discovered that the reason behind this is that many Agile tools, offer a wide array of different customizable options and are thus harder to use and less intuitive than plain tools such as spreadsheets, pen and paper.

The survey was conducted with 100 representatives spread over 35 countries including UK. Sweden, Egypt, United States, France, Canada, India, Spain, Poland, Ukraine, Malaysia, Brazil, Netherlands, Romania, Italy, Australia, Germany.

The results showed an interesting mix of use of simple tools along with the software Agile project management tools.

  • 25% of all responses included physical wall and paper, and 23% included spreadsheets along with other Agile tools that they were using.
  • Though the software Agile tools have virtual storyboards, 62% of the collocated teams still used tangible tools like physical walls and paper.
  • The most desirable aspect of an Agile tool was the 'ease of use' followed by 'customizability' and 'price' as close seconds.
  • Least satisfactory aspect of a tool was 'lack of integration with other systems' followed by 'lack of custom reports'.

Though a detailed analysis of the survey would be published later, according to Migan and Gaia, the preliminary analysis showed significant use of simple and tangible tools.

Agile tool usage survey highlights the fact that a large majority of companies adhere to simple tangible tools, and that usability is the most valued aspect of tool usage.

The results, were in line with the a similar study done by Michael Dubakov and Peter Stevens from TargetProcess.

The study results revealed that tangible tools like whiteboards, cards, big visible charts got a score of 57 ahead of 52 for web based Agile tools and 43 for spreadsheets. Keeping to the inherent philosophy of Agile most teams wanted to keep things simple.

Michael and Peter combined their results as recommendations for teams based on their setup. They concluded that based on the team set up and status reporting required, either tangible, web based or a combination of the two might be required.

              No Status reporting required             Status reporting important
Small Collocated Team           Tangible tools            Mix of tangible tools and web based Agile tools
Large Collocated Team            Mix of tangible tools and web based Agile tools            Web based agile tools
Distributed Team            Web based agile tools            Web based agile tools
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

recommendations by alireza haghighatkhah Posted
Tools for Agile by XebiaLabs XebiaLabs Posted
  1. Back to top

    recommendations

    by alireza haghighatkhah

    Thanks for sharing, it’s very good and I’m totally agree with mentioned recommendation, I think the ease of use and visibility is two most important factor of using agile tools in teams and additionally large scale & distributed agile teams can use tangible tools like physical wall & paper locally or in smaller group as part of team.

  2. Back to top

    Tools for Agile

    by XebiaLabs XebiaLabs

    Good point – it’s very important to have tools in place for agile methodologies to be successful. After all, the whole point is to increase productivity, not increase work. One of the best tools for an agile team is deployment automation because it frees up time and resources for operations teams to focus on more important tasks. Agile tends to generate more deliverables for operations teams to deploy, which can create a backlog if companies are still relying on tedious, manual deployment processes, so automating this process greatly simplifies the to-do list. Would you agree?

Educational Content

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?