From a few people I know who are Scrum trainers and such, who've actually had input on the PMBOK, say the classic waterfall is dead for software for the most part. They also weren't a fan of PMBOKs reference of agile and scrum for what it's worth. I guess it's an academic thing to disagree with things but these guys think the PMP methodology is now a cash grab because very few industries adhere to such rigidity. I remember studying for PMP 8 years ago, and while it was enlightening at the time, I ultimately found Scrum to be a better framework for the modern work environment, so I didn't end up taking the PMP exam (right or wrong). Scrum is a little more idealistic though, in that it doesn't prescribe word for word what should be done, which leaves room for organizational paradoxes that you really have to think what the best way to do things given your organizations constraints on sharing resources at the right time. I don't work in a scrum environment day to day, though I was certified about 2 years ago and think it's worthwhile from a knowledge perspective to have a formal way of guiding yourself (like any methodology).
|