soc-se-bot
commented
9 months ago Team's Response
Thanks for the suggestion. However, we feel that this is not in scope for v1.4. The current product is perfectly usable for event planners.
Like you mentioned, if one wishes to add deadlines, they can write it in the task note.
While handling deadlines as a new entity would be a good addition, we do not feel that it is necessary for the current iteration of our product.
We already have a long list of commands (27 in CoordiMate vs 8 in AB3) in v1.4, and many new entities that will benefit event planners. Not having deadlines does not disrupt an event planner’s ability to use the application.
Hence, we believe that deadlines are not a priority, and more of a good-to-have. Developer effort was hence focused on the other areas of the application.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: Thanks for the response and explanation! I understand and commend the fact that your app has an extensive list of commands that will help event planners (eg. marking tasks, deleting all marked tasks)
However, I feel that as your product specifies its target users as event planners, it would only be expected that they would have a few events to plan for, and deadlines to meet for each event as well (eg. Date to settle logistics, sponsorships, date to publicise and prepare event plans).
I would argue that if the target users were students/people that would use to do lists, then this product is perfectly fine, as to do lists can make do without deadlines. However, i'd disagree with the point that event planners would not be disrupted when they use this application.
They would have to take an extra step to put in the deadline in the notes section (which only displays 1 note at any time, and would result in less flexibility and of putting notes relevant to the task/event itself besides the date, and also reduces readability as the date would now take up space in the notes section rather than a dedicated space for dates).
In the very least, I would say that this is a low severity bug (or higher). Deadlines would be of utmost importance to an event planner in my opinion, as they would have a lot of things to juggle and settle to ensure that the event is properly organised. Should they use this app and miss a deadline (as there is no date feature), it would not be good for them. Hence, I do strongly feel that this feature is incomplete.
As students, I think we will have a lot of tasks and events to keep track of, and it would be important that we also have a date/deadline field for tasks, rather than having to put it under notes. I think that this feature is quite essential, as tasks are not sorted in any order, only the order that you add them in. I feel that the addTask feature is incomplete in this sense.