To ensure quality while addressing demands for rushed software updates, adopt a risk-based approach. Prioritise critical features and high-risk areas for thorough testing while using automation for repetitive tests to save time. Implement feature flags to deploy updates incrementally, enabling controlled rollouts and immediate rollback if issues arise. Engage cross-functional teams to review changes collectively, leveraging their expertise to catch potential flaws early. Conduct parallel testing in production-like environments and involve end-users in beta testing to gather real-world feedback quickly.

We must take into account the tools themselves and put them into practice since the demand is greater than the work itself. Know your KPI.

The need to quickly run a software update often indicates an urgent reaction to an issue with high levels of risk and impact. To maintain quality without impacting testing requires amongst other factors: 1) Close collaboration with relevant stakeholders before, during and after the update. 2) Logging known software vulnerabilities in the automated risk register to trigger continuous impact analyses and mitigation during update. 3) Safe data backup and secure restore points prior update. 4) Ensure all systems, infrastructure and devices are configured with appropriate specifications. 5) Communicate eminent system disruptions with all users and stakeholders. 6) Circulate contingency, backup and continuity plans to minimise impact.