Work example · Product ownership
User Story Lifecycle
As Product Owner for an enterprise content management (ECM) program, I turned stakeholder needs into user stories with clear acceptance criteria, then moved them across a Kanban board from refinement to release. The board below replays that flow for the three themes that drove the backlog: getting content in, letting the right people get to it, and moving it off legacy systems.
RoleProduct Owner
OrganizationECM
DatesJan 2023 – Jul 2024
FrameworkAgile Kanban
Watch a story move
Each card is an issue. The backlog fills from the left, the top-ranked story is pulled into Ready each cycle, and production bugs jump the line.
ECM backlog boardIllustrative sample data. Issues, labels and weights are randomized for this demo.
0stories written0acceptance criteria defined0closed after UAT
New issue
Title
User story
Acceptance criteria
Labels
On a phone, swipe the board sideways to see every column.
How it works
One need in, one accepted feature out.
- Capture the need. Gather what stakeholders and customers need and frame it as a problem worth solving.
- Write the story. Draft the user story and its acceptance criteria so the team knows what “done” means.
- Refine and prioritize. Refine with the team, then rank it against production support and roadmap goals.
- Deliver and accept. Track it through development and UAT, fold in feedback, and close it once the criteria are met.
Where it fit
- Led backlog management and prioritization with cross-functional teams to deliver product enhancements.
- Kept the Agile Kanban team aligned with the product vision, roadmap and business objectives.
- Balanced high-priority production support with new features during legacy system migration and decommissioning.
- Built stakeholder feedback into stories and acceptance criteria before work reached the team.