Agile from the Open Source Trenches
summary
Wikipedia Foundation runs Agile with under 100 engineers (about 75–80 devs and ~25 Ops), uses Git and GitHub plus non‑open tools like Mingle, and supports 286 languages. Teams use two-week sprints and push an overall release every week, reserving 20% fun time for pet projects. Concrete pain points: poor user‑story detail, insufficient acceptance criteria, weak backlog grooming, distributed timezones and resource negotiation that delay code review and deployment.
AI-written summary · about
chapters (12)
- 0:00Agile in open-source
- 3:20Wikipedia’s engineering challenges
- 10:26Agile in open-source culture
- 12:52Roles in Wikipedia’s Agile
- 17:29Wikipedia’s Agile process
- 24:31User stories and criteria
- 27:43Volunteer contributors in Agile
- 31:41Backlog and maintenance issues
- 35:12Cross-team Agile knowledge
- 38:23Open-source vs production
- 41:20Distributed teams adaptations
- 46:18Q&A
related talks
34mNative Agile Psychology of Teams and Individuals
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
49mAgile is a Dirty Word
18mAgile leadership and technical mastery, a harmonious alliance
01h 01mAgile Evolution: An Enterprise transformation that shows that you can too
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
42mDistributed Agile Development
36mWhat Your Mother Never Told You About Agile Development