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.

Agile Tooling Survey - What Is Your Team Using?

Posted by Deborah Hartmann Preuss on Oct 18, 2006

Sections
Process & Practices,
Development
Topics
Agile ,
Artifacts & Tools
Tags
Statistics
Pete Behrens of  TrailRidge Consulting wants to know what kind of tooling Agile teams are using, and he invites our readers to respond to his short Agile Tooling survey.

When the term "Agile" was first coined, it's a good bet that practitioners knew one another, and had a pretty good handle on what was being implemented and invented.  But years of creative adaptation, combined with organic growth far beyond the initial originators, must make it difficult to categorically say "here's what's going on out there".  Leaders in the field still want feedback, though, and seem to be turning to surveys to get it: commercial customer surveys, invitation-only surveys, public surveys.

So, here's an open survey, looking to discover what Agile teams are using to automate aspects of their process: not just software engineering tools, but also requirements management, project management, acceptance testing and remote collaboration software.   This survey is independent from any particular tool vendor and Behrens states it's not intended for marketing use by any particular vendor.  It consists of 16 questions and is designed to take about five minutes.  

It's interesting to see that there's a wide variety of responses acceptable, with multiple responses, and write-in "other" answers. For example:
B1: What type of tool(s) does your team use to manage requirements, user stories and/or the product backlog?
Please choose all that apply:
  • Manual note cards or sticky notes
  • General Office Product (e.g. Microsoft Word/Excel, Star Office, etc.)
  • Wiki (e.g. ScrumWiki, TikiWiki, etc.)
  • Internally developed application
  • Agile Process Tool (e.g. ExtremePlanner, Rally, ScrumWorks, TargetProcess,
  • VersionOne, XPlanner, etc.)
  • Traditional Requirements Management Tool (e.g. Borland Caliber RM, IBM
  • Rational RequisitePro, MKS Requirements, Serena PVCS/TeamTrack, Telelogic)
  • Other (please Specify):
Behrens also wants feedback on the survey itself - an (optional) question asks: "Are there questions you wish we would have asked or asked in a different way?"

You can download the survey pdf on the InfoQ site and fax it to Behrens, or take it online on the Trailridge Consulting site. We will announce when the results are posted, and at the end of the survey you can request a copy of the results.
  • 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!

Tooling - Results? by Geoffrey Wiseman Posted
Re: Tooling - Results? by Geoffrey Wiseman Posted
  1. Back to top

    Tooling - Results?

    by Geoffrey Wiseman

    Were there any results published?

  2. Back to top

    Re: Tooling - Results?

    by Geoffrey Wiseman

    Forget it; found 'em.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

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.