What if I'm not sure what is the risk (I don't know what I don't know and sometimes I don't know if it's a risk). Do you have any idea how I can handle this better?
That’s a great question, Syahirah. And I think “I don’t know what I don’t know” is actually a good place to start testing.
I wouldn’t try to identify every risk upfront. Start by asking questions:
What assumptions are we making?
Who could be affected if this goes wrong?
What would surprise us?
What dependencies do we know very little about?
Then talk to developers, product people, support, users, whoever has a different view of the product. They will often see risks you cannot see from your position.
Explore the product too. What you learn while testing changes what you consider risky.
Risk discovery isn’t something we finish before testing. It is part of testing.
You’ll never know everything. The goal is to keep reducing what you don’t know.
What if I'm not sure what is the risk (I don't know what I don't know and sometimes I don't know if it's a risk). Do you have any idea how I can handle this better?
That’s a great question, Syahirah. And I think “I don’t know what I don’t know” is actually a good place to start testing.
I wouldn’t try to identify every risk upfront. Start by asking questions:
What assumptions are we making?
Who could be affected if this goes wrong?
What would surprise us?
What dependencies do we know very little about?
Then talk to developers, product people, support, users, whoever has a different view of the product. They will often see risks you cannot see from your position.
Explore the product too. What you learn while testing changes what you consider risky.
Risk discovery isn’t something we finish before testing. It is part of testing.
You’ll never know everything. The goal is to keep reducing what you don’t know.
Thank you for sharing Deepak 😀