• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Difference between methodologies

 
Ranch Hand
Posts: 445
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Agile,Scrum,XP,SDLC,Waterfall,RUP...whew!!

Can anyone please list down the differences or similarities between the above mentioned methodologies?

Please feel free to add any other methodology I may have missed.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
author
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
reply
    Bookmark Topic Watch Topic
  • New Topic