Roadmap

This roadmap summarizes the current product direction. The detailed Product Backlog is maintained in GitHub Issues and GitHub Project views.

Current Sprint - Assignment 5 / MVP v2

Sprint Goal

Prepare MVP v2 repository evidence by documenting the architecture and development process, extending recognition-score correctness tests, preserving Assignment 4 quality gates, and creating truthful Week 5 delivery materials with public evidence separated from private recording/access material. The July 4 Sprint Review validated the demonstrated MVP v2 behavior and left Raspberry Pi stability, recognition quality/performance, and fake/spoofing handling as the next product improvement focus.

Selected Sprint PBIs

PBI Expected outcome SP Implementer Reviewer Current status
#17 - US-05: Monitor service status Operator can see backend/server API, edge device/agent, camera, and recognition status from backend health and heartbeat-derived data. 3 privel Sparta2016840 Delivered and closed through reviewed MVP v2 scope.
#59 - PBI-A5-ARCH Maintained architecture package with diagrams and ADRs. 5 Sparta2016840 rmxqwo Reviewed, merged, and closed.
#60 - PBI-A5-PROC Maintained development process and configuration management document. 3 Sparta2016840 etherealboop Reviewed, merged, and closed.
#61 - PBI-A5-QA Recognition-score semantics tests and updated quality/UAT docs. 3 Sparta2016840 privel Reviewed, merged, customer-UAT verified, and closed.
#62 - PBI-A5-DELIVERY Week 5 public report, hosted docs setup, release/deployment evidence plan. 5 Sparta2016840 rmxqwo Reviewed, merged, Sprint Review evidence added, and closed.
#35 - BUG-01: Recognition agent requires restart after authorized-person changes Authorized-person data changes should become effective without manual agent restart. 5 privel Sparta2016840 Closed for the reviewed MVP v2 model-management scope.
#58 - BUG-02: Recognition confidence is displayed in reverse Recognition score display uses raw LBPH distance semantics where lower is better. 3 privel Sparta2016840 Reviewed, merged, customer-UAT verified, and closed.

MVP v2 Evidence Status

  • Hosted documentation is published: FaceGuard documentation.
  • MVP v2 release is published: v2.0.0.
  • Relevant protected-main Quality Gates and GitHub Pages evidence is captured in Week 5 screenshots.
  • Sprint milestone and GitHub Project board evidence is captured in Week 5 screenshots.
  • Public sanitized demo video is published: Two-minute demo video.
  • Preserve the completed July 4 customer UAT and Sprint Review evidence.
  • System service-status evidence is captured in Week 5 screenshots.
  • Remaining evidence gate: Moodle private evidence package.

Previous Sprint - Assignment 4

Sprint Goal

Improve the FaceGuard administrator experience by completing access-log review, making person removal safer, adding clear Dashboard refresh feedback, and introducing automated quality requirements, tests, coverage enforcement, and CI quality gates.

Selected Sprint PBIs

PBI Expected outcome SP Implementer Reviewer Current status Linked PR Merge status
#21 - US-09: Review access-attempt events Administrators can review access attempts with timestamp, result, person or Unknown, device/location, date and status filtering, newest-first ordering, and 25 item pagination. 3 etherealboop rmxqwo Delivered PR #50 Merged to main on June 28, 2026.
#22 - US-10: Edit or remove authorized people Administrators can edit person details and safely remove a person with typed DELETE confirmation and immediate list feedback. 3 rmxqwo etherealboop Delivered PR #51 Merged to main on June 28, 2026.
#47 - PBI-A4-16: Add manual Dashboard refresh and last-updated feedback Dashboard has a compact manual refresh action, refresh loading feedback, and a readable last-updated time without reloading the page. 1 privel Sparta2016840 Delivered PR #52 Merged to main on June 28, 2026.
#48 - PBI-A4-QA: Define and automate FaceGuard quality gates FaceGuard has measurable quality requirements, automated QRTs, backend unit and integration tests, critical-module coverage gates, and CI quality jobs. 3 Sparta2016840 privel Delivered PR #49 Merged to main on June 28, 2026.

Current Sprint Status

  • Selected scope total: 10 Story Points.
  • Delivered to main: #21, #22, #47, and #48, 10 Story Points.
  • In Review or Pending Merge: none in the selected Sprint scope at the time of this update.
  • Customer review: completed on June 28, 2026.
  • UAT: demonstrated during the customer review and confirmed by the customer in follow-up written feedback.
  • Assignment 4 release: v1.1.0 is published.
  • Deployment: available at http://10.93.26.183:5173/ on the Innopolis University private network.
  • Protected-main CI: quality gates run passed after a push to main.
  • Protected-main evidence includes the Quality requirement tests job, Backend tests and critical coverage job, and Docker Compose validation job.
  • Customer confirmation: Week 4 report evidence records the customer message approving all user stories.

Successful PR CI is tracked separately from protected-main CI evidence. The selected scope is merged, released, and confirmed by the customer.

Next Sprint

Likely follow-up scope after Assignment 4:

  • Raspberry Pi integration and hardware-oriented deployment work.
  • Anti-spoofing research and implementation.
  • Broader authentication and role-authorisation testing.
  • Real PostgreSQL integration tests for database-dependent backend paths.
  • Frontend component tests for Dashboard, Access Logs, and People flows.
  • Production-like performance verification outside FastAPI TestClient.
  • Camera and recognition quality testing with representative hardware.
  • Further CI and security hardening, including dependency auditing and stricter branch protection evidence.

Quality and Automation Continuation

The Assignment 4 quality requirements, QRTs, coverage threshold, and CI jobs are maintained project assets. They should be extended when new critical modules are added, when user-facing workflows become more mature, or when the team starts testing with real PostgreSQL, camera hardware, and production-like network paths.

Risks and Decision Gates

  • Branch protection evidence currently proves only the visible active ruleset applied to main, pull request before merge, one required approval, conversation resolution, and restricted branch deletion.
  • Customer Review was completed on June 28, 2026, and follow-up written confirmation approved the checked user stories.