MVVM and division of amongst multiple developers

Can anyone speak to the ease of dividing work amongst multiple developers when designing and building a medium- to large-complexity Silverlight or WPF application? My team is finding it difficult to cleanly split work when you've got, for example, a number of controls that provide different visualizations of a Model/ViewModel that's fairly complex and has a lot of properties and methods for interacting with data. It seems like a very big portion of the work ends up being the design and build of the Model/ViewModel, and much less inside each of the controls, which are naturally开发者_如何转开发 what are easy to ration out to multiple people.

MVVM is especially well suited to this - much more suited than previous user interface options, in my experience.

The "trick" is to break up your application into composite parts. Instead of having one, single, huge Model/ViewModel, have many smaller ViewModels, each responsible for a single part of the program. You would use the same basic structure to break up the View, keeping in mind that you can always nest a view inside of another view if you use UserControls.

This allows you to assign individual Views or ViewModels to individual developers, with almost no overlap.

It sounds your ViewModel and Model classes are too complex.