Project Deliverable 5 - Implementation

Due: There are weekly commitments and deliverables, all of which will affect your grade:

• 11/17 - plan for 11/28 deliverable due
  
• 11/28 - build & reports due
  
• 12/1 - plan for 12/5 deliverable due
  
• 12/5 - build & reports due
  
• 12/8 - plan for 12/13 deliverable due
  
• 12/13 - build & reports due
  
• 12/15 - project presentations due during regularly scheduled final exam

Grading:

• read my Programming Assignment Expectations
  • you are working as a team, not individually
  • you have already done the design work
  • the readability section definitely applies
  • as does academic honesty - if your team uses code from a source other than the team itself, make sure you document this fact clearly and give a reference
• there are no team grades - each student receives an individual grade reflecting his/her contributions
• total points = 15
  • 4 points per increment, 1 for the plan and 3 for quality of deliverable
  • 1 point for attendance and participation
  • 2 points for final presentation
    

Three projects will progress to the implementation phase. The three projects and the project teams are listed below. Attendance will be critical during these last weeks, and lack of attendance will affect your grade. A lot of class time will be devoted to this deliverable. Come to every class meeting and be on time.

Each project team will produce three incremental "releases," one per week. Be realistic. You do not have to implement the entire project. It is more important to plan each increment so that you can be successful with each deliverable.

• project manager duties
  • make sure your name is on everything you produce: plans, code, and reports
  • planning (try to complete on Tuesday)
    • organize your people into two teams of four, select one person on each team to be the team leader
    • you may reorganize these two teams at the start of each new increment if you feel it will be beneficial
    • with input from the team leaders, decide what can be implemented in one week and divide up the work
    • the team leader of each team will provide you with a detailed plan stating what the team will produce during the increment
    • produce a project plan that includes:
      • a summary of the plan and goals for the increment
      • how this increment relates to the goals for the project
      • how the integration of the work from each team will be done
      • attach the original documents produced by the two team leaders
  • technical lead
    • review work and assist team members as needed to ensure quality
    • you may take on some coding/integration/testing duties yourself as needed
  • resolve conflicts on teams (with my help if needed)
  • delivery
    • obtain current build from teams, ensure there is a readme with compile and execute instructions
    • the team leader of each team will provide you with a report on the deliverable
    • write up a report including:
      • a summary of what each team originally commited to delivering in this increment
      • a summary of what each team actually delivered (working, tested code only)
      • explanation/discussion of any differences between the two
      • discussion of management activities necessary to keep things on track
      • attach original documents produced by the two team leaders
  • important: do not be late with any turn-in - if you are unable to get everything from your team leaders, just note in the report or plan what is missing
    
    
• team leader duties
• make sure your name is on everything you produce: plans, code, and reports
• planning (try to complete on Tuesday)
  • meet with project manager to decide what part your team will work on during increment
  • with input from your team members, decide what can be implemented in one week and divide up the work
  • each team member will provide you with a detailed plan stating what he or she will produce during the increment
  • produce a team plan (give this plan to the project manager)
    • an overview of what the team will produce this increment
    • how the integration of the work from team members will be done
    • attach original plans from each team member
• technical lead
  • review work and assist team members as needed to ensure quality
  • you may take on some coding/integration/testing duties yourself
• resolve conflicts on your team (with help from project manager if needed)
• delivery
  • obtain current working, tested code from team members
  • each team member will provide you with a report on their deliverable
  • write up a report including:
    • a summary of what each team member originally commited to delivering in this increment
    • a summary of what each team member actually delivered (working, tested code only)
    • explanation/discussion of any differences between the two, including
      • any reassignment of duties that was necessary
      • any problems which required the assistance of the team leader or project manager
    • discussion of management activities necessary to keep things on track
    • attach original documents produced by the team members
  • deliver code and report to project manager
• important: do not be late getting your plan or code/report to the project manager - if you are unable to get everything from your team members, just note in the report or plan what is missing
  
  
• team member duties
  • make sure your name is on everything you produce: plans, code, and reports
  • planning (try to complete on Tuesday)
    • meet with team to decide what part of increment you will work on
    • decide what you can implement in one week, including testing
    • produce a detailed plan (give this plan to the team leader)
      • what you agree to produce during this increment
      • how/when integration of your work will occur
      • your plan for testing the code you will write
  • implementation
    • implement and test your part of the deliverable
    • get help immediately from team leader or project manager if you have a problem
    • collaborate with other team members on integration and testing
    • keep track of the number of lines of working, tested code you implemented this deliverable
    • keep track of the number of bugs you found and fixed while testing
  • delivery
    • deliver working, tested code to team leader
    • write up a report including:
      • a summary of what you originally commited to delivering in this increment
      • a summary of what you actually delivered (working, tested code only)
      • explanation/discussion of any differences between the two
      • number of working, tested lines of code delivered this increment
      • number of bugs found and fixed this increment
    • deliver code and report to your team leader
      

Turn-in Procedure:

• project managers: in WebCT, click on the Assignments icon, upload your zip file and submit

Presentations:

• presentations will be organized and delivered by the project manager and team leaders
• they will call on team members to produce and/or deliver a part of the presentation
• everyone must contribute to the presentation in some manner (not necessarily by presenting)
• each project team will turn in a one page report summizing each person's contribution to the presentation
• each project team will have a total of 35 minutes to present, including setup time on the computer