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 How to be Agile in a non Agile team? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "How to be Agile in a non Agile team?" Watch "How to be Agile in a non Agile team?" New topic

How to be Agile in a non Agile team?

Qunfeng Wang
Ranch Hand

Joined: Jan 28, 2005
Posts: 434
I'm an Agile fan, but unfortunately work in a non Agile team. How can I introduce Agile to my team? If I can't do this, how to get Agile practices as much as possible in my current team?

I've tried to import some tools often used in Agile team to my team. CruiseControl and CheckStyle. But the result is not good enough. We have no unit tests, the CruiseControl only helps us build(compile) the project when change happens in CVS. And we have to delete many good CheckStyle rules to get the build pass. Otherwise, there are hundreds of errors need to be fixed.

Everyone sits in his/her cube, I don't have the rights to let everyone sit together and pair programming.

No one in our team has TTD experience. I can't find an entry point to introduce Agile to my team. Do you have some ideas?

I don't think I'm the right person to introduce Agile. Initially, i just want to learn Agile in this process. I think i'm failed. But i still want to get some Agile experience, would you have some suggestions?


To be or not to be. It's a question.
Ilja Preuss

Joined: Jul 11, 2001
Posts: 14112
You definitely have full control over one entry point for introducing Agility: yourself. If you want, you can start immediately to organize your work using user story cards, write your code in a test driven fashion, learn how to refactor your code etc. pp.

Once you have some experience with at least some of those techniques, you will already be in a much better position to suggest them to your coworkers - it's not just something you heard about, it's something you can tell your own stories about! And once you got some of them hooked, you can start convincing them to also try some other techniques together.

A good book on the topic is "Fearless Change".

The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33134

Originally posted by Louis Wang:
We have no unit tests,

This sounds like the low hanging fruit as it doesn't require management to allocate resources. Can you write some unit tests as part of your coding tasks? You are testing your code anyway.

When I started writing unit tests, I got agreement from my teammates that they wouldn't break any tests. At the time there weren't any so it was easy to get agreement. After I wrote some for a while, I was able to demonstrate their value.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
I agree. Here's the link:
subject: How to be Agile in a non Agile team?
It's not a secret anymore!