|
|
|
![]() |
|
|||||||
|
||||||||
| View Poll Results: Who makes your team's rules? | |||
| Rules? What rules? |
|
13 | 37.14% |
| Mentors make our rules. |
|
10 | 28.57% |
| Some students make our rules. |
|
8 | 22.86% |
| All the students make the rules. |
|
4 | 11.43% |
| Voters: 35. You may not vote on this poll | |||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Hi Everyone!
The veteran members on our team decided to do some team reorganization. We came up with a constitution for ourselves (the people at the meeting) and general guidelines for rules which we will use to work with the rest of the team to write our rules. I have looked at most of the white papers dealing with team organization and what struck me was the fact that it seemed that those rules were written by few for many. We believe that in order for the rules to be effective everyone needs to have a say in making them. Most of the work was inspired by The Seven Habits of Highly Effective People- http://www.amazon.com/exec/obidos/AS...092673-9327364 I recommend it for everyone to read. Here are the things we came up with. Feel free to use them. If you have any concerns or suggestions, please post them. Our team is going to meet soon and we would be very happy to use them. Leadership Constitution Our purpose is to improve and apply the knowledge of engineering as well as build strong interpersonal relationships. 1) We exercise self control 2) We do not reject ideas from the beginning 3) We never impose rules on members unless it relates to immediate safety 4) We consider everything in the problem 5) We keep everyone informed 6) If we are going to complain, we will present a solution. 7) We strive to realize the potential of all members 8) We consider all things before making promises 9) Everything that can be done before kickoff should be done before kickoff 10) We work with people to make self contracts for jobs Guidelines for Rules and Regulations Design • For an idea to be seriously considered it must be documented as accurately as possible by the person o Must find some relevant prior art o Detailed (to scale, with measurements) • Before Production o Absolute list of materials o Make exact measurements o Basic prototype for all ideas. • Unless the idea is classified a post must be made on Chief Delphi prior to second meeting Team Meetings • Designated meetings • Clear agenda o List of people who need to be present • Revision meetings every month • Work with people to make self contracts for jobs. • Every meeting was to have an agenda. • Update meetings • Do team outings • All ideas must be written down • Brainstorming meetings must be taped • Announce meetings at the end of the day Competitions • Mandatory checklist for robot (Before actual competition we go through the process) As we continue working on reorganizing our team, I will post new material. Thanks everyone! Eugene :) Last edited by Eugene : 16-08-2003 at 22:17. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| The Death of FIRST | Anton Abaya | General Forum | 23 | 03-05-2006 17:18 |
| Loss of Gracious Professionalism Among First Teams | Melissa Nute | General Forum | 82 | 31-03-2003 19:34 |
| The 2003 Index of team's post about their robot... | Ken Leung | Robot Showcase | 4 | 28-02-2003 00:18 |
| More 'Best' Robots (a well thought list) | archiver | 2000 | 2 | 23-06-2002 23:11 |
| Disqualifications | archiver | 1999 | 13 | 23-06-2002 21:53 |