Unclear target audience in UG and DG

[guanquann]

As a person who has just started using this app, I am not sure who your target audience is, as it is not mentioned anywhere in your user guide. It is until when I'm reading the User Stories section in the DG then I realised that the target audience is maybe for students/student leader?

I think it would be much clearer if at the start of UG, you state who your target audience would be.

For example, instead of saying Tailored for individuals with fast typing speeds who prefer keyboard-centric navigation to mouse-driven interfaces, TeamTracker is the ideal solution for anyone looking to enhance their task management workflow.,

you could say Tailored for **YOUR TARGET AUDIENCE** with fast typing speeds who prefer keyboard-centric navigation to mouse-driven interfaces, TeamTracker is the ideal solution for anyone looking to enhance their task management workflow.

[soc-pe-bot]

Team's Response

No details provided by team.

The 'Original' Bug

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

Target audience in user stories

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.

---

In user stories, it shows multiple stories for students, however, its shown in the value proposition that its for leaders to use to manage tasks for the students as shown below. Thus, It is a bit confusing as to who the target audience really is

---

_{[original: nus-cs2103-AY2324S2/pe-interim#1197] [original labels: severity.Low type.DocumentationBug]}

Their Response to the 'Original' Bug

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

In our value proposition, we did mention that the app helps manage individual and group tasks. Therefore, our target audience consists of students and group leaders. We believe this issue only comes from the value proposition not specifying the target audience clear enough, so the user stories is actually fine. We believe this issue is Severity.VeryLow as it only affects the understanding in the value proposition alone, not affecting the user stories.

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)

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** VeryLow severity should only be used for cosmetic issue. 

---