Okay, so, favourite methods, stories, experiments (failed and successful) on gathering risks from various parts of a team?
Background: I’m overhauling our automation, and want to figure out not only what I think the risks are for the product but what the devs and the product owner think are the risks. This will be helpful for automation and everythng else - I know where to put my efforts best when I know what the risks are.
I’ve suggested a risk storming session, but while I wait to see if that’s going to happen, I thought I’d tap into this resource as well
At the moment the product owner is thinking mostly in terms of the user path and what bits of that is critical, but I want to make sure we’re covering everything - performance if that’s a priority or stability or whatever.
There’s also a method around asking what headlines about the prduct would be that I’ve heard but my google skills are failing me in finding that one.
Let’s share tips