Thread 5 - no ownership definition of done breakdown
Platform
Link
Post Text (Key Excerpt)
Essentially, I’m moving mountains to get any work item done.
The devs said the work was done, but it was not merged and the functionality was broken.
Every ticket is like this, and every dev is like this.Why It Matches Ryva ICP
This is severe ownership ambiguity plus execution drift, not a vague productivity complaint. It shows work falling through cracks despite tickets, sprint structure, and stated DoD.
Underlying Problem
No enforced shared ownership of delivery state, so “done” and “working” diverge repeatedly.
Suggested Public Response (Copy)
This reads like a system failure, not an isolated ticket quality issue. When ownership, DoD enforcement, and escalation paths are unclear, teams optimize for ticket closure instead of shipped outcomes.Suggested DM Idea (Copy)
Your example has all the signs of ownership collapse (state says done, reality says blocked). If useful, I can send a practical “done-state” checklist that ties merge, behavior, and reviewer accountability together.Snapshot
- Subreddit: r/agile
- Author: u/AtWitsEnd1974
- Posted: 2026-03-25 (18h ago at capture; within 14 days)