A presentation at Agile Cambridge 2023 in in Cambridge, UK by Areti Panou
Building up the confidence to release Preparing to Preparing to avoid errors handle errors
Have we tested enough?
Did we do everything that we had to do?
From To Our software cannot contain code with GNU General Public License No findings reported after running the Foss scan - check results The new feature is tested Our pipeline is successful, and the feature is explored exploratory charters Documentation is in place Documentation has been added to the guide and the FAQ
Check the Done criteria before starting the implementation
What happens when someone reports an error?
email website help button chatbot ticket
How can we find unreported errors?
Try to connect to user satisfaction or retention to justify the effort
Building up the confidence to release Preparing to avoid errors Documenting what we know we have tested Making the best of our done criteria Preparing to handle errors Streamlining our support process Monitoring key functionality
Building up the confidence to release Preparing to avoid errors Documenting what we know we have tested Making the best of our done criteria Preparing to handle errors Streamlining our support process Monitoring key functionality A culture to speak up when in doubt The whole team is aware and takes care of the guardrails
Releasing new functionality to our users can be stressful, but it doesn’t need to be. Learn how to set up, use, and continuously improve practices that increase the confidence of your entire team in the quality of your changes.
for free. You
can too.