🧩 Customer Feedback (Milestone Review)

1. Scenario & Feature Coverage

• Each scenario should directly demonstrate a specific feature of the system.
• Avoid presenting features outside the scope of scenarios — all features must be tied to at least one scenario.

2. Filtering & Search Functionality

• The category-based filtering feature was appreciated.
• The customer asked whether location-based searching is also supported — this functionality is currently missing and should be added.

3. Complaint and Reporting System

• A complaint/report feature should be included.
• The customer emphasized that users must be able to report issues or inappropriate content.

4. Privacy & Data Protection

• The system should not display or share personal information such as phone numbers, emails, or exact locations.

5. Volunteer Assignment & Confirmation

• When a person is assigned as a volunteer, there should be a confirmation mechanism (e.g., the volunteer must accept or confirm the assignment).
• Volunteers could also receive notifications a few days before the event/task as reminders.

6. Review & Rating Categories

• Reviews should have multiple sub-categories
• This makes evaluations more structured and informative.
• The customer suggested having two separate rating types for each user:
  • One for their requester performance
  • One for their volunteering performance

7. Visualization Improvements

• The visual representation of data and interactions was found to be insufficient.
• The customer suggested adding stronger visualization components to better communicate the system’s functionality and impact.

8. Community Domain & Inclusivity

• The customer emphasized that the platform should foster an inclusive community where everyone can contribute in different ways.
  • Example: Elderly people could contribute by sharing local history or storytelling.
• Broaden the domain of requests to include more diverse community-driven activities.

9. Documentation & Guidance

• This documentation should serve as a guide for organizing and managing community-based assistance, rather than explaining how to use the application itself.

10. Administrative Role

• Instead of using a standard “admin” role, the customer suggested a more community-oriented title, such as “muhtar” (local leader), to match the project’s spirit.

11. Global Accessibility

• The mobile app should support global locations, not just Turkey-based users.