aspose file tools*
The moose likes Agile and Other Processes and the fly likes Agile with SMALL teams 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 with SMALL teams" Watch "Agile with SMALL teams" New topic
Author

Agile with SMALL teams

Mike Dean
Greenhorn

Joined: Sep 28, 2005
Posts: 14
I have found (I think) that most aspects of agile programming are useful even for me as a solo programmer on hobby projects (no pair programming!). I run a data center that has only three programmers, and they generally work on their own projects, and I have not been able to convince them to use the other aspects of agile programming. Hard to get them to use SVN religiously, impossible to suggest TDD, we have no concept of continuous builds, etc.

On the other hand, except for my personal belief that it helps me as a relative amateur, it is hard to quantify any problems with our current system because the programmers are acutely aware of their own coding time, the systems generally work, etc.

How do you overcome resistance at the MICRO level - convincing even the solo programmer that agile is the way to go?
James Shore
author
Ranch Hand

Joined: Sep 21, 2007
Posts: 46
Hi Mike,

I've learned the very hard way that I can't convince people to do anything. I can force them to do things, but that only works until they quit. The best I can do is convince people to try things and see for themselves.

Mann & Rising's Fearless Change is an excellent resource for convincing people to change. It may have some ideas you can use.


James Shore, coauthor of <a href="http://www.amazon.com/Art-Agile-Development-James-Shore/dp/0596527675" target="_blank" rel="nofollow">The Art of Agile Development</a>. Website and blog at <a href="http://www.jamesshore.com" target="_blank" rel="nofollow">http://www.jamesshore.com</A> .
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
One thing you could do is teaching by doing. Ask for help on some tasks, and help them if they want, if only for a couple of minutes at the beginning. After some time, it might begin to feel a little bit like partial pair programming. Slip in a unit test here and there when working together. Have a visible board with your stories cards that shows your progress etc. pp.


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
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Agile with SMALL teams
 
Similar Threads
Stealth XP
Practical Java programming books
making the mathematical case for pair programming
Pair programming
Software process - recommended books?