Feature description
We need to finish report for week 2, link to the google dock: https://docs.google.com/document/d/15mekgcLT8IRX_yB-M2dwLVT6pvJSvUETzAC_Ry9n_N8/edit?tab=t.0
Link to the course portal:
https://capstone2026.innopolis.university
What is needed to be done
Team name, members, and assigned roles.
Chosen project, chosen track, problem statement, and point-by-point justification against the track's acceptance criteria.
clear described plan for the next week
Project plan (week-by-week roadmap, milestones, risks) and link to the prioritized backlog (Kanban board).
Requirements artifacts:
List of user stories with acceptance criteria and the defined MVP scope.
Frontend Developers : Links to merged Pull Requests (PRs) or closed issues. Screenshots/GIFs of new UI components or functionality.
Designers : Wireframes/mockups, user flow diagrams (.fig files, screenshots).
Backend Developers : Links to merged PRs or closed issues. Links to updated API documentation (e.g., Swagger/OpenAPI).
Project Managers : Links to created/assigned issues, updated Kanban board (e.g., Trello, Jira, GitHub Projects), summary of customer/TA feedback and action items.
ML : Links to source code (e.g., specific commits/PRs), model artifacts (e.g., Hugging Face model page, .pkl files in your codebase)
Chosen tech stack with justification.
Description of implemented MVP features and the functional user journey(s), with screenshots/GIFs.
Links to relevant PRs/Issues for skeleton and implemented features, and link to API documentation.
Notes from internal demo and identified next steps.
Submit a video demonstrating the current state of the project — a short walkthrough or demo of what is working at the end of that week.
Acceptance Criteria
Feature description
We need to finish report for week 2, link to the google dock: https://docs.google.com/document/d/15mekgcLT8IRX_yB-M2dwLVT6pvJSvUETzAC_Ry9n_N8/edit?tab=t.0
Link to the course portal:
https://capstone2026.innopolis.university
What is needed to be done
Acceptance Criteria