View Single Post
  #67   Spotlight this post!  
Unread 19-11-2015, 10:51
techhelpbb's Avatar
techhelpbb techhelpbb is offline
Registered User
FRC #0011 (MORT - Team 11)
Team Role: Mentor
 
Join Date: Nov 2010
Rookie Year: 1997
Location: New Jersey
Posts: 1,620
techhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond repute
Re: Mythical Six Week Build Season

Quote:
Originally Posted by MrForbes View Post
If we had a 6 week build season, and at around week 5 it was then extended to an 8 week build season, then I think the extra time would help many teams. But if we know that we have 8 weeks, we'll try to do more, and still not get it done in time.
This is an obvious concern that people will not exercise good foresight. The less you really know about the competition and the hardware the more likely this will happen.

In DevOps we fix this with a checkpoint. Show your work and tell us how you will reach the end in 2 more weeks. It serves the same purpose without replicating the robot which is cost ineffective. Perhaps teams could be required to show their work to their peers in the area. I mean we ask for documentation which, in theory, should show the plan.

The way FIRST works now is very waterfall. We give you 6 weeks. Then judge how complete you are at the hard stop at the first competition you show up to. However some teams manage to slip a little more time in by taking it out of the time they have between the 2: stop build and competition. I am pretty sure we can all tell if you have no drive train at all by the end of 6 weeks you are in trouble.

Last edited by techhelpbb : 19-11-2015 at 10:57.
Reply With Quote