6
Vote

Create 2 development teams

description

UX and Back-end

Set up a solution architecture, so the two teams can work seperately (with MEF and MVVM perhaps?)

comments

CKurt wrote Jul 5, 2010 at 2:40 PM

I'm pro ! I'm condidate for the Back-End team. However I don't have any MVVM experience. A split seems oppertune.

MatthijsKrempel wrote Jul 5, 2010 at 4:34 PM

If you guys want, I can set-up a skeleton architecture with MVVM and MEF

As soon as I understand what needs to be in there,..

Backend doesnt need to have MVVM expierence :) They just write "services" the front-end guys consume,..

BasP wrote Jul 5, 2010 at 8:04 PM

I'm keen on seeing an MVVM project develop (and participating in it). What would be the advantages of MEF and MVVM over other paradigms for this specific case?

rd3d2 wrote Jul 5, 2010 at 8:46 PM

I've ebeen hearing a lot of good things about Laurence Bugnion's MVVM Light for WP7 development (http://chriskoenig.net/2010/07/05/mvvm-light-messaging/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+ChrisKoenig+%28Chris+Koenig+-+Microsoft+Developer+Evangelist%29&utm_content=Twitter) . Was thinking of using it for my next WP7 project.

Worth a look anyway.

rd3d2 wrote Jul 5, 2010 at 9:21 PM

I think maybe three teams - back end,UI and a third team whos job it is to annoy Clint & Paulo (I can head that one up myself)

MatthijsKrempel wrote Jul 6, 2010 at 6:30 AM

@BasP

MVVM will easy development for the UX team, because it forces them to do the UI a certain way

MEF wil bridge back-end and front end. Basically, we can create mocks for C9 en Live services, so it wont stop UX development. And when back-end team is done, replace mocks with the real stuff.

MatthijsKrempel wrote Jul 6, 2010 at 6:31 AM

I ment, ease

Spivonious wrote Jul 6, 2010 at 1:33 PM

MVVM is nice for unit testing, but I find it adds a lot of time to the coding (and a lot of duplicate code).

crutkas wrote Jul 8, 2010 at 1:08 AM

Should create a wiki page for dev team breakdown