Skip to content

report: collect and analyze student feedback for noluyoetu app #13

@Eren-Can-Donertas

Description

@Eren-Can-Donertas

1. Description

Conduct structured qualitative interviews with 5 students who have used the NoluyoETU application and collect detailed feedback on their user experience. Each participant must provide 5 favorite aspects and 5 pain points, ensuring responses are specific and non-generic. This work is critical to identify product strengths, usability issues, and improvement opportunities, and to produce a structured 5+ page report that aggregates insights into actionable findings for product development.


2. Ownership, Timeline, and Effort

Owner: @Eren-Can-Donertas
Given Date: 02-04-2026
Deadline: 08-04-2026 24:00 (end of day)
Hours: 5
Value: 1
Week: 15


3. Deliverables

  • Interview records for 5 distinct users (notes or transcripts)
  • Structured document (minimum 5 pages) including:
    • Introduction and methodology
    • Individual feedback sections for each user
    • 5 favorite points and 5 pain points per user
    • Aggregated insights and patterns
    • Actionable recommendations
  • Final report uploaded to shared drive with accessible link

Completion rule:
This issue is complete only when the final document is uploaded to a shared drive and the link is provided.


4. Scope Definition

In Scope

  • Identifying and contacting 5 NoluyoETU users
  • Conducting structured interviews
  • Collecting consistent feedback (favorites and pain points)
  • Documenting individual responses
  • Synthesizing insights across all users
  • Producing a structured 5+ page report

Out of Scope

  • UI/UX redesign or implementation
  • Quantitative analytics or large-scale surveys
  • Marketing or promotional content creation
  • Expanding beyond 5 users

5. Acceptance Criteria

  • Feedback collected from exactly 5 distinct users
  • Each user provides 5 favorite points and 5 pain points
  • Responses are specific, non-generic, and user-driven
  • Document length is at least 5 full pages
  • Each user has a clearly structured section
  • Aggregated insights section identifies common patterns
  • Recommendations are actionable and tied to findings
  • Final document is uploaded to shared drive
  • Shared drive link is accessible and complete

6. Domain Specific Notes

Business Development / Product Research context:

  • Focus on usability, value perception, and friction points
  • Ensure feedback reflects real usage scenarios
  • Avoid leading questions during interviews

Assumption:

  • Users are accessible within university/student network

7. Validation and Review Requirements

Validation:

  • Review document for completeness, structure, and clarity
  • Verify that all 5 users are represented with full responses
  • Ensure insights are derived from collected data (not assumptions)

Reviewers:

  • Project owner or product lead

Definition of Done:

  • All deliverables are completed
  • Acceptance criteria are satisfied
  • Final report is uploaded and accessible via shared drive link

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions