Mid phase B peer evaluations are now open on TEAMMATES (there'll be another one at the end of phase B). You should have received the submission link by now. Note that peer evaluation submission is compulsory and missing them can count against your participation marks. Email me if you didn't receive the submission link. As usual, there will be no deadline extensions.
In spite of the increase in requirements and strictness of checking from v1.1 to v1.2, it's good to note a slight increase in the percentage who met individual and team deliverables (81% and 68%, respectively). Let's keep that trend going in v1.3. If you team is failing to meet team deliverables, it's time for you to take charge and steer the team towards team deliverables instead of totally focusing on individual deliverables.
Related to the above point, v1.3 requires you to run the product from a jar file. Unexpected errors can happen when you do that. Use the technique of schedule buffers to safeguard against such unexpected problems.
Good to see a flurry of posts offering features for reuse. Let's keep that going too. If someone offered a feature for reuse but you have already implemented a similar feature on your own, you can post in the same thread to offer yours as an alternative. That gives everyone a rare opportunity to compare alternative implementations and decide which to adopt.
Mid phase B peer evaluations are now open on TEAMMATES (there'll be another one at the end of phase B). You should have received the submission link by now. Note that peer evaluation submission is compulsory and missing them can count against your participation marks. Email me if you didn't receive the submission link. As usual, there will be no deadline extensions.
In spite of the increase in requirements and strictness of checking from v1.1 to v1.2, it's good to note a slight increase in the percentage who met individual and team deliverables (81% and 68%, respectively). Let's keep that trend going in v1.3. If you team is failing to meet team deliverables, it's time for you to take charge and steer the team towards team deliverables instead of totally focusing on individual deliverables.
Related to the above point, v1.3 requires you to run the product from a jar file. Unexpected errors can happen when you do that. Use the technique of schedule buffers to safeguard against such unexpected problems.
Good to see a flurry of posts offering features for reuse. Let's keep that going too. If someone offered a feature for reuse but you have already implemented a similar feature on your own, you can post in the same thread to offer yours as an alternative. That gives everyone a rare opportunity to compare alternative implementations and decide which to adopt.