Quote:
Originally Posted by Chris Hibner
I don't understand this. If FIRST dropped the 6 week build limit, there would be no one from FIRST HQ holding a gun to your head to work beyond 6 weeks. Why not just organize your team to stick to a 6 week season?
For teams that want a practice robot but are already stretched too thin, eliminating the 6 week limit lets them practice.
For teams that already build a practice bot, eliminating the 6 week limit is a large relief from burnout from having to build 2 robots within 6 weeks.
For teams that have no interest, feel free to impose a 6 week limit to save your team from themselves.
|
Project schedules always grow to fill the maximum allotted time. There's a theorem or law or something in the software world that more elegantly states it.
If even 1 or 2 people on the 'team' isn't on board with arbitrarily cutting a build season down from an 'unlimited' amount of time, then they can easily convince the rest of the team that their view is better when the end of the arbitrary deadline hits. This is especially true if they're someone with a critical system that isn't finished.