> every task needs a single person who is responsible for ensuring that task is done. Indeed. But "done" means different things to different people—to the dev

> every task needs a single person who is responsible for ensuring that task is done. Indeed. But "done" means different things to different people—to the developer, to QA, to deploy engineers, to devops, to the stakeholder. And more goes into a ticket than done/not done, that needs other people to chime in.