That is one great article ali, thanks. There's much truth in what Ward Bell is saying but truth be told MVVM is just one of many patterns. Yes, it does provide a level of complexity at first that reduces your productivity granted its not a mere View/Code Behind paradigm, but once you move away from this mentality, you'll find that it's quite simplistic to use, in fact, every single developer that i've presented MVVM to, had a shock on his face; not because it provides magic, but it "just makes sense". There are numerous implementations of the MVVM pattern, some are simplistic (MVVM Light Toolkit) and some are extreme (Prism).
The choice you need to make depends on how much of the implementation features you're going to use. I remember from the meeting that you enjoy learning new things and i honestly believe that neither me, nor scottgu nor martin fowler can preach a single pattern and enforce everyone to use it.
You've probably already seen
this, if you haven't, this is my take (in summary) on Prism and MVVM Light Toolkit.
Edit: Microsoft invested in Prism and MVVM, shouldn't we?
Edit 2: That blog post is undeniably based on frustration, I just found this incredibly funny:
In the end, I am unrepentant: I continue to practice MVVM and recommend it to others.