HKSM

A documented description of the specific customer segments or personas that a planned release is meant to serve. Identified during release planning, it guides which backlog items are selected, how features are validated, and how the release is deployed and communicated.

Key Points

• Specifies which users, segments, or personas the release is intended to reach.
• Created in release planning and referenced throughout sprint planning and deployment.
• Drives story selection, acceptance criteria, user validation, and rollout strategy.
• Acts as an output of release planning and an input to backlog prioritization and deployment planning.
• Should include inclusion and exclusion criteria, channels, regions, and rollout waves.
• Updated as feedback emerges from reviews, demos, and market data.

Purpose

Target Customers for Release focuses the team on the specific users who will benefit from and receive the increment. By narrowing scope to defined segments, the team maximizes business value and avoids building features for the wrong audience.

It also clarifies deployment needs, support readiness, training, and communications. This alignment reduces waste, improves adoption, and supports measurable release goals.

Key Terms & Clauses

• Persona or Segment: A concise profile of users sharing needs, behaviors, or constraints.
• Inclusion Criteria: Who is explicitly in scope for the release (e.g., region, plan tier, device type).
• Exclusion Criteria: Who will not receive this release and why (e.g., compliance limits, unsupported channels).
• Rollout Waves: Beta, canary, phased, or full rollout sequencing by cohort.
• Channels: Web, mobile, partner portal, internal users, or specific customer success pilots.
• Validation Contacts: Representative users or stakeholders for demos, UAT, and feedback.
• Success Measures: Adoption, activation, NPS, defect rates, or revenue tied to the targeted segments.

How to Develop/Evaluate

• Review the product vision, release goals, and prioritized product backlog to infer who benefits most now.
• Segment customers using data (usage, revenue, risk, geography, compliance) and stakeholder input.
• Draft brief persona or segment cards with inclusion/exclusion criteria and key needs.
• Quantify scale and impact (size of cohort, value potential, risk profile) to support prioritization.
• Validate with stakeholders, customer representatives, and the Scrum Team; refine for clarity and feasibility.
• Record in the Release Plan with traceability to selected epics and user stories.
• Evaluate fitness by checking testability, measurability, feasibility of deployment, and alignment to goals.

How to Use

• Backlog Prioritization: Select and order stories that deliver the highest value to the defined segments.
• Acceptance Criteria: Tailor scenarios and test data to reflect targeted users and their environments.
• Sprint Planning: Choose backlog items and plan capacity aligned with the targeted customers and rollout waves.
• Reviews and Demos: Invite representative users and stakeholders from the target segments for feedback.
• Deployment Planning: Define channels, timing windows, migration steps, and support for the specified cohorts.
• Go-to-Market: Align release notes, training, and communications to the needs and language of the target segments.
• Metrics: Track adoption and outcomes specifically within the targeted cohorts to confirm value realization.

Example Snippet

Excerpt from a Release Plan:

• Release 2.1 Target Customers: EU small and mid-size merchants using the web app; internal compliance reviewers.
• Exclusions: US market and legacy desktop client this cycle.
• Rollout: 2-week beta to 200 opt-in merchants, then phased to remaining EU cohort.
• Success Measures: 30% feature adoption in target cohort within 30 days; defect rate under 2% for beta users.

Risks & Tips

• Risk: Vague or overly broad targeting leads to scattered scope and weak adoption. Tip: Use explicit inclusion/exclusion criteria.
• Risk: Ignoring compliance or region specifics causes rollout delays. Tip: Involve legal and regional SMEs early.
• Risk: Static targets despite new data. Tip: Revisit targets each sprint review and adjust the Release Plan as needed.
• Risk: Mismatch between target users and test participants. Tip: Recruit reviewers from the actual target cohort.
• Risk: Metrics do not isolate the cohort. Tip: Instrument analytics by segment to measure value realized.

PMP/SCRUM Example Question

During release planning, the Product Owner identifies early adopters in APAC as the target customers for the next release. What should the Scrum Team do next to align execution with this decision?

1. Select stories with the largest story points to maximize throughput.
2. Reorder the product backlog to prioritize items that deliver value to APAC early adopters and define matching acceptance criteria.
3. Freeze the Definition of Done to prevent changes during the release.
4. Schedule only technical spikes until more market data is available.

Correct Answer: B — Reorder the product backlog to prioritize items that deliver value to APAC early adopters and define matching acceptance criteria.

Explanation: Target Customers for Release is an output of release planning that becomes an input to backlog prioritization, acceptance criteria, and subsequent sprint planning. Options A, C, and D do not align scope and validation with the specified cohort.