Estimators of the Lost A.R.C. - Advance Recon Crew
summary
A team-within-team runs pre-scoping technical spikes using a design sprint from the Open Practice Library to vet options, identify dependencies and give development-ready recommendations in one to five weeks. Work on Fedora Messaging Notification, Bodhi, webhooks and activity account scripts cuts message lag and avoids rework. The process produces 17 finished investigations and results in 7 projects delivered on time, clearer estimates, fewer surprises and documented options and tradeoffs for each initiative.
AI-written summary · about
chapters (11)
- 0:00ARC team origins
- 8:04ARC heroes and villains
- 11:20ARC investigation process
- 13:09Live ARC investigation demo
- 16:40Real ARC investigation cases
- 19:14Fortune from ARC investigations
- 22:45Team benefits and planning
- 25:11ARC feedback and future plans
- 26:37ARC for smaller teams
- 30:09ARC investigation rules
- 33:00Q&A
related talks
52mToo many cooks! Supporting augmented teams without getting salty
32mStrength Training for RHEL Lightspeed: Building Agility, One Rep at a Time
40mAgile Software Development: Practice and Analytics
18mAgile leadership and technical mastery, a harmonious alliance
26mAgility Works Only If You Are Truly Agile...
45mUnlocking High Performing Teams with Open Source
44mEnhancing the Performance of Engineering Teams
20mBuilding High-Productivity Teams Focused on Outcomes: Team Design and Collaboration Case Studies