Project and SDLC methodologies and Agile development

This entry is a quick comment on how 'official', PMBOK-style project management is so far removed from software development using Agile methodology.
All these monolithic methodologies / frameworks - PMBOK, CMMI, etc. claim that you can tailor them to the realities and specificities of your project. This is true. But at what cost? I had an engagement where I had the luxury of spending 3 months tailoring PMBOK and CMMI frameworks before I engaged on a grueling, 15 months software development cycle. But most engagements cannot afford that. Most clients (unless they are in the government space) expect you to come to battle with your arrows already sharpened; they won't pay for you to get your act together as you go. Hence the usual demise of PMBOK and CMMI.
That's where Agile (or Agile-style processes) come into place. In Agile, everything happens as you go (or as you see a need), including creating processes. You might not get it right the first time around, but you eventually get there. The beauty of it is that you only build the processes that you need, when you need them. Team getting bogged down because you don't have a defect management process? It might be time to sit down and create one. Need a more complex process where you include a step for triage and approval of what gets fixed with priority? Better add it in the process. After a while, you're going to get to a state of equilibrium. There - you have the process and not only that, but unlike many monolithic methodology implementations, you will also have buy-in from the process stakeholders.