Syncing Business and Development Norms in Sprint Review
summary
A Scrum team changed Sprint Review into a weekly business briefing where sales and support bring real consult logs and customer quotes (no slides), which led to prepared materials and active feedback. They then adopted split reviews—English for developers and Japanese for business—and transcribed the Japanese sessions in Zoom, using AI summarization of Zoom transcripts to send concise feedback to engineers, accelerating learning cycles and increasing engineer participation in user interviews.
AI-written summary · about
chapters (13)
- 0:00Syncing norms intro
- 2:33Sprint review problems
- 5:48Root cause analysis
- 7:33Engagement strategy change
- 9:22Adding business voice
- 11:53Scaling challenges
- 12:55Review separation
- 14:42Reintegrating feedback
- 16:31Business context circulation
- 17:35User interview access
- 18:16Information revitalization
- 19:17Feedback gap solutions
- 20:07Summary
related talks
16mSmall Scale Scrumming
35mScrum Overview
26mVirtual Scrum
40mAgile Software Development: Practice and Analytics
15mAdvanced Scrum techniques for optimal delivery
49mBaking Boards: Tweak the Recipe for Agile Development
36mDistributed & Local: Getting the Best of Both Worlds
54mEffective SCRUM in Distributed Teams