Theme
Definition
A theme is a high-level grouping of related user stories and epics in agile product development that represents a strategic area of focus — such as performance, user onboarding, or internationalization — used to organize the product backlog and communicate roadmap intent.
Themes exist at the strategic layer of the agile hierarchy, above epics. They're not a Scrum concept — the Scrum Guide doesn't mention them — but they're widely used in product management to communicate what the team is focused on across a quarter, half-year, or longer.
What themes are for: Themes help stakeholders understand the product strategy without needing to read every epic and story. "This quarter, we're focused on three themes: onboarding, performance, and API partner access" communicates direction far more clearly than a list of 60 stories.
Theme vs. epic vs. user story:
- Theme: a strategic area of focus, lasting months (e.g., "User trust")
- Epic: a significant feature within a theme, lasting weeks (e.g., "Two-factor authentication")
- User story: a sprint-sized unit of work within an epic (e.g., "As a user, I want to set up 2FA via SMS")
This hierarchy varies between organizations. Some teams use "theme" and "initiative" interchangeably. Others use themes as horizontal cross-cutting concerns that span multiple epics in different product areas.
How teams use themes in practice:
- Quarterly planning: leadership selects two or three themes that represent business priorities.
- Roadmap communication: themes appear on public or internal roadmaps rather than specific features.
- Backlog organization: stories and epics are tagged by theme to make trade-off conversations easier.
The flexibility of themes is a feature, not a bug — they adapt to how a given organization thinks about strategy and communication. Just be consistent with your own definitions.
Examples
- Q2 roadmap organized around three themes: Growth, Reliability, and Developer Experience
- Theme 'User trust' groups epics for 2FA, privacy controls, data export, and audit logging
- Product strategy slide shows four themes with the number of epics in each for the year
- Engineering team uses themes to balance investment: 60% product themes, 40% technical themes
- PO tags every backlog item by theme to run a report on how much work went to each area each quarter
Related terms
Snap a theme. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.