Yes, you need time for bug fixes
“We don’t always test our code – but when we do – we do it in production.”
This common saying perfectly describes at least one project, that everyone heard of. Legacy code, years of bad practices, thousands of end-users. This paper won’t be a thrilling story about zombies, but a short presentation describing how to learn from your mistakes.
What if some of the bugs might be foreseen at the beginning of the development, so we are able to prepare ourselves? Shall we try? Time matters – especially if there is a fixed deadline. The presentation is based on a project ina rush and tries to provide lessons learned from it.
It will also require some interaction from the audience – we’ll try to play around time and team sprint. Everyone is highly recommended to bring joy and good mood with him. In return, it is possible to be filled with some tips and tricks to improve your planning sessions and save time for the unexpected.
In return, it is possible to be filled with some tips and tricks to improve your planning sessions and save time for the unexpected.
A girl in IT. Kinga Witko is an experienced software tester who fell in love with agile methodologies. Cat-lover. Fantasy books fan.
She works as a Software Tester for 4 years now, introducing good quality into code. She believes that any software is bug-free. She used to work in web, mobile and data warehouse projects, now she begins her adventure with NewVoiceMedia.
She is interested in user experience and its implementation in making great applications. Kinga is also curious about novelties in astronomy and new technologies.
Kinga tries to share her project and testing – related experiences on various events and conferences.