It depends entirely on where you are. Some projects are a completely chaotic mess, of course. Some have a methodology, perhaps cobbled from bits and pieces of c

It depends entirely on where you are. Some projects are a completely chaotic mess, of course. Some have a methodology, perhaps cobbled from bits and pieces of conventional wisdom, but they don't give it a name. Some explicitly declare a methodology and pay attention to its rules, more or less. Some, alas, become religious devotees of a methodology, train a police force to enforce the rules, and go into full blown cargo cult mode. But all real-world instantiations of methodologies are, in some sense, "amalgamations". For one thing, none of them are complete. As both the article and Raganwald point out, Scrum is far from a complete description of what you need to do to organize a successful project, just as using Lisp and Emacs aren't sufficient conditions for producing great software.