Skip to content

Roadmap

Sprint-by-Sprint delivery plan. For story-level detail, current status, and acceptance criteria, see the issue tracker and docs/user-stories.md — this file only summarizes intent and links out.

Sprint 1 — Core recommendation happy path

  • Milestone: Sprint 1
  • Dates: 2026-06-15 – 2026-06-21
  • Sprint Goal: Deliver the core recommendation happy path — a guided questionnaire (budget, ethical preferences, allergen exclusion, skin concerns) producing a structured cosmetic bag of real products with per-item justification, deployed and ready for customer review. This is the MVP v1 increment.
  • Focus: Ship the /recommend backend end-to-end, then build the questionnaire and results frontend on top of it.
  • Planned items:
  • User stories: US-02, US-03, US-04, US-05, US-06, US-07, US-08, US-17
  • Backend: PBI-101, PBI-102, PBI-103, PBI-104
  • Frontend: PBI-107 (decomposed into PBI-110–PBI-117), PBI-108, PBI-116
  • Docs & process: PBI-105, PBI-106, PBI-109

Sprint 2 — Polish the MVP, personalize by skin type, raise quality and automation

  • Milestone: Sprint 2
  • Dates: 2026-06-22 – 2026-06-28 (Mon–Sun)
  • Sprint Goal: Polish the MVP for real customer use: apply the customer's requested design and copy changes on the frontend, add automated tests for the product-recommendation (matching) logic and fix any defects they surface, and extend the recommendation engine with skin type as a new filtering criterion (database markup, questionnaire step, and matching logic).
  • Focus: Customer-feedback-driven design/copy fixes, skin-type personalization, a short non-storytelling questionnaire variant, automated testing of the recommendation engine, and the Assignment 4 quality/automation baseline (Quality Requirements, QRTs, CI gates, Definition of Done, testing and UAT docs).
  • Planned items:
  • User stories: US-01 (landing page), US-09 (skin type), US-18 (short questionnaire variant)
  • Skin type: PBI-201, PBI-202
  • Design/frontend: PBI-203, PBI-204, PBI-205
  • Testing and quality automation: PBI-206, PBI-207, PBI-208, PBI-209, PBI-210, PBI-211, PBI-212

Sprint 3 — MVP v2: more accurate, more personal, better explained

  • Milestone: Sprint 3
  • Dates: 2026-06-29 – 2026-07-05 (Mon–Sun)
  • Sprint Goal: Make the budget expectation honest — present budget as a tier with an approximate total instead of promising an exact ₽ range; let users who don't know their skin type get a personalized result through a short skin-type mini-quiz; integrate LLM-generated justifications for the recommended products; and apply the customer's design and copy feedback. In parallel, document the product architecture (static/dynamic/deployment views and ADRs) and the development process.
  • Focus: Customer-feedback-driven product improvements (budget precision, design/copy), the skin-type mini-quiz, LLM justifications (justification-only — model and prompt provided by the customer), and the Assignment 5 maintained documentation (architecture, ADRs, development process, hosted docs).
  • Delivered increment: MVP v2, mapped to release v1.2.0.
  • Planned items:
  • User stories: US-19 (skin-type mini-quiz), US-14 (LLM justification), US-20 (special-condition safety)
  • Product: PBI-301 (mini-quiz), PBI-302 (budget precision), PBI-303 (LLM justifications), PBI-304 (design/copy polish), PBI-312 (special-condition filter)
  • Architecture & process: PBI-305–PBI-308 (static/dynamic/deployment views, ADRs), PBI-309 (development process), PBI-310 (hosted docs), PBI-311 (tests, UATs, Definition of Done)

