Product Owner & Developer: An Unexpected Journey
summary
A practical recipe for improving delivery: use a ticket backlog and break epics into day-sized user stories with clear acceptance criteria, run two-week sprints with planning, demo and retrospective, and reserve a 20% capacity buffer for unplanned work. Employ a visible pipeline or ticket tool, enforce automated tests and small deployable increments, and rotate on-call responsibilities (example: logistics support across 6–22 shifts) to reduce context switches and help developers focus on shipping.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:40Software plans matter
- 6:10Collaboration tools
- 12:14User stories & criteria
- 15:05Sprint planning
- 22:10Product Owner role
- 27:21Teamwork & demos
- 30:40Retrospectives
- 35:02Lessons learned
- 36:26Summary & Q&A
related talks
36mDEVELOPER ORIENTED PROJECT MANAGEMENT
49mBaking Boards: Tweak the Recipe for Agile Development
41mChallenges of product owner in a new agile team
40mAgile Software Development: Practice and Analytics
48mHow to Win and Start Contract Development Projects That Leverage Agile Values
32mLessons Learned from 7 Years of Running Developer Platforms
18mNavigating the Dev's Journey: Crafting an Effective Roadmap for Success
34mHow to effectively communicate to Developers/PMs - A guide for developers and project managers