Agile Product Owner

What This Skill Does

This skill provides a toolkit for agile product owners to manage backlogs and execute sprints effectively. It includes user story generation, acceptance criteria patterns, sprint planning workflows, and velocity tracking. It's designed to help product owners build and prioritize product features in an agile environment.

When to Use

• Generate INVEST-compliant user stories.
• Write effective acceptance criteria.
• Break down epics into smaller tasks.
• Plan sprints and estimate story points.
• Prioritize backlog items.
• Track sprint velocity.

Key Features

• Generates user stories using a defined template.
• Provides patterns for writing acceptance criteria.
• Offers a workflow for breaking down epics.
• Includes a sprint planning workflow.
• Helps prioritize backlog items.
• Validates user stories against INVEST criteria.

Manual Installation

Manual installation View Full Skill Content The complete markdown content that gets installed Agile Product Owner

Backlog management and sprint execution toolkit for product owners, including user story generation, acceptance criteria patterns, sprint planning, and velocity tracking.

Table of Contents

User Story Generation Workflow

Acceptance Criteria Patterns Epic Breakdown Workflow Sprint Planning Workflow Backlog Prioritization Reference Documentation Tools

User Story Generation Workflow

Create INVEST-compliant user stories from requirements:

Identify the persona (who benefits from this feature) Define the action or capability needed Articulate the benefit or value delivered Write acceptance criteria using Given-When-Then Estimate story points using Fibonacci scale Validate against INVEST criteria Add to backlog with priority Validation: Story passes all INVEST criteria; acceptance criteria are testable

User Story Template

As a [persona], I want to [action/capability], So that [benefit/value].

Example: As a marketing manager, I want to export campaign reports to PDF, So that I can share results with stakeholders who don't have system access.

Story Types

Persona Reference

Acceptance Criteria Patterns

Write testable acceptance criteria using Given-When-Then format.

Given-When-Then Template

Given [precondition/context], When [action/trigger], Then [expected outcome].

Examples: Given the user is logged in with valid credentials, When they click the "Export" button, Then a PDF download starts within 2 seconds.

Given the user has entered an invalid email format, When they submit the registration form, Then an inline error message displays "Please enter a valid email address."

Given the shopping cart contains items, When the user refreshes the browser, Then the cart contents remain unchanged.

Acceptance Criteria Checklist

Each story should include criteria for:

Minimum Criteria by Story Size

See references/user-story-templates.md for complete template library.

Epic Breakdown Workflow

Break epics into deliverable sprint-sized stories:

Define epic scope and success criteria Identify all personas affected by the epic List all capabilities needed for each persona Group capabilities into logical stories Validate each story is ≤8 points Identify dependencies between stories Sequence stories for incremental delivery Validation: Each story delivers standalone value; total stories cover epic scope

Splitting Techniques

Epic Example

Epic: User Dashboard

Breakdown: Epic: User Dashboard (34 points total) ├── US-001: View key metrics (5 pts) - End User ├── US-002: Customize layout (5 pts) - Power User ├── US-003: Export data to CSV (3 pts) - End User ├── US-004: Share with team (5 pts) - End User ├── US-005: Set up alerts (5 pts) - Power User ├── US-006: Filter by date range (3 pts) - End User ├── US-007: Admin overview (5 pts) - Admin └── US-008: Enable caching (3 pts) - Enabler

Sprint Planning Workflow

Plan sprint capacity and select stories:

Calculate team capacity (velocity × availability) Review sprint goal with stakeholders Select stories from prioritized backlog Fill to 80-85% of capacity (committed) Add stretch goals (10-15% additional) Identify dependencies and risks Break complex stories into tasks Validation: Committed points ≤85% capacity; all stories have acceptance criteria

Capacity Calculation

Sprint Capacity = Average Velocity × Availability Factor

Example: Average Velocity: 30 points Team availability: 90% (one member partially out) Adjusted Capacity: 27 points

Committed: 23 points (85% of 27) Stretch: 4 points (15% of 27)

Availability Factors

Sprint Loading Template

Sprint Capacity: 27 points Sprint Goal: [Clear, measurable objective]

COMMITTED (23 points): [H] US-001: User dashboard (5 pts) [H] US-002: Export feature (3 pts) [H] US-003: Search filter (5 pts) [M] US-004: Settings page (5 pts) [M] US-005: Help tooltips (3 pts) [L] US-006: Theme options (2 pts)

STRETCH (4 points): [L] US-007: Sort options (2 pts) [L] US-008: Print view (2 pts)

See references/sprint-planning-guide.md for complete planning procedures.

Backlog Prioritization

Prioritize backlog using value and effort assessment.

Priority Levels

Prioritization Factors