CS2103/T Website - Admin: tP: mid-v1.2 [week 8]

Ensure you know tP expectations
Adjust process rigor if necessary
Start proper milestone management
Add another increment to your feature

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.

1 Ensure you know tP expectations

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

2 Adjust process rigor if necessary

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

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.

3 Start proper milestone management

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

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

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%.

4 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 the amount of code does not matter; even small contributions are acceptablesome code to each v1.3, v1.4 milestone, preferably each week; only merged code is considered as contributions The ability to deliver code incrementally is an important learning outcome of this module because incremental delivery, among other things, improves the visibility of your work.(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.