This site is from a past semester! The current version will be here when the new semester starts.
CS2103/T 2020 Aug-Dec
  • Full Timeline
  • Week 1 [Mon, Aug 10th]
  • Week 2 [Fri, Aug 14th]
  • Week 3 [Fri, Aug 21st]
  • Week 4 [Fri, Aug 28th]
  • Week 5 [Fri, Sep 4th]
  • Week 6 [Fri, Sep 11th]
  • Week 7 [Fri, Sep 18th]
  • Week 8 [Fri, Oct 2nd]
  • Week 9 [Fri, Oct 9th]
  • Week 10 [Fri, Oct 16th]
  • Week 11 [Fri, Oct 23rd]
  • Week 12 [Fri, Oct 30th]
  • Week 13 [Fri, Nov 6th]
  • Textbook
  • Admin Info
  • Dashboards
  •  Individual Project (iP):
  • Individual Project Info
  • iP Upstream Repo
  • iP Showcase
  • iP Code Dashboard
  • iP Progress Dashboard

  •  Team Project (tP):
  • Team Project Info
  • Addressbook-level3
  • Team List
  • tP Code Dashboard
  • tP Progress Dashboard
  • Report Bugs
  • Forum
  • Gitter (Chat)
  • Instructors
  • Announcements
  • Files
  • Tutorial Schedule
  • Java Coding Standard
  • Git Conventions
  • Forum Activities Dashboard
  • Participation Dashboard
  • tP: ConstraintstP week 3: Kickoff


    tP: Forming Teams


    [Picture: The team that was at the top of early Google]

    When to form teams

    • CS2103T: Your team will be formed by the CS2101 side.
    • CS2103: Team forming will be done at the start of the week 3 tutorial. If you are not there at the team forming time and others in the class are unaware which team you wanted to be in, we'll have to put you into a team randomly.

    Team size

    • The default team size is five.

    Team composition

    • We allow some freedom in choosing team members, subject to these constraints:

      • All team members should be in the same tutorial. Delay forming teams until your place in a tutorial is confirmed. We do not allow changing tutorials to team up with your preferred team mates.
      • Teams of single nationality are not allowed unless the only language common among all team members is English. e.g. an all-Singaporean team that include both Chinese and Malay students. Rationale: to train you to work in multicultural teams, to ensure that English is used for all project communication
      • No more than one exchange students per team Rationale: to increase interaction between exchange students and NUS students.
      • Same gender teams are discouraged but allowed. Rationale: to train you for mixed-gender work environments.
    • If you prefer not to form teams yourselves, not to worry; we'll put you in a team.

    • We may modify teams when circumstances call for it. There is no avenue for you to object. Staying with your preferred team is not guaranteed.

    Team ID

    • To be given to you after forming teams.

    • Has the form TUTORIAL_ID-TEAM_NUMBER e.g, CS2103-W14-2 means you are in tutorial CS2103-W14 (i.e., in module CS2103, on Wednesday, at 1400-1500), team 2.

    Our tutorial IDs are different from LumiNUS. Format: CS2103T-W09 means a tutorial of CS2103T module, held on Wednesday at 0900, and so on.

    Module Venue Time Tutorial ID
    in LumiNUS

    (don't use this!)
    Our Tutorial ID
    (use this!)
    Tutors
    (contact details)
    CS2103T Wed 10:00 LG02 CS2103T-W10
    CS2103T Wed 11:00 LG03 CS2103T-W11
    CS2103T Wed 12:00 LG04 CS2103T-W12
    CS2103T Wed 13:00 LG05 CS2103T-W13
     CS2103  Wed 14:00 T01 CS2103-W14
    CS2103T Wed 15:00 LG06 CS2103T-W15
    CS2103T Wed 16:00 LG07 CS2103T-W16
    CS2103T Wed 17:00 LG08 CS2103T-W17
    CS2103T Thu 09:00 LG09 CS2103T-T09
    CS2103T Thu 10:00 LG10 CS2103T-T10
    CS2103T Thu 11:00 LG11 CS2103T-T11
    CS2103T Thu 12:00 LG12 CS2103T-T12
    CS2103T Thu 13:00 LG13 CS2103T-T13
     CS2103  Thu 14:00 T02 CS2103-T14
    CS2103T Thu 15:00 LG15 CS2103T-T15
     CS2103  Thu 16:00 T04 CS2103-T16
    CS2103T Thu 17:00 LG14 CS2103T-T17
     CS2103  Fri 09:00 T06 CS2103-F09
     CS2103  Fri 10:00 T07 CS2103-F10
    CS2103T Fri 11:00 LG16 CS2103T-F11
    CS2103T Fri 12:00 LG17 CS2103T-F12
    CS2103T Fri 13:00 LG18 CS2103T-F13

    Team Communications

    • Use English for all team communications, both spoken and written.

    • We recommend at least one 1-2 hour synchronous online project meeting per week, in addition to any asynchronous communicating. Reason: Having all members available at the same time will facilitate easier collaboration and more peer-learning.

      • Fix a weekly 1-2 hour time slot and a venue for project meetings after the team has been finalized (latest by the end of week 3 tutorial). All members are expected to attend weekly project meetings (not doing so could lower the peer evaluation ratings you receive, which in turn will be factored into your grade).
      • The best time for the weekly project meeting is the period Saturday, Sunday, Monday, Tuesday i.e., soon after the lecture but well ahead of the deadline for weekly tasks. Reason: After the lecture → you'll have the knowledge required for upcoming project tasks; before the deadline → you can use the meeting to deal with weekly project tasks.

    tP: ConstraintstP week 3: Kickoff