TΣAM M1NDSTӨЯMΣЯZ Aaron Doades, Bryce Brown, Corey Richmond, John Witting.

TΣAM M1NDSTӨЯMΣЯZ

Aaron Doades, Bryce Brown, Corey Richmond, John Witting

Introduction

•Problem

•Overview

•Process

•Lessons

•Conclusions

•PDS for Future ECE-361 Classes

Problem

• Design Robot to complete 3 events as described in PDS

• Teamwork – Getting to know teammates– Trusting other members work/decisions– Being responsible for group members actions– Communication

Overview

Preliminary Design:Final Design:

Process

• Team Documents– Agendas– Minutes

• Communication

• Brainstorming– Original Ideas Carried Through to the End

• Verification / Testing– Test, Tweak, Retest

Lessons

• Good Decisions– Chassis

• Bad Decisions– Splitting up the work– Software not a subsystem

Conclusions

• Overall: Success!

• Team methods: Useful for the most part– Brainstorming: Incredibly useful– Agendas: Maybe not as useful

• Design: OK, could have been better

• Competition: Beaten by the board…

• Final Presentation: Excellent!

Suggestion for Future Projects

• Block Stacking (ordered?)– Color Coded blocks?

• Ball Gathering– Gather balls from one side of board– Place in a central location

• Battle Blocks?– Definitely would be fun to watch…