How can you reduce risk when implementing agile development in your SDLC?
Sideshow designs, manufactures, and distributes exclusive pop culture figures, statues, and high-end items. They are known for their collectible properties, including characters and elements from Star Wars, DC Comics, MARVEL Comics, Terminator, Predator, Disney, and more. Fans around the world rely on Sideshow for the latest and greatest collectibles around the world.
I spoke with Marc Hawkins, Ecommerce Implementation Manager, about Sideshow's development and bug-fixing processes.
Read the whole case study here.
Marc told us that initially his team was able to handle most QA manually on their own. Once the mobile world opened up, for ecommerce in particular, it became more and more difficult to maintain a comprehensive approach to testing given all of the devices out there.
“It became a pain to test, to run another couple tests that we didn’t have time for.”
Extended regional and device coverage with test IO has bolstered confidence and has been instrumental in international efforts, as both device coverage as well as awareness of geographically based issues have been enhanced.
“Features such as screencaps are invaluable; the reports are detailed, succinct, and show us exactly what went wrong.”
Interested in learning more about how different companies work with test IO and use crowdtesting? Visit the Customers page for more case studies and stories.
How can you reduce risk when implementing agile development in your SDLC?
What are bug reproductions, and why do they matter? Could you be missing out?
