Development methodologies

Software development methodologies – talking about them, criticizing them, and perhaps even using them – are all the rage. (If this is not the case in your friends’ circle, perhaps one of us have the wrong friends? 🙂 ) For example, the waterfall method is (rightly) considered old-fashioned and ineffective, but where do you go to find out how to do it right?

There are a ton of books about development methodologies, from the agile to the heavyweight, and most of them are either excruciatingly boring or just plain wrong.

Fortunately, a guy named Mishkin Berteig has brought us a page entitled Books, Web Sites and Tools for Software Technology, which lists a whole raft of excellent books on the subject – go browse it, it’s a rewarding experience.

He lists books and online resources by type (i.e. for developers, project managers, architects, testers, etc) and by level (essential, recommended and supplemental), and many of the items on the list are truly excellent and worth a read.

Personally, I can heartily recommend the following excellent books to any developer, designer or technically minded manager that wants to improve themselves in interesting ways (clicking on a book takes you to

Design PatternsRefactoring: Improving the Design of Existing CodePatterns of Enterprise Application ArchitecturePeopleware : Productive Projects and Teams, 2nd Ed.Beyond Software Architecture: Creating and Sustaining Winning SolutionsThe Pragmatic Programmer: From Journeyman to Master

Happy reading – it’s well worth the effort!

One thought on “Development methodologies

  1. If you can get past the absurd songs (takeoffs on
    various Beatles tunes) and the biting writing style
    (there is no mistaking the UK style humor) then
    the the content is there. Personally I feel the
    authors put considerable thought and research into
    the book.

    It probably doesn’t need to be 300 pages and really
    should have some kind of serious summary of the
    points they are trying to make…

    Personally I can forgive all this since the style
    makes a very, very dry subject entertaining. Even
    if you disagree w/ the points being made you will
    at least bust out laughing more than a few times.
    This of course assumes that you are not some kind
    of XP zealot.

    This book has clearly had a polarizing effect on the
    audience. Reviews are largely distributed between two
    extremes. This is to be expected though. You see
    the same distrubition with book on religeon, the middle
    east, etc. People obviously take the subject quite
    seriously… scary.

    You can find lots of reviews on Amazon but here is
    a link to one by Steve McConnell:

    The author’s website is here:

    “For the uninitiated, Extreme Programming (or XP) is a popular software development process that encourages a return to the days of little or no documentation, Design After First Testing, and Constant Refactoring After Programming. Despite its popularity, not everyone thinks XP is a good idea.”

    Design After First Testing – D.A.F.T
    Constant Refactoring After Programming – C.R.A.P


Comments are closed.