Rights and Responsibilities of a Delivery Team
summary
Only one project works as expected out of 14 years of agile experience, and the claim is that friction comes from unclear team ownership and missing rights paired with matching responsibilities. Delivery teams must be seeded by a sponsor, include business and tech together, and own backlog, hiring and process while being accountable to stakeholders; they should define their own composition, control time or scope, and use hypotheses and measurable outcomes instead of output metrics, with RACI/CEMET as practical tools.
AI-written summary · about
chapters (8)
- 0:00Start
- 8:23managing the product backlog
- 23:01grow the rest of the team according to the needs
- 24:06define their own composition
- 40:54work with respectful teammates
- 44:39use the raci matrix
- 48:18start with signals
- 48:57create a hypothesis
related talks
36mMine! Yours! None! Responsibility in Agile Teams
01h 01mHow Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
32mBuild Teams as an Engineer
49mAccountability – The Evolution of Responsibility
49mDelivering with Self-Organized Teams — Real, Fast + Good
47mAgile experience in changing environments and the challenges faced
05mFrAgile - lessons from a failed agile transformation
25mHow to get your derailed agile transformation back on track