eg-252:gbe
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
eg-252:gbe [2008/09/30 13:53] – eechris | eg-252:gbe [2011/01/14 12:45] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Team Building Exercise ====== | ||
+ | Here is a selection of notes from the Team Building Exercise (last performed Tuesday 5th October 2010). Please feel free to expand on these as you feel fit for the benefit of your colleagues. | ||
+ | |||
+ | ===== Russell Morris' | ||
+ | |||
+ | * Implicit in Russell' | ||
+ | * He also mentioned a need to identify early the content that will be required for your group' | ||
+ | * He stated that the identification of skills was very important, but also the need for flexibility should skills identified at the start turn out to be different from those first identified. | ||
+ | * Time outside the lab is very important: remember that there is a notional 200 person hours for EG-252 and only around 80 of these will be in the lab! It is also important to be productive: three people waiting in the lab for one team member to complete a soldering task is not productive use of time. There will always be opportunities for additional testing, research, reflection or documentation during idle moments. It is acceptible to have coffee breaks. | ||
+ | * Communication is vital: ensure that each member of your team is aware of the project plan and has signed up on their tasks. Use the communication tools: instant messager, Blackboard, this wiki, blogs, etc to keep your finger on the pulse. If you are struggling -- seek help! | ||
+ | |||
+ | ===== Requirements ===== | ||
+ | |||
+ | // | ||
+ | |||
+ | Here is an initial list: | ||
+ | |||
+ | - Micromouse (MM) must follow a white line | ||
+ | - MM must avoid obstacles | ||
+ | - MM must be able to engage in combat | ||
+ | - MM must be autonomous | ||
+ | - MM must have an extra feature | ||
+ | - MM must be programmable and able to switch modes | ||
+ | - Project team must have a web site | ||
+ | - Team members may need training | ||
+ | |||
+ | Interrogate the " | ||
+ | |||
+ | |||
+ | ===== Deliverables ===== | ||
+ | |||
+ | // | ||
+ | |||
+ | (in no particular order) | ||
+ | |||
+ | * Micromouse | ||
+ | * Web site | ||
+ | * MM program | ||
+ | * Demonstration | ||
+ | * UML Diagrams | ||
+ | * Software Documentation | ||
+ | * Report | ||
+ | * User manual | ||
+ | * Tests | ||
+ | * Specifications | ||
+ | * Project plan | ||
+ | * Test results | ||
+ | * Chassis design | ||
+ | * Chassis | ||
+ | * Micro-controller assembly | ||
+ | * Sensor circuits | ||
+ | * Motor assembly | ||
+ | * Design documents | ||
+ | * Progress reports | ||
+ | |||
+ | ===== Resources ===== | ||
+ | |||
+ | |||
+ | // | ||
+ | |||
+ | Some resources identified where: | ||
+ | |||
+ | * Lab technicians and demonstrators | ||
+ | * The lecturers (particularly Dr Davies :!:) | ||
+ | * Internet/ | ||
+ | * Equipment: note limited access to lab! | ||
+ | * Components and consumables | ||
+ | * Interactive Development Environment (IDE) for software. | ||
+ | * Yourselves(!) | ||
+ | * Time | ||
+ | * Experience and skills within your team | ||
+ | * Notes from other modules. | ||
+ | |||
+ | Others previously identified: | ||
+ | |||
+ | * Computers | ||
+ | * Software: CAD/ | ||
+ | * Existing mice | ||
+ | * Web server (and existing web sites) | ||
+ | |||
+ | ===== Deadlines ===== | ||
+ | |||
+ | // | ||
+ | |||
+ | Some examples are: | ||
+ | |||
+ | * An agreed " | ||
+ | * You must have completed " | ||
+ | * The chassis design has to be submitted to mecahnical workshop before Christmas. | ||
+ | * Sensors must be prototyped before Christmas. | ||
+ | * There must be a web site of some from by beginning of second semester. | ||
+ | * All documentation must be complete and on the web site by the date of the demonstration. | ||
+ | * The mouse must be ready for inspection by the end of teaching in the summer term. | ||
+ | * There must be at least two reflective blog postings from each team member each semester. These should be relate to an aspect of the project that you have been responsible for. | ||
+ | |||
+ | There may be others! | ||
+ | |||
+ | ===== Roles and Skills ===== | ||
+ | |||
+ | Think about: | ||
+ | * What skills will you need to complete the micro-mouse? | ||
+ | * What skills you have? | ||
+ | Over the next week or so, within your groups, think about: | ||
+ | * What skills does your team actually have. | ||
+ | * If there are any gaps, how will you fill them? | ||
+ | * When will those skills be required? | ||
+ | * If you need to buy in skills –- when will they be available? | ||
+ | |||
+ | You will be required to complete and sign off on a " | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Project Planning ===== | ||
+ | |||
+ | A project plan specifies how a complex project will be broken down into tasks, the sequence of the tasks that must take place in order to complete the project, and an assignment of tasks to shared limited resources. One of the simplest and most widely understood representations of a project plan is the [[wp> | ||
+ | |||
+ | A key feature of a Gantt chart is the identification of the // | ||
+ | |||
+ | ---- | ||
+ | |||
+ | See also: [[eg-252: | ||
+ | |||
+ | [[eg-252: |