BTP300B A2 Teams Fall 2013

From CDOT Wiki
Revision as of 18:59, 6 October 2013 by Peter.liu (talk | contribs)
Jump to: navigation, search

Notes

  • Designate a team leader and post up a brief description of responsibilities for each team member.
    • The team leader is in charge of merging a branch with the trunk. Merging should be allowed only after the team members have tested their own code!
    • Each team member must keep a log of testing that has been done at the branch level. The log should indicate what tests have been done on the code and the dates of testing. Also, at least ONE testing program should be put in each branch. (Note: The testing requirements will affect the final grade of your assignment.)
  • Your team should keep the Weekly Bugs Report updated.
  • The team members should communicate with each other regularly.
  • Each team member must submit a brief report when an assignment is due. The report consists of peer evaluation, team work experiences, and programming experiences. On a scale of 0 (lowest) - 5 (highest), you should assign a score to your team member and yourself.
  • Please contact your professor ASAP if you have team work issues.

BTP300B - List of Team Members (3-4 students) for A2
Team Number Team Members Plan For Team Work Weekly Accomplishments/Bug Reports Completed

1

Dennis Villasenor
Huda. R
Shianne Lee
Work Plan Accomplishments and Bug Reports

No

2

Member 1 (Team Leader)
Member 2
Member 3
Work Plan Accomplishments and Bug Reports

No

3

Alek Minassian (Team Leader)
Anson Tan
Justin Flowers
Work Plan Accomplishments and Bug Reports

No

4

Member 1 (Team Leader)
Member 2
Member 3
Work Plan Accomplishments and Bug Reports

No