Sprint 4 — Personal account: sign-in, profile, saved bag, feedback, replacement and tracker (Week 6 trial)

  • Milestone: Sprint 4
  • Dates: 2026-07-06 – 2026-07-12 (Mon–Sun)
  • Sprint Goal: Turn Koyash from an anonymous one-shot tool into a personal service, per the approved account specification. Users can register and sign in (email + password; phone collected but not used for auth), while the questionnaire → cosmetic-bag flow stays fully available to guests. Signed-in users get a personal account: a profile card, one saved cosmetic bag with "Подошло / Не подошло" feedback, replacement of unsuitable products with similar alternatives, a result tracker, and account management (edit profile, change password, delete account). In parallel, publish the customer-facing documentation set and cut the Week 6 trial release v1.3.0.
  • Focus: Guest-first authentication and the personal account (profile, single saved bag, feedback, product replacement, result tracker, profile & security), the Assignment 6 customer-facing docs (README entry point, CONTRIBUTING.md, AGENTS.md, docs/customer-handover.md), ADR-004 for authentication, and a stable trial release. Priorities P0/P1 in the issue bodies protect the trial core if some P1 work slips into Week 7.
  • Delivered increment: the personal-account layer, released as v1.3.0 — the Week 6 trial / handover-candidate release. Customer trial and documentation review completed at the Week 6 meeting; handover level reached: Ready for independent use.
  • Planned items:
  • User stories: US-21 (account + sign-in), US-22 (profile card), US-12 (single saved bag), US-13 (feedback), US-24 (result tracker), US-25 (product replacement), US-26 (account & security)
  • Product: PBI-401–PBI-407 (auth, profile, single bag, feedback), PBI-414/PBI-415 (replacement), PBI-416/PBI-417 (tracker), PBI-418/PBI-419 (profile & security)
  • Architecture, quality & docs: PBI-408 (ADR-004 + config), PBI-409 (tests), PBI-410 (README), PBI-411 (CONTRIBUTING/AGENTS), PBI-412 (customer-handover), PBI-413 (trial release v1.3.0)

Sprint 5 — Trial feedback and final transition (Week 7, MVP v3)

  • Milestone: Sprint 5
  • Dates: 2026-07-13 – 2026-07-19 (Mon–Sun)
  • Sprint Goal: Respond to the Week 6 trial feedback and complete the transition — ship the deterministic irritant warning for sensitive-skin users (US-11), self-service password reset via the customer's mail domain (US-27), and the remaining frontend UX fixes; then deliver the final MVP v3 release, confirm the transition with the customer, and produce the Week 7 evidence (public demo video, UAT, Sprint Review, Week 7 report).
  • Focus: Week 6 trial follow-up and the final transition. Scope is fixed after the Week 6 review, with one external dependency: password reset needs the SMTP credentials for the customer's mail domain.
  • Delivered increment: MVP v3 — the final course version.
  • Planned items:
  • User stories: US-11 (deterministic irritant warning for sensitive-skin users), US-27 (password reset)
  • Product: PBI-505 (deterministic irritant warning for sensitive-skin users), PBI-503 (password reset via the customer's mail domain), PBI-506 (frontend UX fixes — navigation and missing actions)
  • Transition & delivery: PBI-507 (final MVP v3 release), PBI-508 (public sanitized demo video), PBI-509 (final transition confirmation + handover status), PBI-510 (Week 7 UAT), PBI-511 (Week 7 report set)
  • Dropped after the Week 6 review: tracker email reminders (PBI-504) — the customer will handle reminders with her own Telegram bot, so they are out of the product's scope.

Course outcome

MVP v3 (Sprint 5) is the final course version. It delivers the guest questionnaire → justified cosmetic bag together with the personal account (profile, one saved bag, «Подошло / Не подошло» feedback, product replacement, a 12-week result tracker, account management), password reset, and a deterministic irritant warning for sensitive-skin users — deployed, documented, and handed over with docs/customer-handover.md. The handover level and the customer-confirmation status reached by submission are recorded in that document and in reports/week7/README.md.

Backlog / later (not scheduled)

  • Favorites (US-23, PBI-501) — not part of the approved account specification; kept for later.
  • Product photo on each card (US-10); a mobile version. Fuller skin-progress tracking beyond the 6-checkpoint tracker (daily habit calendar, dynamics charts, before/after photos) remains a product vision, not scheduled course work.

Continuing work (maintained across Sprints)

The architecture documentation and ADRs, quality requirements and quality requirement tests, CI quality gates, Definition of Done, and the hosted documentation site introduced or maintained in Assignments 4–5 are maintained assets. Later Sprints must keep them current as product scope, architecture, deployment model, or workflow change.