Skip to content

[Phase 2] FR-2: Five parent interviews, recruited regardless of incident history #11

Open

Description

@don-petry

Story

As a Decider (or a delegate interviewer),
I want to interview five parents of Bedrock players aged about 7–15 and record a dated outcome per interview,
so that SM-1 shows whether lost-world and device-change incidents are common, and what parents already pay for.

Acceptance Criteria

  1. Five interviews with adult parents of Bedrock players aged about 7–15 are completed; each is dated and has notes, including the interview length chosen.
  2. Parents are recruited without regard to whether they have had an incident, and the recruitment approach is recorded.
  3. Each record states yes/no whether the parent described a lost-World or device-change incident in the last twelve months, what they did about it, and what backup-like services they already pay for.
  4. No child is interviewed and no notes name a child.
  5. The count of parents describing an incident (out of five) is written into brief.md §6 row 1 with a date.

Tasks / Subtasks

Dev Notes

  • Source: PRD FR-2, UJ-2, SM-1, §5 Privacy; brief §6 row 1, §7 criterion (a).
  • Safeguard (anti-gaming): recruiting only parents who already lost worlds would make SM-1 pass by construction (PRD FR-2). Do not screen on incident history.
  • Safeguard (consistency): write one fixed question guide before the first interview and use it unchanged for all five; record the guide version on each record so the SM-1 count is comparable across interviews.
  • "Recent" = within the last twelve months (PRD §10 assumption).
  • Raw notes identify adults and must stay out of the public worldchest repo; commit only the de-identified count and a short summary.
  • Out of scope: interviewing children, surveys. Compensation is the Decider's choice and is recorded.
  • Human-only work.

Project Structure Notes

Only the aggregated count lands in _bmad-output/planning-artifacts/brief.md §6 row 1.

References

Story prepared by the BMAD Scrum Master (Bob) for epic #7. Status: ready-for-dev.

Activity

  1. don-petry commented on Oct 21, 2026

    @don-petry
    ContributorAuthor

    dev-lead is withholding action on this item.

    It is labeled dev-lead:hands-off (deliberately kept off-limits to dev-lead (e.g. changes to the dev-lead automation itself)), so dev-lead will not pick it up while that label is present. This notice is posted once so the withhold is visible rather than looking like a stalled run.

    To re-enable automated pickup: remove the dev-lead:hands-off label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions