This site is not ready yet! The updated version will be available soon.

Week 8 [Oct 7] - Project

iP:

  1. Evaluate two peer iPs by Saturday 2359

tP:

  1. Adjust process rigor if necessary
  2. Start proper milestone management
  3. Add another increment to your feature

iP

1 Evaluate two peer iPs by Saturday 2359

This activity is worth 2 participation points!

  1. Find out which iPs are allocated for your evaluation from the panel above.
  2. Download the JAR file of the first iP by following the link provided.
  3. Locate the User Guide of the app by following the link provided.
  4. Open the LumiNUS survey (the one named iP Peer Evaluation 1) that you will be using to submit your evaluation and take note of the things you need to evaluate.
  5. Do a light testing of the app (not more than 10 minutes) to ensure the claimed features actually exist.
    If double-clicking the jar file doesn't work, use the java -jar {file_name} command to open it.
    Make sure you are using Java 11 to run the jar file (use java -version command to confirm).
  6. Do a quick examination of the code (~ 5 minutes) by following the provided link.
  7. Submit your evaluation using the survey.
  8. Repeat the above steps for the 2nd iP allocated to you (use the survey iP Peer Evaluation 2).


tP: mid-v1.2

Reminder:

Milestone requirements are cumulative. The recommended progress for the mid-milestone is an implicit requirement for the actual milestone unless a milestone requirement overrides a mid-milestone requirement e.g., mid-milestone requires a document to be in a temp format while the actual milestone requires it to be in the proper format. Similarly, a requirement for milestone n is also an implicit requirement for milestone n+1 unless n+1 overrides the n requirement. This means if you miss some requirement at milestone n, you should try to achieve it before milestone n+1 or else it could be noted again as a 'missed requirement' at milestone n+1.

0 Ensure you know tP expectations

  • If you haven't done so already, make sure you know individual and team expectations of the tP

Relevant: [Admin tP Scope: Individual Expectations ]

Relevant: [Admin tP Scope: Team Expectations ]

1 Adjust process rigor if necessary

  • Adjust process rigor to suit your team's pace, as explained in the panel below.

Relevant: [Admin Appendix E(extract): Workflow (after v1.1) ]

You are free to adjust process rigor and project plan at any future time in the project, starting from v1.2. If you are not sure if a certain adjustment is allowed, you can check with the teaching team first.

2 Start proper milestone management

  • Set up the issue tracker as described in the panel below, if you haven't done so already.

Relevant: [Admin Appendix E(extract): Setting up the issue tracker ]

  • Start proper schedule tracking and milestone management as explained in the panel below.

Relevant: [Admin Appendix E(extract): Project schedule tracking ]

Try to achieve all milestone requirements, but do not fret if you miss a few. You will get full marks as long as you achieve about 60% of the milestone requirements on average. Yes, that's a pretty low bar, but we have set it low in order to reduce workload and stress. Ideally, you should achieve close to 80-90%.

3 Add another increment to your feature

  • Add an increment to your feature, aiming to deliver a user-visible version of your feature by v1.2 i.e., simpler than the feature intended for v1.4, but still usable by the user.

  • From v1.2 onwards each member is expected to contribute some code to each milestone, preferably each week; only merged code is considered as contributions (Reason) .
    If an enhancement is too big to complete in one milestone, try to deliver it in smaller incremental steps e.g. deliver a basic version of the enhancement first.