Baking Boards: Tweak the Recipe for Agile Development
summary
JetBrains shows concrete board recipes: product team moves to continuous delivery with two-week sprints, adds designers and testers as visible tasks, limits any task to three-day task limit, surfaces critical issues in a priority support swimlane, and uses an internal backlog project — result: four major releases, >90% sprint completion, ~50% fewer reported bugs. Documentation uses version-based sprints with in review and published states and delivers on schedule. Marketing uses a single-column, no-sprint board; design uses three-month seasonal sprints and per-designer swimlanes; the IDE team runs Kanban with WIP limits and automated stage assignment. Tools must be customizable to fit the process.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 2:25Agile challenges and goals
- 5:20Utrecht team’s agile process
- 16:52Documentation team’s workflow
- 20:07Personal task management example
- 24:21Design team’s seasonal sprints
- 28:41CLion and UpSource Kanban
- 32:17Key agile principles at JetBrains
- 35:29Tool customization and flexibility
- 36:35Resources and closing remarks
- 37:22Q&A on combining practices
related talks
40mAgile Software Development: Practice and Analytics
08mLightning Talk: A Tale of Two Spirits
34mNative Agile Psychology of Teams and Individuals
18mAgile leadership and technical mastery, a harmonious alliance
41mProduct Owner & Developer: An Unexpected Journey
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
11mLeading Agile Teams to Success: Lessons from the Trenches
47mMinimum Viable Process