Quote:
|
Originally Posted by KenWittlief
you are off to a good start. What you are really trying to do is impose requirements on your design team.
|
Thanks for your comments. I am, in fact, trying to set up a strategic direction for our team that includes the following:
Vision
Mission
Principles of Teamwork
Engineering Principles
These will inform the next step which includes (this is NOT all-inclusive):
Team roles
Design and build goals
Competition goals
Design methodology
Build methodology
Testing/training methodology
Other competitions (web, animation, CAD) methodology
Tournament methodology
Measurement and planning cycle
It may sound imposing, but I hope to scale all of these to the task at hand. At work, I deal with multi-zillion dollar products and large teams of professionals. The FIRST methodology we develop will, I hope, expose the students all these things to get a flavor of how structure can help, while limiting its sheer volume so that they don't have to spend all their time doing administration.
I really take to heart your comments on measurement. The "Engineering Principles" list is both too low-level and too high-level at the same time. I'm still noodling on how to scope this and I appreciate everyone's input. (KISS is important, tux, thanks for the reminder.)