Open T-Wan-Lin opened 1 year ago
We did not think that list confirmed was needed considering the use case. The main purpose of the confirm/unconfirmed was to let the user chase the companies who have yet to confirm their attendance. Before the event, there would not be any need for a list confirm function since the user can simply delete the companies who are not attending, and when the event starts there should not be any companies who have yet to confirm their attendance.
Team chose [response.NotInScope
]
Reason for disagreement: The user stories in the developer guide say otherwise:
Due to the lack of time during the testing phase, I was not able to read the developer guide properly but now after due consideration, it seems even more baffling that you would omit a crucial command which has been planned for in v1.0 and v2.0. As an event planner, I do agree that a list unconfirmed
command is important for follow-up action but what about a list of confirmed attendees? I believe that such a command to essentially filter by confirmed attendance is important for an event planner to ensure that the venue size is appropriate for the number of companies attending the event. The user would have to actually manually look through the list, which contradicts your user stories.
If a user has a long list of companies, it would be very helpful to be able to list out all companies that have confirmed their attendance rather than just those that have not confirmed. This is because you have a
confirm
andunconfirm
command which gives due consideration that a company may pull out at the last minute. Being able to have the opposite oflist unconfirmed
would be very helpful, rather than having to trawl through the whole list with thelist companies
command. The omission of such a command is strange.