It's always confusing, with the number of resources, the project type and the deadlines (Specially deadlines!), to choose a methodology for development. What are the characteristics that show you clearly that Agile is for you?
As I said in another post, I think agile development can be used in many situations. The limiting factor is usually the people involved. Does everybody want to try agile development? Is there enough expertise on the team to customize agile development to your specific situation?
Any prepackaged method, on the other hand, has definite limits, and the approach to XP we present in our book does too. One of the things I like about our book is that we state those limits clearly and unequivocally, and we also describe what to do if you can't meet one of our prerequisites.
Note that "Agile" is not a method, but a category that includes XP, FDD, Scrum, the Crystal family, DSDM, and so forth.
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> .
Originally posted by James Shore: As I said in another post, I think agile development can be used in many situations.
Which isn't very surprising when we remember that Agile Software Development is first and foremost a set of guiding *values*: http://agilemanifesto.org/
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