Group 1
CS 4970/5973
March 6, 2003

Project 2 – Team Organization and Task Allocation Proposal


Team Structure
For the first project, we had divided responsibilities into three positions; a documentation, software, and hardware.  On the whole, we found our team this to be a very satisfactory and efficient plan for us.  However, we have a new team member to integrate into our structure this time around.  Instead of redesigning our organization from the ground up, we have decided to maintain the same basic structure this time around, adding a second software position to accommodate a fourth team member.

Task Allocation
Much like as we did for the first project, task allocation was relatively simple.  Team members with special needs or arguments made cases during a team meeting for taking a specific position, and others took what was left.

Software 
Tim will be the senior software developer for this project, with Manohar acting as junior developer.  Tim has had much experience with IC in the past, and Manohar was the sole developer for project 1, so this should work out well.  Tim wanted to work on software on earlier projects, rather than later, so this works out to be a good time for him.  Manohar was the last to be placed in a position for this project.  
It is very likely that should no further changes be made to the team structure, the senior developer for each project goes on to be the junior developer for the next.  This will leave the senior member of future projects spearheading the development, provide more chances to learn, with the advice of a junior member who has worked on IC before.  Senior and Junior here would only denote who has final say.  

Hardware 
Romain will develop the hardware for this project.  The current idea is to work from the previous base, but we will see how this works.  He will build the prototype based of the ideas and direction the team comes up with in design meetings.  He and Tim will be here over spring break, and it made sense to have a hardware and software representative around for spring break work.

Documentation 
Adam will prepare all the required documentation; this document, the Timeline and Milestone report, the final report, and prepare the presentation for the class.  As with the first project, short reports from the software and hardware developers will be integrated to create a final report.  Elements of this report will then be used to create a final presentation.  Adam’s schedule for the next two weeks is messy, so he volunteered for this position.

Team
As before, the team will work together for the final testing.  This worked out well for the last project, and we anticipate that it will remain a good plan.  We expect that any plans we have for “crunch time” will be thrown away anyway.  Our members that will be unavailable through spring break especially will be prepared for extensive testing when they return.