Our Agile practitioners are struggling to find time for the community. How do we keep members consistently active in sharing Scrum best practices without causing meeting fatigue?
3 answers
The key is to move away from scheduled "meetings" and toward asynchronous "Value Bites." In my experience, Scrum Masters are already over-scheduled with ceremonies. If you create a space for them to post short videos or artifacts of their latest Sprint Retrospective, it sparks curiosity. We introduced a "Story Point Challenge" where members guess the complexity of a redacted user story. It turned learning into a game. You must ensure the community doesn't feel like a second job but rather a support system where they can vent and solve common Agile scaling bottlenecks together.
Are you providing any tangible incentives for those who contribute the most, or is it purely voluntary based on their own interest in Agile methodology?
Rotating the "Community Lead" role every month keeps things fresh. Different people bring different topics, from Kanban flow to DevOps integration, which appeals to a wider audience.
Rotation is a great idea, Gregory! It prevents one person from burning out and ensures the topics aren't biased toward just one aspect of the Scrum framework every week.
We currently don't have a budget for prizes, Justin. However, we are looking into "Shout-Outs" during the monthly town hall for the top contributors. Do you think public recognition is enough to sustain long-term engagement, or do we eventually need something more substantial?