Answering this question appropriately could easily fill a book or two. I think you would be well advised to ask something more specific. What do you need that information for?
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
One way to get around that problem by NOT looking at methodologies, and instead focusing on the practices that make up those methodologies. Therefore you can look at "test first development", "stand up meeting", "retrospective", or whatever other practice, and decide if that practice is good for your environment and will deliver what you need or not.
The question is, do you have clarity on what you need? Do you need to improve quality? Increase delivery speed? Or possibly increase the lifetime of your product? Until you know what you and your team want out of a new set of practices, you can't effectively choose what to adopt or know if what you have adopted is working or not.
This book is a duplex book, and the first part has nothing to do with patterns at all, it really is all about getting clarity on your goals and choosing the practices that will help you achieve your goals regardless of what methodology they come from
Amr Elssamadisy<br /><a href="http://www.amazon.com/Agile-Adoption-Patterns-Roadmap-Organizational/dp/0321514521/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1220909336&sr=8-1" target="_blank" rel="nofollow">Agile Adoption Patterns</a>
He was expelled for perverse baking experiments. This tiny ad is a model student: