Business as usual: how to stop drowning and learn to swim
summary
Shows that BAU consumes 20–100% of team time, once blocking a project for 12 months, and that the team released a new online publication platform a year after prioritising work. Describes a simple kiwi rota that spreads knowledge, finds contracting fails without good docs, pushes incremental Jenkins automation, and runs regular two-week consolidation sprints (target one per quarter ≈ eight weeks/year). Creates a technical support engineer role whose explicit goal is to automate routine work and transition into full development.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:59Why is BAU a challenge?
- 3:36How do I know?
- 6:34A kiwi?
- 8:59Deluged by BAU
- 13:43All change, please
- 14:33Documentation
- 15:50Simplification
- 20:55Consolidation
- 23:51A New Hope (for BAU)
related talks
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
05mKill the Project. Build a Team.
35mThree Steps to Change: Lessons from Battling Bureaucracy
51mThe subtle art of supporting mature products
06mIgnite: Escaping the Black Hole of Release Management
52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & Scrum
18mTackling tech debt
05mIgnites- Escaping the Black Hole of Release Management