Quality is a word that creates divisiveness. It creates conflict and controversy. However, not all conflict is bad and this particular one is looming over our heads whether we face it or stick our head in the sand.
Whatever we choose to do, there will be a price to pay.
People often try to quantify risks. Any project with higher compliance requirements will tell you they estimate Likelihood and Impact, that they then put those in matrix and show which ones are minor, major or critical risks. Apart from helping you pass an audit, these practices also look nice and make you feel safer…
‘Feel safer’. No matter which process you use to quantify risks, it won’t ever remove that it’s all based on feelings.
The focus is on sharing ideas, extending helping hands and finding comon ground. If people have been saying ‘Quality is a Team Responsibility’, then this is the moment it actually takes shape.
Only now have your teammembers understood sufficiently what quality actually means and how they can work together, from within their roles, to achieve it.
Find out how your team can finaly craft a strategy and start working together on building quality after having gone through each of the RiskStorming phases.
Watch several awesome IT professionals do RiskStorming on Star Wars’ Deathstar.
Do I get enough value from RiskStormingOnline after 45 minutes? Not sure RiskStormingOnline is for you? You watched the videos, read the posts, maybe even participated in a workshop already, but all the information and moderation seems daunting? I know the feeling. Every workshop, I doubt myself. Do I know the context well enough? Will […]