Maintenance as a release cadence, not firefighting

Live systems need a release cadence that honestly prioritises security, features and debt. In the workshop we shape a care plan that fits team size, SLA and architecture — instead of slipping back into emergency mode.

Marc Hillen shows how Bitbrew organises maintenance in projects: branching, test depth, dependencies and stakeholder communication. You leave with a concrete cadence and backlog logic for the months ahead.