Requirements Changes

[jbrucker]

There are 3 changes or clarifications to requirements
that result from email and conversation with customer.
Each one is detailed in a file. They are:

1. should voters be required to enter a code or verification that they viewed contestant's work before
   entering an evaluation?
   Requirements-Change-1
2. should system allow voters to not vote for some items?
   Requirements-Change-2
3. should system allow voter to modify vote after he submits it?
   Requirements-Change-3

Since this in the middle of an iteration, you should not change your design or work now based
on these updates. Wait until next iteration planning. I don't think any of the changes will cause
any serious rework.

[whs]

On the 3rd change, TeamGG's application doesn't have a "voting form" system that user go to and enter score for every groups similar to Google Docs. The rationale is that user might want to view the group's details before voting and have to leave the form incomplete especially on mobile.

Our system works similar to Play Store. Voter visit every project's page and rate it one by one (if voting is open). They don't need to lock to their final decision.

So, should I create a vote lock-in system or I can make my own call on this requirement?