Fire-inspection coaches treat hackathons as optional extras that disappear when stories slip. How should the Scrum Master / Team Coach protect Innovation and Planning?
Select an answer to reveal the explanation.
Short Explanation
A fire-inspection hackathon that only happens if nothing slipped is a spare hose sold at the first alarm. Innovation is a purpose of IP, not leftover scraps. Protect the time or the ART never learns a new tool.
Full Explanation
Innovation—including hackathons and Community of Practice learning—is a first-class purpose of the Innovation and Planning iteration, not an optional extra after delivery. Canceling it when stories slip, moving it to evenings, or requiring a Feature ticket all treat learning as leftover capacity. The Scrum Master / Team Coach protects innovation time so fire-inspection teams can experiment without waiting for a perfect PI. That protection is part of coaching IP, not a luxury.