I like that idea a lot.

In the abstract I like the idea of starting with a release of 2 one week iterations. We can then swap before the size of the code base has gotten too large and scary and then do a longer release (maybe 2 two-week iterations). You then bend and twist the last release until it fits in the time that you have and you’re good.

The details will need some love and affection, esp. since Dagstuhl and Spring Break fall at bad times, but I bet I can figure something out.

Thanks for the help!

I think the idea of increasing the interations in a good idea, but I share you concern for the initial release and the code swaping.

What about variring the size of the interations in each release?

Release One: 2 or 3 one week interations
Release Two: 2 two-week iterations.
Release Three: 1 two-week interation or 2 week and a half interations (if you go with 2 iterations for the first release.)

Just a thought, I had to sketch a calendar to get it all to work out. You could rotate it to have the long interations first the shorter last and vice versa. I don’t remember if the student are better of with more time to figure thing out in the beginning or at the end when they want to do more fancy stuff. But that is why they pay you the big bucks!

Have a good day,

Dan

P.S. My blog has moved to my home page: http://www.danflies.com/