nus-pe-bot
commented
3 years ago Team's Response
Having a backlog, todo, in progress and done is in line with Agile kanban boards, such as Jira.
The backlog serves as a longer term todo list where it's not currently about to be worked on in the near future, but are still tasks that require the user's attention to complete eventually but do not want to lose track of exactly what is left over.
The todo serves as a short term todo list where the user is actively working through the list to ensure they are able to complete all of their tasks.
Additionally, this is in the glossary of the developer's guide, so we are just explaining the terms to developers, while if a developer wants a better understanding of agile methodologies of project management, it is expected that they should do reading up outside of our developer's guide.
According to CS2103T guidelines on bugs in the DG:
Problems in Glossary. Examples:
- Unnecessary terms included
- Important terms missing
This belongs to neither of those.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: UG needs to explain the difference between BackLog and Todo clearly, instead of leaving it unclear and up to the user, which does not make this app very specific to its target users.
:question: Issue severity
Team chose [severity.Low]
Originally [severity.High]
- [x] I disagree
Reason for disagreement: A medium is more appropriate as all users need to know this before using the app, which can cause inconvenience to the users when using the app.
The difference between BackLog and Todo does not seem clear as a user reading the DG, or UG. Perhaps more explanation would be better. If there is not too much difference, can consider removing one of the 2 categories.