agile-product-owner

User stories meeting INVEST criteria are generated by defining the feature requirement, structuring the narrative, and applying the INVEST checklist to ensure the story is independent, negotiable, valuable, estimable, small, and testable.

Acceptance criteria using the Given-When-Then format are defined by specifying the initial context (Given), the triggering action (When), and the expected outcome (Then) to clearly verify user story completion.

Sprint planning and team capacity calculation are executed by evaluating team velocity, determining available hours, and loading user stories from the prioritized backlog until capacity is reached.

Large epics are broken down into manageable user stories by decomposing the overarching feature into smaller, actionable units that adhere to agile INVEST criteria for accurate estimation.

Backlog prioritization and velocity tracking are supported by evaluating story value and dependencies for ordering, while monitoring completed story points across sprints to measure team velocity.

An agile product owner's role in sprint execution and backlog management involves prioritizing the backlog, writing clear user stories, defining acceptance criteria, and facilitating sprint planning to optimize team capacity.