search

VisnuRavi / pe

0 stars 0 forks source link

Use of Backlog and Todo #2

Open VisnuRavi opened 3 years ago

VisnuRavi commented 3 years ago

It feels like back log and todo seems like very similar categories, and they seem to achieve the same thing. As such, I feel that there is no need to have a distinction between the two, as it does not solve any additional issues for the student.

nus-pe-bot commented 3 years ago

Team's Response

A duplicate of #2475

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Difference between BackLog and Todo

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

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.

image.png

[original: nus-cs2103-AY2021S2/pe-interim#2475] [original labels: severity.High type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

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 duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: This is different from the other bug, as that is asking the users 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. This bug is about why there is BackLog and a Todo, instead of just 1.

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: The explanation given for todo and backlog still seem very similar. I do not see why there needs to be a difference, especially when there is an in progress section to distinguish the tasks that are currently being done.

:question: Issue type

Team chose [type.DocumentationBug] Originally [type.FeatureFlaw]

Reason for disagreement: This is a feature flaw as the backlog section is not very useful to the target user during normal usage, especially so when the find command can easily find the various tasks.

:question: Issue severity

Team chose [severity.Low] Originally [severity.High]

Reason for disagreement: Perhaps a change to medium would be more appropriate, as many users could experience the confusion to decide on putting their tasks in todo or backlog and be inconvenienced.