[kramarczyk]

Loose the fix-it window definition.

In industry I am not familiar with any kind of "tools down" period during product development, so why are we doing it here? FIRST has already got a finite constraint on time between kick-off and the comps, so why create a sub constraint? I don't think that success on the field is related to number of hours worked. In fact, I suspect that consistently successful teams probably work fewer, higher quality hours. Limiting work hours probably only hurts the teams that are still working out the bugs in their process.