A Scrum Master story
summary
A company of ~80 people gets a week-long company hackathon with explicit rules and two weeks prep; 16 developers plus marketing, operations and customer service join in, running about a dozen to two dozen projects. Teams deliver small UX and booking-system improvements and ship roughly 24 features released and an eco prototype accepted by the owner as proof of concept. Result: high attendance (people bring kids), concrete releases by Friday, stronger cross‑department buy‑in and a management commitment to allow staff time for future hack days.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 3:16From campsite to tech company
- 10:31Motivating change in teams
- 14:07Hackathon experiment
- 19:10Hackathon results and insights
- 24:13Company-wide impact
- 27:36Scaling agility
- 31:20Scrum Master role in organization
- 33:48Management support and growth
- 38:22Q&A and closing
related talks
35mScrum Overview
16mSmall Scale Scrumming
15mAdvanced Scrum techniques for optimal delivery
05mThe Case For Longer Hackathons
05mScrumming Solo No Scrum Master or Product Owner
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
54mEffective SCRUM in Distributed Teams
21m600 Days of LeSS: A Practice Chronicle