How do you prioritise risks?

[simon_tomes]

Lots of helpful replies in this post about risks. Thanks to everyone who shared:

How do you document and communicate risks?

Is it a risky business to document risks? I’d like to hear your anecdotes and stories. How do you document and communicate risks? How do you tailor risks to the appropriate audience? What forms of documentation have you used? i.e. risk register, risk matrix, risk policy docs, etc How does documentation map to your testing efforts i.e. test cases, charters, etc Who tends to be the recipient of your documentation?

Let’s dive into the nitty gritty of prioritising risks.

What prioritisation techniques have you used? What did they look like and how did they help?

What pitfalls should we be aware of when prioritising risks?

Can we use generic prioritisation techniques in combination with risk assessment techniques? What risk and prioritisation combos can we create?

[kristof (Kristof Van Kriekingen)]

@simon_tomes

What prioritisation techniques have you used? What did they look like and how did they help?

Impact vs Probability. Quickly going to show some tables:

How to calculate the impact: (you can adjust this for your own project)

How to calculate probability:

And then you have something like this:

This is basically how we did it on my previous project. High gets fixed asap.
Medium is next sprint and low is often just backlog or if there is some time left.

[ezeetester (Guruprasad B Gopinath)]

@simon_tomes I believe specific examples in the impact scale example and a why could probably help