RiskStorming workshops
Whole-Team Quality Responsibility.
Risk Analysis.
An Integral Part of any Quality Coach’s toolset.
RiskStorming workshops, now Online!
Interactive & Asynchronous
Why RiskStorming?
Online RiskStorming
- Deliver quality cost-efficiently
- Identify high value risks
- Make quality a team responsibility
How it works
Phase 1 – Choose Quality Aspects
Phase 2 – Identify Risks
Phase 3 – Dealing with Risks
Phase 4 – A Plan
Let us help you get started
Pricing Plans
Explorer
- Includes phase 1 & 2
- Use Testing-focused card deck
- Share app on video-call
- No interactivity
- Nothing is saved
Quality Coach
- All aspects of RiskStorming
- Interactive features
- Asynchronous preparation
- Analysis, Architecture, Testing & Operations cards
- 5 Saved sessions
- 5 Moderator users
- PDF exports
- (5 Customisable decks)
- (Create your own cards)
- Supports English, Spanish & German
Expert Workshop
- Moderation of a RiskStormingOnline session by our experts on your product
- 2-4-6 hour packages
- Create a quality strategy
- Learn how to run your own RiskStormingOnline sessions in the future
- Includes the Quality Coach package
Who are we?
KZA B.V.
Netherlands
Dutch, English
Ard Kramer
Rotterdam, Netherlands
Dutch, English
oose
Hamburg, Germany
German, English
Beren Van Daele
Europe
Dutch, English
Vernon Richards
Leicester, UK
English
Andrea Jensen
Germany
German, English
General Questions
FAQ
When is the best time to do a RiskStorming Online Workshop?
Alternatively, you can run RiskStorming workshops later than this, but you might not enjoy the outcome as much. Risks could be identified too late for good countermeasures to be taken. Instead of not building a risky feature, you may be stuck with spending hours of testing it.
Then again, forewarned is forearmed, the earlier the better.
How long does a session take?
The shortest session we’ve run was 1 hour. People knew what the subject matter was and how the team worked. The discussions were much more targetted and the outcome absolutely stellar.
Your milleage will varry. Count between 2-3 hours to do it effectively for the first time.
Who should be present?
The long answer: It depends on the context of your project. Look for people who have deep understanding of the business, the architecture and which negative scenario’s could happen. Some projects are marketing heavy, others are very data dependent, invite those who’ll give you good ideas on where the value is and what you need to protect.
Look for four types of people: a business expert, an architectect/developer with broad skills, someone with a tester mindset and someone with experience in running applications in production. This kind of team will come up with the most well-rounded strategy.
Contact
Let’s work together!
RiskStormingOnline is a product built by many beautiful minds. Your point of contact is Beren Van Daele who helps the team with which step to take next. He’ll gladly help you out and have a chat with you.
beren@isleof.it
calendly.com/berenvd
Our History
Ministry of Testing offered to fund & cocreate the cards together with multiple members from the community.
Several months later TestSphere was born.
TestSphere is a card deck that gets people thinking and talking about Quality & Testing.
It became quite popular in the testing field, with decks going across the globe to help people improve their understanding and quality of the project.
RiskStorming is a hands-on workshop that was created through experimenting with TestSphere by Andreas, Marcel & Beren.
This brought us to where we are now: on a journey to spread RiskStorming beyond the software testing craft and into analysis, development, architecture and operations too, so you’re better equiped to deal with your important risks.
Testimonials
At eBay, we use RiskStorming regularly before we start a new project. This helps us to generate a common understanding between the different stakeholders, increase the understanding of what’s important to different people, and of course identify risks. We usually identify lots of new risks that we haven’t thought of before and we can then decide as a team how to mitigate them. Overall, I can highly recommend using RiskStorming in your project.