Sprinting & why your company needs to let you do it
summary
Contribution sprints are focused work sessions where people triage issues, write and test patches, and sometimes perform a live commit (often a small low‑risk change like a one-line CSS patch). Tools and workflows covered include local dev setup, applying patches, IRC/Slack mentoring, and trying new tooling such as visual regression testing. Outcomes range from updated docs and tested issues to module porting and performance tests (e.g., mass Twig template profiling) that ship later and improve agency knowledge.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:26Meet the speakers
- 4:02Sprint definition
- 4:59Why should you care
- 10:42Issues vs Sprints
- 17:54New to Drupal
- 21:44What should I bring
- 25:48Why agencies should do it
- 33:22Making mistakes is better
- 38:28Visibility
- 39:02Our favorite stories
- 42:36Reaching out
- 48:02Mentoring
related talks
05mSprints Introduction
40mAgile Software Development: Practice and Analytics
49mBaking Boards: Tweak the Recipe for Agile Development
40mSoftware Delivery - 10% time the pros and cons?
24mExpediency & Fluency
11mLeading Agile Teams to Success: Lessons from the Trenches
27m"Getting Started with Open Source Contributions"
47mThe Great Adventure of Open Source Contribution