What you can take control of.

If you are not looking at risk, then it is likely you are increasing costs in the development life cycle and putting your production environment in jeopardy.

The parts to play are identifying, assessing, mitigating and prediction.

What can help you?

1. Look at historical data!

What issues are you finding during sprint, regression, and what customer issues are being reported? Are there any patterns? Any product areas that continually have a high number of issues?

2. Use the risk matrix to assess.

Google the risk matrix — there is a tonne of information out there, but here’s an example:

Image for post
Image for post

3. Whole team approach to risk-based approach.

Make sure everyone in the team are contributing to the discussion in those refinement/planning meetings or during sprint work. What I have found important is the close connection between a developer and tester. A developer calling out what they’re changing in the code and the tester questioning/using their experience to dig in either further.

4. Customer focus

Focus on the customer — what do they care about the most in your product? What would could massive disruption if there were issues? How are they using your product?

5. Be kind to yourself

Although we want to mitigate ALL the risks — there is never enough time. So be kind to yourself by focusing on the risks that are most important to mitigate.

6. Have fun!

Enjoy the risk based approach. It saves so much time and energy by preventing issues, rather than reacting all the time.

Written by

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store