File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Agile and Other Processes and the fly likes Agile Adoption Patterns: Technologies Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Agile Adoption Patterns: Technologies" Watch "Agile Adoption Patterns: Technologies" New topic

Agile Adoption Patterns: Technologies

Tomasz Prus
Ranch Hand

Joined: May 20, 2008
Posts: 73
I know that there is some division between technologies, tools and libraries for which ones are Agile and those are not. Can You recomend me any?
Katrina Owen

Joined: Nov 03, 2006
Posts: 1367
I think the tool would depend very much on what you are trying to accomplish.

My team tried using something which was essentially a bug-tracking system to track stories, requirements, and tasks.

It turns out, whiteboards and post-it notes were much more appropriate for us.

If you look at it from the vantage point of purpose rather than tools, Agile is about making it possible to produce a good quality product in a given amount of time - or several given amounts of time.

Certain practices help achieve that. Certain tools might also be more helpful than others, but even a great tool would be no help at all if there is no place for it.

A burn-down chart is not going to help much, if the product owners add requirements and stories every day - whether it is on a digital dash-board or a low-tech whiteboard.

I while back I was involved in creating a small utility using TDD. It was basic, did two things, but the code pretty much read like a newspaper article. Certainly, it wasn't perfect, but it was a nice little piece of code.

After a while, another feature was needed. Within two days, a base class had been copy/pasted, renamed to plural in order to add a feature, the display code suddenly contained calls to the database and was making decisions based on a mysterious status code.

The purpose of making it nice and clean was so that when it needed to be extended, we would have the flexibility of adding a feature without breaking any windows... I kind of doubt that a library would have helped keep that code clean. (A couple of hours of refactoring, however, did wonders)

I guess my personal opinion about tools, are that if they can let you work in an agile fashion - great, but even the best tools probably aren't going to bestow agility.

Huh. I hope that didn't sound maudlin' :-)
I agree. Here's the link:
subject: Agile Adoption Patterns: Technologies
jQuery in Action, 3rd edition