Sounds like there is disagreement and misunderstanding I don't claim to offer the "correct" answer, but I will define how I have been applying MVC to good effect lately.
Model -- Data only. Get methods, set methods, etc. It is isolated -- it knows nothing about the View, nor the Controller.
View -- UI only. Dumb or "humble". Only shows what you tell it to, and never performs any transformation or validation logic -- e.g., it always forwards input via an event/callback system. It is isolated - it knows nothing about the Model, nor the Controller.
Controller -- Sits between Model and View. Does any data transformation (business logic) that is necessary to get the data from the Model to the View. Does most data validation on input that comes back from the View. It "knows" about both the View and the Model.
With this definition it becomes much easier to divvy up work between engineers. If someone is a database engineer, they probably don't know UI. But they can write the Model to great effect, and hey maybe they can stub out a crappy-and-simple View. Maybe it's simply a text dump of the data, that's fine. At least the code-level interface is in place. Then the UI developers can come and write the Controller and View. Then when the UX designers change what they want the UI to look like, you can either change the View or write a new one. Or if you want to use different UI technologies -- WinForms on XP, WPF on Vista, or Cocoa on MacOS, then just have different View implementations for each. Things like skinning are then easily isolated to the View pillar.
The other useful pattern to employ here is an Inversion of Control (IoC) container/scope object. None of the classes participating in MVC need to know about the specific implementation of each other, just the interface/contract. This makes it trivial to unit test the Controller with faked out View and Model implementations. The Controller just says, "hey Create me an instance of I____View" ... and your unit test harness just happens to be providing it the Mock____View instead of the ____View that is used in production.