HKSM

A facilitated discussion with a small, targeted group of users or stakeholders to gather qualitative feedback on epics, user stories, prototypes, or increments. In SBOK Scrum, it is a Product Owner technique to validate assumptions, discover needs, and refine the prioritized product backlog.

Key Points

• Qualitative technique using moderated group discussions to explore user needs and perceptions.
• Best for early discovery and backlog refinement of epics and user stories, and to validate design options.
• Participants represent key personas or user segments; groups are typically small and focused.
• Often uses artifacts such as wireframes, prototypes, story maps, or a working increment.
• Produces insights that translate into new or updated user stories, acceptance criteria, and priority changes.
• Complements but does not replace Sprint Review feedback, usability testing, or analytics.

Purpose of Analysis

Focus group meetings aim to surface what users value, what confuses them, and what trade-offs they prefer. This helps the Product Owner decide which features to build next and how to shape acceptance criteria.

The technique reduces uncertainty around epics and stories by validating assumptions and revealing risks, constraints, and non-functional needs such as performance or accessibility.

Method Steps

• Define objectives: clarify the decisions you want to inform, such as splitting an epic or refining acceptance criteria.
• Recruit participants: select 6–10 people who match the target personas; avoid mixing very different personas in one group.
• Prepare materials: create a discussion guide, scenarios, mockups or prototypes, and a consent/recording plan.
• Facilitate the session: a neutral moderator leads; the Product Owner listens; the Scrum Master supports timeboxing and logistics.
• Capture data: record quotes, themes, pain points, desired outcomes, and any measurable ratings.
• Synthesize findings: group insights into themes, validate with the team, and convert into backlog changes.
• Follow up: confirm key interpretations if needed and schedule additional sessions for other personas.

Inputs Needed

• Project Vision Statement and product goals.
• Personas or user segments and relevant usage scenarios.
• Epics, user stories, or a slice of the prioritized product backlog to explore.
• Design artifacts such as wireframes, prototypes, or the latest increment.
• Discussion guide with open questions and tasks.
• Logistics plan for recruitment, consent, recording, and timeboxing.

Outputs Produced

• Consolidated findings and themes with supporting quotes or observations.
• New or updated user stories and refined acceptance criteria.
• Priority adjustments in the prioritized product backlog.
• Identified risks, assumptions, constraints, and potential non-functional requirements.
• Recommendations for additional research or validation.

Interpretation Tips

• Treat results as directional insights, not statistically representative truth.
• Weigh feedback by persona relevance and business value, not by who speaks the loudest.
• Convert insights into INVEST-quality user stories and clear acceptance criteria.
• Triangulate with other data sources such as analytics, A/B tests, or stakeholder interviews.
• Timebox the synthesis and review changes with the team during backlog refinement.

Example

A Product Owner explores an epic for onboarding. Eight target users review a clickable prototype and discuss first-time setup tasks. The session reveals confusion around permissions and a desire for a guided checklist.

The team creates new user stories for a step-by-step wizard, clarifies acceptance criteria for error handling, and raises a risk about third-party integrations, resulting in priority changes in the product backlog.

Pitfalls

• Recruiting the wrong participants or mixing incompatible personas in one session.
• Leading questions or facilitator bias skewing the discussion.
• Letting dominant voices overrule quieter participants.
• Jumping to solutions without capturing the underlying problem or outcome.
• Overgeneralizing from a single session without triangulation.
• Poor documentation that cannot be traced back to updated backlog items.

PMP/SCRUM Example Question

A Product Owner wants quick, qualitative input on a newly proposed epic before splitting it into user stories. Which tool or technique is most appropriate?

1. Focus group meetings
2. Sprint Retrospective
3. Daily Scrum
4. Monte Carlo simulation

Correct Answer: A — Focus group meetings

Explanation: Focus groups gather early user feedback to shape epics and acceptance criteria. A Retrospective targets process improvement, the Daily Scrum is for team coordination, and Monte Carlo models schedule or delivery risk.