TalentQuote Product MVP Delivery Tracker v0.3
Status: Candidate Product Execution Source of Truth
Version: 0.3
Category: Category C - Operational Execution Document
Folder: TalentQuote/Product-v1/
Primary Audience: Hugo, Triana, Product, Engineering, QA, Delivery, Codex, ChatGPT
Purpose: Prepare the TalentQuote MVP tracker to become the official Product Execution Source of Truth.
Governing model:
- Strategic docs govern vision.
- User Stories govern scope.
- Acceptance Criteria govern acceptance.
- UX Guide governs experience.
- Product MVP Delivery Tracker governs execution.
- Jira mirrors execution.
This document does not create new product strategy, expand MVP scope, or replace approved source documents.
Executive Product Dashboard
Executive Assessment
TalentQuote MVP execution is moving from source consolidation into launch governance. The current product spine is clear: talent intake, validation, approved reusable profiles, client browsing, legal gate, interviews, SOW, payment, and activation.
The tracker is close to becoming the execution source of truth, but it is not v1.0-ready yet. The biggest blockers are unresolved MVP/Phase conflicts, missing QA owners, missing QA evidence, malformed backlog rows, and unclear decisions around Instant Match, video tooling, invoice automation, and psychometrics.
MVP Readiness
| Area | Status | Rationale |
|---|---|---|
| Browse Talent | Complete | SCRUM-38 is marked Done, but still needs QA evidence before v1.0. |
| Candidate Profiles | Partial | CV/profile parsing, candidate tracking, videos, approval, and TalentScore storage remain mixed Not Started / Needs Review / Partially Done. |
| Talent Intake | Needs Review | SCRUM-70 is malformed and must be repaired before Jira import. |
| Recruiter Operations | Partial | Active roles and candidate tracker exist as MVP items, but several recruiter ops stories lack owners or validation. |
| Interviews | Partial | SCRUM-54 is Partially Done and missing webhook/account behavior. |
| MSA | Needs Review | MSA stories are MVP-critical but still require data update, alert, and QA validation. |
| SOW | Partial | SCRUM-58 is Partially Done and has alert/storage gaps. |
| Payments | Partial | Stripe payment is partially done; invoice automation should not block MVP if manual/semi-manual process is approved. |
| Instant Match | Needs Review | Strategically central, but SCRUM-165 is marked FASE 1 / conflict. Minimal Instant Match list should be MVP-critical. |
| AI Videos | Partial | SCRUM-115 is Partially Done; tooling and voice gap remain. |
| Onboarding | Needs Review | Full dashboard is deferred; MVP needs minimal activation/onboarding status. |
Product Health Summary
| Metric | Count |
|---|---|
| Total Stories | 40 |
| MVP Stories / Launch-Critical Candidates | 18 |
| Phase 1 Stories | 10 |
| Phase 2 / Future Stories | 9 |
| Unknown / Malformed | 2 |
| Done | 1 |
| In Progress / Partially Done | 7 |
| Needs Review | 18 |
| Blocked | 0 |
| Unassigned Engineering Owner | 33 |
MVP Launch Baseline
Launch-critical means the story is required to make the core TalentQuote MVP work end-to-end. It excludes Phase 2, advanced reporting, agency features, polished dashboards, advanced AI learning, and nice-to-have UI.
| Story ID | Story | Priority | Status |
|---|---|---|---|
| SCRUM-38 | Browse Talent / blurred profiles | Launch Critical | Done |
| SCRUM-44 | DocuSign inline MSA | Launch Critical | Needs Review |
| SCRUM-54 | Book interviews via Cal.com | Launch Critical | Partially Done |
| SCRUM-58 | Review and sign SOW | Launch Critical | Partially Done |
| SCRUM-59 | Stripe payment | Launch Critical | Partially Done |
| SCRUM-70 | Candidate application via WhatsApp/QR | Launch Critical | Needs Review |
| SCRUM-83 | Active roles sync | Launch Critical | Not Started |
| SCRUM-84 | Candidate tracker by status | Launch Critical | Needs Review |
| SCRUM-85 | Parsed CV data | Launch Critical | Not Started |
| SCRUM-87 | Video generation status | Launch Critical | Not Started |
| SCRUM-88 | Approve candidates | Launch Critical | Partially Done |
| SCRUM-115 | Generate AI videos | Launch Critical | Partially Done |
| SCRUM-116 | Supabase/Airtable data sync | Launch Critical | Not Started |
| SCRUM-122 | MSA required before interviews | Launch Critical | Not Started |
| SCRUM-123 | Store MSAs and SOWs | Launch Critical | Not Started |
| SCRUM-124 | Stripe payment webhook records | Launch Critical | Not Started |
| SCRUM-158 | Store CVs/interviews/TalentScores for reuse | Launch Critical | Needs Review |
| SCRUM-165 | Instant Match available talent list | Launch Critical | Needs Review |
Launch baseline interpretation:
SCRUM-165should be treated as MVP-critical at minimum viable level because Instant Match is central to the current product reality.SCRUM-62full onboarding dashboard is not launch-critical, but minimal activation/onboarding status must exist through the launch flow.SCRUM-125invoice automation is not launch-critical if a manual or semi-manual invoice process is explicitly approved.
MVP Execution Tracker
| Story | Story / Capability | Scope | Priority | Delivery Status | Product Owner | Engineering Owner | QA Owner | QA Status | Product Decision |
|---|---|---|---|---|---|---|---|---|---|
| SCRUM-38 | Browse Talent / blurred profiles | MVP | Launch Critical | Done | TBD | TBD | TBD | Needs Validation | Confirm Done with QA evidence |
| SCRUM-41 | Motion and animations | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Move to Phase 1 unless required for core trust UX |
| SCRUM-44 | DocuSign inline MSA | MVP | Launch Critical | Needs Review | TBD | Ricardo Mateo / Samu | TBD | Needs Validation | Keep in MVP; validate data update and Slack alert behavior |
| SCRUM-49 | Short video intro / psychometric display | MVP | Needs Review | Partially Done | TBD | TBD | TBD | Needs Validation | Keep profile media in MVP; move advanced psychometric display to Phase 1 if needed |
| SCRUM-54 | Book interviews via Cal.com | MVP | Launch Critical | Partially Done | TBD | Omar Bautista Baigorri | TBD | Needs Validation | Keep in MVP; confirm missing webhook/account behavior |
| SCRUM-58 | Review and sign SOW | MVP | Launch Critical | Partially Done | TBD | Ricardo | TBD | Needs Validation | Keep in MVP; confirm alerting/storage gap |
| SCRUM-59 | Stripe payment | MVP | Launch Critical | Partially Done | TBD | Marcos Laurens | TBD | Needs Validation | Keep in MVP; invoice automation can remain manual/semi-manual for launch |
| SCRUM-62 | Onboarding dashboard | FASE 2 | Needs Review | Deferred | TBD | TBD | TBD | Needs Validation | MVP needs minimal onboarding status, not polished dashboard |
| SCRUM-70 | Candidate application via WhatsApp/QR | Malformed / MVP-Phase 1 | Launch Critical | Needs Review | TBD | Jan Leone Ramirez Martinez | TBD | Needs Validation | Repair row and split SCRUM-70/71/72 before Jira import |
| SCRUM-72 | AI interview candidate flow | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Split web vs WhatsApp; keep only launch-critical intake validation in MVP |
| SCRUM-78 | AI psychometric score | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Phase 1 unless required as basic internal TalentScore |
| SCRUM-80 | Delete / deactivate profile | FASE 2 | Future | Deferred | TBD | TBD | TBD | Needs Validation | Future privacy/control enhancement |
| SCRUM-83 | Active roles sync | MVP | Launch Critical | Not Started | TBD | Jorge Alejandoro Estrella | TBD | Needs Validation | Keep in MVP as recruiter ops foundation |
| SCRUM-84 | Candidate tracker by status | MVP | Launch Critical | Needs Review | TBD | TBD | TBD | Needs Validation | Keep in MVP; validate Airtable functionality |
| SCRUM-85 | Parsed CV data | MVP | Launch Critical | Not Started | TBD | TBD | TBD | Needs Validation | Keep in MVP if Candidate Profiles depend on parsed profile fields |
| SCRUM-86 | AI interview from Airtable | FASE 2 | Future | Deferred | TBD | TBD | TBD | Needs Validation | Move out of MVP; depends on TestGorilla/psychometrics decision |
| SCRUM-87 | Video generation status | MVP | Launch Critical | Not Started | TBD | TBD | TBD | Needs Validation | Keep if AI videos remain launch-critical |
| SCRUM-88 | Approve candidates | MVP | Launch Critical | Partially Done | TBD | TBD | TBD | Needs Validation | Keep in MVP; recruiter approval is required for marketplace visibility |
| SCRUM-91 | Recruiter alerts | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Split; MVP only needs essential operational alerts |
| SCRUM-94 | Stripe invoices / finance sync | FASE 2 | Future | Needs Review | TBD | TBD | TBD | Needs Validation | Do not include advanced finance automation in MVP |
| SCRUM-96 | Client subscription status | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Phase 1; MVP can rely on Stripe/admin validation |
| SCRUM-99 | Failed payment alerts | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Phase 1 unless payment failure blocks launch |
| SCRUM-104 | SLA timers/logs | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Split logs vs SLA dashboard; MVP needs basic SLA accountability |
| SCRUM-110 | Support feedback / satisfaction | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Not launch-critical; keep outside MVP baseline |
| SCRUM-115 | Generate AI videos | MVP | Launch Critical | Partially Done | TBD | Luis Robledo | TBD | Needs Validation | Resolve HeyGen/Synthesia tooling and voice gap |
| SCRUM-116 | Supabase/Airtable data sync | MVP | Launch Critical | Not Started | TBD | TBD | TBD | Needs Validation | Keep in MVP as data integrity foundation |
| SCRUM-117 | Feedback clustering | FASE 2 | Future | Needs Review | TBD | TBD | TBD | Needs Validation | Move to Future Scope |
| SCRUM-118 | Forecast redeployment | FASE 2 | Future | Deferred | TBD | TBD | TBD | Needs Validation | Move to Future Scope |
| SCRUM-119 | Highest success rate recommendations | FASE 2 | Future | Deferred | TBD | TBD | TBD | Needs Validation | Move to Future Scope |
| SCRUM-121 | AI model retraining | FASE 2 | Future | Partially Done | TBD | TBD | TBD | Needs Validation | Move to Future Scope; validate missing source story |
| SCRUM-122 | MSA required before interviews | MVP | Launch Critical | Not Started | TBD | TBD | TBD | Needs Validation | Keep in MVP as legal gate |
| SCRUM-123 | Store MSAs and SOWs | MVP | Launch Critical | Not Started | TBD | TBD | TBD | Needs Validation | Keep MVP as secure storage/backfill if automation not ready |
| SCRUM-124 | Stripe payment webhook records | MVP | Launch Critical | Not Started | TBD | TBD | TBD | Needs Validation | Keep in MVP for payment confirmation |
| SCRUM-125 | Invoice and receipt generation | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Move automation to Phase 1; manual invoice process acceptable for MVP if approved |
| SCRUM-126 | Payment failure / buyout notifications | FASE 1 | Phase 1 | Needs Review | TBD | TBD | TBD | Needs Validation | Move to Phase 1 unless required for launch risk control |
| SCRUM-133 | Agency revenue share payouts | FASE 2 | Future | Deferred | TBD | TBD | TBD | Needs Validation | Future Scope |
| SCRUM-156 | White-label branding | FASE 2 | Future | Deferred | TBD | TBD | TBD | Needs Validation | Future Scope |
| SCRUM-158 | Store CVs/interviews/TalentScores for reuse | MVP | Launch Critical | Needs Review | TBD | TBD | TBD | Needs Validation | Keep minimal reusable asset storage in MVP; advanced reuse analytics later |
| SCRUM-165 | Instant Match available talent list | FASE 1 / MVP conflict | Launch Critical | Needs Review | TBD | TBD | TBD | Needs Validation | Recommend MVP-critical minimal Instant Match list |
| SCRUM-166 | Missing story | Unknown | Needs Review | Needs Review | TBD | TBD | TBD | Needs Validation | Define or remove before Jira import |
MVP Scope Decisions
| Story | Current Labels | Conflict | Recommendation |
|---|---|---|---|
| SCRUM-41 | FASE 1 / MVP / MVP | Motion is labeled MVP in ordered source but FASE 1 in Triana. | Move to Phase 1 unless required for core trust confirmation. |
| SCRUM-49 | MVP with FASE 1 psychometric gaps | Profile video appears MVP, advanced psychometrics are incomplete. | Keep basic video/profile media in MVP; move advanced psychometric display to Phase 1. |
| SCRUM-54 | MVP / Phase 1 | Interview booking is MVP-critical but missing webhook/account work. | Keep in MVP; reduce launch scope to working booking + status update. |
| SCRUM-62 | FASE 2 / MVP Phase 1 / Phase 1 | Onboarding dashboard appears deferred but activation needs status visibility. | Move full dashboard to Phase 1/2; keep minimal onboarding status in MVP. |
| SCRUM-70 | Malformed / MVP-Phase 1 | Triana row is shifted and includes SCRUM-71/SCRUM-72 data. | Repair and split before Jira. |
| SCRUM-72 | FASE 1 / MVP / Phase 1 | Candidate AI interview has web/WhatsApp and psychometric scope mixed. | Split; only launch-critical candidate validation stays in MVP. |
| SCRUM-78 | FASE 1 / MVP / Phase 1 | Psychometric score is not clean MVP execution. | Move advanced candidate-facing score to Phase 1; keep internal basic signal if needed. |
| SCRUM-86 | FASE 2 / MVP / MVP | AI interview from Airtable depends on psychometrics/TestGorilla decisions. | Move out of MVP. |
| SCRUM-91 | FASE 1 / MVP / Phase 1 | Recruiter alerts are too broad and need splitting. | Keep only essential operational alerts in MVP if required. |
| SCRUM-104 | FASE 1 / MVP / MVP | SLA logs/dashboard story is too broad. | Split; keep basic SLA accountability, defer dashboard/log sophistication. |
| SCRUM-115 | MVP / MVP Phase 1 / Phase 1 | Video generation is MVP-relevant but tooling/voice are unresolved. | Keep basic approved AI video in MVP; resolve HeyGen/Synthesia decision. |
| SCRUM-117 | FASE 2 / MVP Phase 1 / Phase 1 | Feedback clustering is advanced AI learning. | Move to Future Scope. |
| SCRUM-119 | FASE 2 / MVP / Phase 1 | Recommendation intelligence/redeployment logic is future-facing. | Move to Future Scope. |
| SCRUM-125 | FASE 1 / MVP / MVP | Invoice automation conflicts with manual/semi-manual reality. | Move automation to Phase 1; approve manual launch process. |
| SCRUM-165 | FASE 1 / MVP / Phase 1 | Instant Match is central but tracker marks it FASE 1. | Keep minimal Instant Match available-talent list in MVP. |
| SCRUM-166 | Unknown / Phase 1 | Story data missing. | Define or remove before Jira import. |
Product Decision Log
PD-001
Tracker governs execution; User Stories govern scope; Acceptance Criteria govern acceptance; UX Guide governs experience.
PD-002
BRD v1.3 remains historical/supporting context and does not govern Jira execution.
PD-003
Minimal Instant Match available-talent list is MVP-critical; advanced matching intelligence is future scope.
PD-004
Full onboarding dashboard is not MVP-critical; minimal activation/onboarding status is required.
PD-005
Advanced psychometric display and candidate-facing scoring move to Phase 1 unless needed as basic internal validation.
PD-006
Feedback clustering, forecasting, retraining, redeployment intelligence, agency features, white-label, and advanced analytics move to Future Scope.
PD-007
Invoice automation does not block MVP if manual/semi-manual finance process is approved.
PD-008
SCRUM-70 must be repaired and split before Jira import.
PD-009
SCRUM-166 must be defined or removed before Jira import.
PD-010
Done cannot mean accepted until QA evidence is attached.
Ownership Model
| Story | Product Owner | Engineering Owner | QA Owner |
|---|---|---|---|
| SCRUM-38 | Hugo / Product | TBD | TBD |
| SCRUM-41 | Product | TBD | TBD |
| SCRUM-44 | Hugo / Product | Ricardo Mateo / Samu | TBD |
| SCRUM-49 | Product | TBD | TBD |
| SCRUM-54 | Hugo / Product | Omar Bautista Baigorri | TBD |
| SCRUM-58 | Hugo / Product | Ricardo | TBD |
| SCRUM-59 | Hugo / Product | Marcos Laurens | TBD |
| SCRUM-62 | Product | TBD | TBD |
| SCRUM-70 | Hugo / Product | Jan Leone Ramirez Martinez | TBD |
| SCRUM-72 | Product | TBD | TBD |
| SCRUM-78 | Product | TBD | TBD |
| SCRUM-80 | Product | TBD | TBD |
| SCRUM-83 | Hugo / Product | Jorge Alejandoro Estrella | TBD |
| SCRUM-84 | Hugo / Product | TBD | TBD |
| SCRUM-85 | Hugo / Product | TBD | TBD |
| SCRUM-86 | Product | TBD | TBD |
| SCRUM-87 | Hugo / Product | TBD | TBD |
| SCRUM-88 | Hugo / Product | TBD | TBD |
| SCRUM-91 | Product | TBD | TBD |
| SCRUM-94 | Product | TBD | TBD |
| SCRUM-96 | Product | TBD | TBD |
| SCRUM-99 | Product | TBD | TBD |
| SCRUM-104 | Product | TBD | TBD |
| SCRUM-110 | Product | TBD | TBD |
| SCRUM-115 | Hugo / Product | Luis Robledo | TBD |
| SCRUM-116 | Hugo / Product | TBD | TBD |
| SCRUM-117 | Product | TBD | TBD |
| SCRUM-118 | Product | TBD | TBD |
| SCRUM-119 | Product | TBD | TBD |
| SCRUM-121 | Product | TBD | TBD |
| SCRUM-122 | Hugo / Product | TBD | TBD |
| SCRUM-123 | Hugo / Product | TBD | TBD |
| SCRUM-124 | Hugo / Product | TBD | TBD |
| SCRUM-125 | Product | TBD | TBD |
| SCRUM-126 | Product | TBD | TBD |
| SCRUM-133 | Product | TBD | TBD |
| SCRUM-156 | Product | TBD | TBD |
| SCRUM-158 | Hugo / Product | TBD | TBD |
| SCRUM-165 | Hugo / Product | TBD | TBD |
| SCRUM-166 | Product | TBD | TBD |
QA Readiness
| Story | QA Status | Evidence Required |
|---|---|---|
| SCRUM-38 | Needs Validation | UI walkthrough, data privacy check, marketplace/profile visibility proof |
| SCRUM-41 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-44 | Needs Validation | DocuSign/Supabase record, webhook log, signed document storage evidence |
| SCRUM-49 | Needs Validation | UI walkthrough, data privacy check, marketplace/profile visibility proof |
| SCRUM-54 | Needs Validation | Cal.com booking, calendar invite, Airtable interview_status update |
| SCRUM-58 | Needs Validation | DocuSign/Supabase record, webhook log, signed document storage evidence |
| SCRUM-59 | Needs Validation | Stripe event, Supabase/Airtable record, invoice/payment status evidence |
| SCRUM-62 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-70 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-72 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-78 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-80 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-83 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-84 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-85 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-86 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-87 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-88 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-91 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-94 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-96 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-99 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-104 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-110 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-115 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-116 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-117 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-118 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-119 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-121 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-122 | Not Tested | DocuSign/Supabase record, webhook log, signed document storage evidence |
| SCRUM-123 | Not Tested | DocuSign/Supabase record, webhook log, signed document storage evidence |
| SCRUM-124 | Not Tested | Stripe event, Supabase/Airtable record, invoice/payment status evidence |
| SCRUM-125 | Needs Validation | Stripe event, Supabase/Airtable record, invoice/payment status evidence |
| SCRUM-126 | Needs Validation | Stripe event, Supabase/Airtable record, invoice/payment status evidence |
| SCRUM-133 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-156 | Not Tested | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-158 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
| SCRUM-165 | Needs Validation | UI walkthrough, data privacy check, marketplace/profile visibility proof |
| SCRUM-166 | Needs Validation | Acceptance criteria pass/fail, screenshot or Loom, test data, owner sign-off |
Story Dependencies
| Story | Depends On | Rationale |
|---|---|---|
| SCRUM-44 | SCRUM-38 | MSA unlock depends on client entering through Browse Talent/profile discovery. |
| SCRUM-54 | SCRUM-44 / SCRUM-122 | Interview booking should not occur before MSA/legal gate is valid. |
| SCRUM-58 | SCRUM-54 | SOW follows candidate/interview selection. |
| SCRUM-59 | SCRUM-58 | Payment follows SOW acceptance. |
| SCRUM-62 | SCRUM-59 | Onboarding status follows payment/contract activation. |
| SCRUM-70 | None visible | Talent intake starts talent-side flow. |
| SCRUM-85 | SCRUM-70 | Parsed profile data depends on candidate application/intake. |
| SCRUM-87 | SCRUM-115 | Video status tracking depends on video generation. |
| SCRUM-88 | SCRUM-85 / SCRUM-87 / SCRUM-115 | Recruiter approval depends on profile data and media readiness. |
| SCRUM-158 | SCRUM-85 / SCRUM-88 | Reusable profile storage depends on parsed/approved candidate assets. |
| SCRUM-165 | SCRUM-88 / SCRUM-158 | Instant Match marketplace visibility depends on approved, reusable, available talent. |
| SCRUM-124 | SCRUM-59 | Payment webhook records depend on Stripe payment flow. |
| SCRUM-123 | SCRUM-44 / SCRUM-58 | Document storage depends on signed MSA/SOW events. |
Current MVP Product Journey
Talent Side
| Stage | Story Mapping | Execution Status |
|---|---|---|
| Apply | SCRUM-70 | Needs Review; malformed source row must be repaired. |
| Validation | SCRUM-85, SCRUM-78 | Profile parsing is Not Started; psychometrics need scope decision. |
| Interview | SCRUM-72 | Needs Review; split web vs WhatsApp and psychometric scope. |
| Video | SCRUM-115, SCRUM-87 | Partially Done / Not Started; tooling and status tracking unresolved. |
| Approval | SCRUM-88 | Partially Done; recruiter approval remains MVP-critical. |
| Instant Match Ready | SCRUM-158, SCRUM-165 | Needs Review; minimal marketplace-ready state must be defined. |
Client Side
| Stage | Story Mapping | Execution Status |
|---|---|---|
| Browse | SCRUM-38, SCRUM-49, SCRUM-165 | Browse marked Done; profile/video/Instant Match need validation. |
| MSA | SCRUM-44, SCRUM-122, SCRUM-123 | MVP-critical; needs review and QA evidence. |
| Interview | SCRUM-54 | Partially Done; missing webhook/account behavior. |
| SOW | SCRUM-58, SCRUM-123 | Partially Done; storage/alerting gap. |
| Payment | SCRUM-59, SCRUM-124 | Partially Done / Not Started; invoice automation deferred. |
| Activation | SCRUM-62 minimal status, SCRUM-104 basic SLA accountability | Full dashboard deferred; minimal activation status required. |
Instant Match Ready Definition
A candidate is Instant Match Ready only when the following operational requirements are true:
| Requirement | Story Reference | Status |
|---|---|---|
| Approved profile | SCRUM-88 | Partially Done / MVP-critical |
| Skills validated or profile fields parsed | SCRUM-85, SCRUM-78 | Not Started / Needs Review |
| Availability confirmed | SCRUM-165, SCRUM-158 | Needs Review |
| Candidate introduction completed | SCRUM-115, SCRUM-87 | Partially Done / Not Started |
| Compensation defined | SCRUM-38, SCRUM-165 | Must be visible as rate/rate band in marketplace/profile |
| Recruiter approval | SCRUM-88 | Required before marketplace visibility |
| Visible in marketplace | SCRUM-38, SCRUM-49, SCRUM-165 | Browse is Done; Instant Match list needs MVP decision |
Operational rule:
Do not mark a candidate as Instant Match Ready until profile, availability, compensation, media/introduction, recruiter approval, and marketplace visibility have all been validated.
Future Scope
The following items should not pollute MVP execution tracking. They remain visible for governance, but should not block MVP launch.
| Story | Future Scope Area | Reason |
|---|---|---|
| SCRUM-80 | Candidate data control enhancement | Useful but not core launch flow. |
| SCRUM-86 | Advanced AI interview automation | Depends on psychometrics/TestGorilla decisions. |
| SCRUM-94 | Advanced finance sync/dashboard | Finance automation beyond launch-critical payments. |
| SCRUM-117 | Feedback clustering | Advanced AI learning. |
| SCRUM-118 | Forecasting | Future redeployment intelligence. |
| SCRUM-119 | Role success recommendations | Advanced recommendation layer. |
| SCRUM-121 | AI retraining | Future model governance. |
| SCRUM-133 | Agency payouts | Agency portal/future business model. |
| SCRUM-156 | White-label branding | Agency portal/future business model. |
| Advanced analytics | Dashboards / Metabase / revenue intelligence | No current implementation spec; belongs after MVP. |
Jira Readiness Review
Ready For Jira
These are candidates for Jira only after QA/evidence fields are added during sprint setup:
- SCRUM-38
- SCRUM-83
- SCRUM-85
- SCRUM-87
- SCRUM-116
- SCRUM-122
- SCRUM-123
- SCRUM-124
Require Grooming
- SCRUM-41
- SCRUM-49
- SCRUM-54
- SCRUM-58
- SCRUM-59
- SCRUM-62
- SCRUM-70
- SCRUM-72
- SCRUM-78
- SCRUM-88
- SCRUM-91
- SCRUM-104
- SCRUM-115
- SCRUM-158
- SCRUM-165
- SCRUM-166
Require Owner Assignment
Most stories still require explicit Engineering Owner and QA Owner assignment. Current known engineering owners are preserved where visible: Ricardo Mateo / Samu, Omar Bautista Baigorri, Ricardo, Marcos Laurens, Jan Leone Ramirez Martinez, Jorge Alejandoro Estrella, and Luis Robledo.
Require Acceptance Clarification
- SCRUM-70: source row malformed.
- SCRUM-72: web vs WhatsApp / psychometric scope mixed.
- SCRUM-78: candidate-facing vs internal scoring needs decision.
- SCRUM-104: SLA logs vs dashboard scope needs split.
- SCRUM-115: HeyGen/Synthesia and voice/tooling acceptance unclear.
- SCRUM-165: Instant Match MVP vs Phase 1 conflict.
- SCRUM-166: missing story.
Require Scope Clarification
- SCRUM-41
- SCRUM-62
- SCRUM-86
- SCRUM-91
- SCRUM-94
- SCRUM-96
- SCRUM-99
- SCRUM-110
- SCRUM-117
- SCRUM-119
- SCRUM-125
- SCRUM-126
- SCRUM-165
Historical Data Quality Findings
These findings came from the v0.2 workbook comparison and are preserved for audit only. They should not dominate daily execution tracking.
- Ordered import duplicate keys:
SCRUM-93,SCRUM-94,SCRUM-120. - Triana backlog had no duplicate issue keys.
SCRUM-70row is malformed and contains shiftedSCRUM-71/SCRUM-72data.SCRUM-166is missing story data.- Triana workbook had
#VALUE!artifacts near the top ofEPICA,PRODUCT BACKLOG,TASK, andROAD MAP. Hoja1appears unrelated to TalentQuote and referencesPara el AntojoHome work.TASKandROAD MAPsheets were incomplete and should not govern execution timing yet.- Missing ownership and QA ownership remain the largest operational data gap.
Tracker Promotion Recommendation
Recommendation: Yes with Minor Revisions.
v0.3 can become TalentQuote_Product_MVP_Delivery_Tracker_v1.0 after the following minor but important revisions:
- Repair or remove
SCRUM-70andSCRUM-166. - Confirm the MVP treatment of
SCRUM-165Instant Match available-talent list. - Assign Engineering Owner and QA Owner for launch-critical stories.
- Add actual QA evidence for stories marked Done or Partially Done.
- Confirm manual vs automated invoice handling for launch.
- Decide HeyGen vs Synthesia language and tooling for AI videos.
- Move Future Scope items out of active MVP sprint views.
Once those are done, v1.0 can be approved as the official Product Execution Source of Truth and Jira should mirror it.