Browsing articles in "Getting Started in FTC"

Starting a Team “-” GreyMatter Edition

Oct 19, 2012   //   by sam   //   Getting Started in FTC, Tutorials  //  No Comments

UK robotics team GreyMatter has a great tutorial in starting a new team. Please check it out if you and “your mates” want to start a new FIRST Tech Challenge team!
http://greymatterrobotics.com/try-it-yourself/start-a-team/

What is an SVN?

Jan 28, 2012   //   by sam   //   FIRST Tech Challenge, Getting Started in FTC  //  3 Comments

RobotC Code

Our 2012 code is now open source! You can access our code at this website: http://code.google.com/p/ftc-2012-team-4466/source/browse/. If you know how to use an SVN, you can also add the repository using this link: http://ftc-2012-team-4466.googlecode.com/svn/trunk/ ftc-2012-team-4466-read-only. We will have short wiki’s writen up about the different code coming soon along with some visual tutorials on how our Omni-bot code works.

Getting a team up and running Part 2

Sep 3, 2011   //   by sam   //   Getting Started in FTC, Tutorials  //  No Comments

A continuation of the previous tutorial by our previous manager Aaron. Read Part 1 here!


Jobs

Now that you have a list of goals, everyone needs a job. Analyze the list and figure out what the different roles might be. (Basic ones are: Manager, Software Engineer, Hardware Engineer, Media correspondent, CFO – Chief Financial Officer.) It might sound like a great idea for every team member to work in all departments but from what we have seen it isn’t. It is impossible to organize tasks that way, no one will know who is doing what. Also, if people specialize in one area they learn more in-depth, resulting in a more sophisticated robot. Keep in mind that team members can have more than one job, just not every job. Editors note: we actually switch around jobs this year, so that everyone would be able to learn something new every year.

Every Department should have a group leader. The leader will divide up tasks within his team, and is responsible for making sure that the projects given to his group are completed on time. Ex. The Manager tells the Head of Software that he needs a program to make the robot cross over a bridge in the center of the field. The Head of Software can write the program, or allocate it to a member of his software team. The head of software is also responsible for making sure that the bridge-crossing program is done, whether he writes the program, or someone else does. With many jobs that focus on projects that aren’t based on the robot, like media, often there aren’t enough people for a “group.” There still should be someone in charge so that there is someone making sure those projects are done on time.

A good way to organize who does what is with a RACI chart:
R: Responsible – Makes sure the project gets done (usually group leader)
A: Accountable – Does the project (can be the “R” or can be anyone in the group)
C: Consulted – If the person working on the project needs help, they should find the “C.”
I: Informed – should know the progress of the project but doesn’t need more info, and doesn’t help.

Some models include an S for supportive – this person can provide recourses or play a supporting role in implementation.

This is the format that our team used:

R A C I
 Task1    Name     Name     Name     Name  
 Task2    Name     Name     Name     Name  

Another way that the RACI chart could be written:

  Name     Name     Name     Name  
 Task1    C   I   A   R
 Task2    A   R   C   I

Editors note: Many companies also use RACI charts, or a chart like it. Whether or not your RACI chart helps you (we hope it will) show it off!

Pages:12»
Yes, you can buy cheap seroquel