Whose Scrum Is It? — Scrum Development That Includes All Stakeholders, Not Just the Development Team
summary
Argues that Scrum is deliberately incomplete and fills the gap by adding a regular stakeholder ritual: a timeboxed post-daily meeting called an "お便りコーナー" held twice weekly with the PO and a prewritten agenda. Describes using this practice on the STORES Brand App (a B2B2C SaaS) where after ~15 sprints it enabled face-to-face stakeholder interactions, and by sprint 53 improved shared product knowledge, highlighted sales/support urgencies, prompted developer questions, and reduced risks from misaligned value.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:27Scrum’s intentional incompleteness
- 3:14Stakeholder plug-in approach
- 5:23Value and external perception
- 7:13Learning from external environment
- 8:35Risks of direct engagement
- 9:37Weekly stakeholder meetings
- 10:20Case study: Brand app team
- 12:52Tuckman model and trust phase
- 14:59Summary and benefits
- 15:20Q&A
related talks
20mFacing Our Organization's Philosophy with Scrum
15mAdvanced Scrum techniques for optimal delivery
52mFragile development
01h 13mScrum for Executives, Leaders, and Your Boss
41mScrum@Scale
39mWhy Scrum Is So Often 'Failed' and Criticised
17mScrum: I Came, I Saw, I Don't Want It
43mEver Since We Started Doing SCRUM Everything's Great. Not!