TestToTester

" A picture is worth a thousand words" - well, who has not heard that before but as with most things simple we might not give it its due because it's easily understood.  In our team we have a pretty straight forward process to deal with bugs. I demo it to the dev, and add a sticky on the board for it to be fixed. Most of the time the fixes take priority, so we can move the stories across. It works well for our context. Today, when working from home I wanted to share a bug with my dev - list view loosing placeholder image data on scroll on android. I typed the steps to reproduce on slack and then followed it with the below image  The team loved it... ( Yea, you read that right! dev's loved the bug report ;) It was fun and made the point clear...  I bet it would look stunning on the kanban board compared to the long list of words on a sticky...

We have delivered over 20 builds to production in the last 12 months. (avg 15 stories per sprint) We have no show stoppers or major issues reported by end users. We have customised sprint + kanban to suit our team dynamics. We believe that a story is Done/Ready for sign-off when it's DEV + Test complete We pair up with Business for Story Kick-offs, grooming cards, demos, etc We pair up with Dev's for tech tasks, API tests & support/bug investigations We pair up with Dev Ops for infrastructure testing, build, deployment process We test functionality, integration, migration, UX, localisation, regression And YES We test most of our cards MANUALLY ( SBTM approach). to be continued...