Interview with – Michael Wansley
summary
A sustaining team at Tableau Software handles bugs from released versions rather than feature work and struggles to keep a growing bug backlog from disrupting sprint planning The team experiments with carving out two days out of a two-week sprint or three days out of a three-week sprint strictly for fixes but finds this skews burndown and estimation The working practice that stabilizes flow is to schedule dedicated bug days and include explicit estimates for fix, verification, regression, interoperability and localization work
AI-written summary · about
related talks
42mFostering New Contributors In SWT: Lessons In Community Management
26mEnhance Developer Experience by community
22mPanel Discussion: The 5 Ws and...
08mBelinda Waldock - Software Cornwall - Tech Connect Lightning Talk, Software Cornwall
09mCaitlin Gould - Bluefruit Software - Tech Connect Lightning Talk, Software Cornwall
28mBuilding Thriving Communities in Platform Engineering: Collaboration, Innovation, and Growth
39mMaintaining a big open source project: lessons learned
05mLightning Talk: Sprints
