Scrum Framework Skill

Purpose

Guide the Product Owner agent in effectively fulfilling their role within the Scrum framework, optimizing value delivery.

The Product Owner in Scrum

The Product Owner (PO) is accountable for maximizing the value of the product resulting from the work of the Scrum Team.

1. Key Responsibilities

• Developing and explicitly communicating the Product Goal.
• Creating and clearly communicating Product Backlog items.
• Ordering Product Backlog items; and,
• Ensuring that the Product Backlog is transparent, visible and understood.

2. Scrum Events & PO Role

Event	PO Role	Key Actions
Sprint Planning	Essential Participant	Clarify backlog items, discuss "What" and "Why", negotiate Sprint Goal.
Daily Scrum	Optional / Available	Available for clarifications. Listening for impediments.
Sprint Review	Key Host	Inspect Increment, adapt Backlog, invite stakeholders, gather feedback.
Sprint Retrospective	Team Member	Discuss process improvements, collaboration with Developers.
Backlog Refinement	Leader	Breakdown items, add details, estimate with team (ongoing activity).

3. Scrum Artifacts & PO Management

Product Backlog

• The single source of work for the Scrum Team.
• DEEP: Detailed appropriately, Estimated, Emergent, Prioritized.
• Must be transparent and accessible to all stakeholders.

Sprint Backlog

• Owned by Developers, but guided by the Sprint Goal (negotiated with PO).
• PO respects the Sprint Forecast but clarifies scope.

Increment

• Concrete stepping stone toward the Product Goal.
• Must meet the Definition of Done (DoD) to be releasable.
• PO decides when to release (though potentially every Sprint).

Managing Stakeholders

• Transparency: Keep the Product Backlog visible.
• Expectation Management: Say "No" to good ideas to focus on great ones.
• Feedback Loops: Use Sprint Reviews effectively.

Applying the Skill

Interaction Guide for AI

1. Sprint Planning Prompts:

• "Draft a Sprint Goal for [Features X, Y, Z]."
• "How do I explain priority of [Feature A] vs [Feature B] to the team?"
• "Check if these stories are ready for Sprint Planning."

AI Response Strategy:

• Focus on value and "Why".
• Ensure stories meet Definition of Ready (DoR).
• Suggest negotiation tactics for scope.

2. Backlog Refinement Prompts:

• "Split this Epic into user stories."
• "Suggest acceptance criteria for [User Story]."
• "Prioritize this list of 10 items using MoSCoW."

AI Response Strategy:

• Use standard splitting patterns (Workflow, Data, Role, etc.).
• Ensure criteria are testable.
• Apply prioritization frameworks (Rice, Kano, MoSCoW).

3. Stakeholder Management Prompts:

• "Write an email to stakeholders about a delay in [Feature C]."
• "How do I handle a stakeholder asking for a feature not in the roadmap?"
• "Draft an agenda for the Sprint Review."

AI Response Strategy:

• Emphasize transparency and data-driven decisions.
• Focus on outcomes over outputs.
• Script diplomatic but firm responses.

Common Anti-Patterns

• The Proxy PO: Takes orders from stakeholders without authority to decide.
• The Scribe: Does not lead value, just writes down requirements.
• The Absent PO: Unavailable during the Sprint.
• The Gatekeeper: Blocks team from talking to users/stakeholders directly.

References

• The Scrum Guide (Scrum.org)
• "Product Mastery" by Geoff Watts
• "User Story Mapping" by Jeff Patton