2 Replies - 2269 Views - Last Post: 26 June 2010 - 09:48 PM

#1 induja   User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 1
  • Joined: 20-June 10

How do you document Agile software projects?

Posted 22 June 2010 - 06:27 AM

We've been trying various tools to document our projects. Have tried everything from the Rational Rose suite to a basic Wiki with Visio to write up just the right amount of documentation, use cases and specs. Lately we've adopted a more agile approach to development and wanted some ideas on what you guys use to communicate clearly within your teams and capture some of the thinking and design that goes into your projects.

We're now trying FogBugz with a Creately diagramming plugin that seems to work quite well as its very easy to use, includes a wiki and lets us quickly draw our mockups and flowcharts right there in the browser.

This post has been edited by induja: 22 June 2010 - 06:29 AM


Is This A Good Question/Topic? 0
  • +

Replies To: How do you document Agile software projects?

#2 sbromley   User is offline

  • D.I.C Head

Reputation: 21
  • View blog
  • Posts: 127
  • Joined: 20-May 09

Re: How do you document Agile software projects?

Posted 24 June 2010 - 07:16 AM

I work on an agile team, and we use JIRA for keeping track of tasks assigned, bugs, and user stories. It fits with the agile process perfectly. As for req and design documents we still use file shares to store everything. All of our tech docs are pretty vague though. Design documents kind of feel like a formality to me anymore. All of our code documentation is done with javaDocs, maven site documentation, a company wide social network, and we just started using drupal.

In your case are you using FogBugz for your tasks, bugs, and tech docs?
Was This Post Helpful? 0
  • +
  • -

#3 The Neoracle   User is offline

  • Check, check, 1, 2.
  • member icon

Reputation: 21
  • View blog
  • Posts: 4,097
  • Joined: 30-March 01

Re: How do you document Agile software projects?

Posted 26 June 2010 - 09:48 PM

Can you expand more on what you mean by "documentation"? Do you have a business person on the team? Are you writing user stories? How do you do iteration planning? Have you looked at using Cucumber or FITness for atdd?

In agile, typically the only documentation of a project is user stories for communication between the business and the developers, a common vocabulary, and executable automated testing at various levels for inter-developer communication.
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1