Finding the Rhythm: Agile and Open Source Development in Harmony
summary
Argues Scrum can coexist with open source by treating the community as an external dependency and controlling only what the team can finish: break large features into sprint-sized subtasks, copy relevant fields into an epic, and reserve capacity for unpredictable reviews. Describes a Python + Jira automation that creates epics, generates labeled upstream task and QA subtasks, and performs a daily sync from upstream (GitHub/GitLab/Pagure/Bugzilla), used on ~15–20 projects to cut double‑accounting and surface upstream effort for capacity planning.
AI-written summary · about
chapters (23)
- 0:00Agile and open source harmony
- 1:25Rigid Scrum problems in open source
- 3:34Scrum for upstream dependencies
- 5:21Scrum as rhythmic framework
- 6:26Tuning upstream noise control
- 8:10Room for unpredictable upstream work
- 8:32Iterative task breakdowns
- 9:36Subtasking large features
- 10:17Automating task tracking
- 11:22Syncing upstream issues
- 13:10Demo: task splitting & automation
- 20:41Key lessons for Scrum & open source
- 21:44Flexibility in Agile adoption
- 22:48Q&A: Sprint visibility & task breakdowns
- 23:38Q&A: Automation tools details
- 24:21Q&A: Story points & velocity
- 25:40Q&A: AI-assisted task breakdowns
- 26:40Q&A: Enabling automation in projects
- 27:48Q&A: Handling upstream unpredictability
- 28:51Q&A: Auto task generation
- 30:28Q&A: Shippable increments
- 31:51Q&A: Tracking community issues in Jira
- 33:05Closing remarks
related talks
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
40mProject Management on GitHub
27mDesign Your Open Source Project
21mScaling Internal Collaboration with Open Source Operating Models
39mSolving (team) dependencies - the Open Source way
52mBottom-Up Open Source Culture
40mHow to Open Source a Project and Possibly Not Fail While Trying
20mA guide to Indie Open Source Software