I think the most significant meaning of risk managament in scrum is that iteratively validate our assumptions by frequently releasing increment,please talk about how to start agile transformation in an enterprise company by using evidence base management in details.
"We don’t accumulate Risk We Retire Risk" Nice inspirational quote for a Linkedin post but you basically said nothing in particular. Do you do matrixes, do you invlove the whole team, do you involve the clients or upper management, do you look at risk only at the start of project, before every sprint, during the daily meetings, etc. , etc.? This is what people wish to know. Otherwise, they'll be a Nike T-shirt saying "Just do it".
You just named a bunch of ways you can, in fact, retire risk. You probably didn't even need the sarcastic LinkedIn comment or T-shirt reference you made to do it. The reality is risk is specific to the context that you find yourself in. A few examples though... We retire risk by shipping and validating we're building the right things. In the Sprint Review we create product transparency and retire the risk that not everyone is on the same page. The retrospective creates process improvements that retire risks in regards to people, processes, and tool improvements. Self-management retires the risk that decision making is taking too long and eliminates dependencies. There are many more ways... When leveraged well, risk retirement is inherently build into empirical process control (inspection, adaptation, and transparency) which is the fabric of the Scrum events and artifacts.
@@AgileforHumans Apologies if I sound too aggresive. But as agile coaches you need to provide more detail. Give an example from you work experience, draw something on the screen. You can earn so much more followers. And YT algorithn will boost your videos if they're longer. That way we all win. Cheers!
Love the videos, Love the narrative "Retire the Risk, not accumulate". But there are risks and issues which take longer to address or require managing/tracking. Is that ok? Do you manage it in a traditional RAID log (Like i do) is there a better way to do it?
Great episodes guys! Love listening to them. Just in addition to Risk and your comment 'retire the risk' would you be able to elaborate if there is any way to demonstrate RAID log within scrum?
Another good episode.
We don’t accumulate Risk We Retire Risk ... 👍🏻
Thank you Ryan and Todd.
Good episode !!!
Can you state an example for Risk management in scrum ?
Good session team.. can you please list some of the examples of risk management 🙏
Yay, Ginger! Looking forward to more special Ginger appearances.🥰
Ginger loves the attention 😊
I think the most significant meaning of risk managament in scrum is that iteratively validate our assumptions by frequently releasing increment,please talk about how to start agile transformation in an enterprise company by using evidence base management in details.
"We don’t accumulate Risk We Retire Risk"
Nice inspirational quote for a Linkedin post but you basically said nothing in particular.
Do you do matrixes, do you invlove the whole team, do you involve the clients or upper management, do you look at risk only at the start of project, before every sprint, during the daily meetings, etc. , etc.?
This is what people wish to know. Otherwise, they'll be a Nike T-shirt saying "Just do it".
You just named a bunch of ways you can, in fact, retire risk. You probably didn't even need the sarcastic LinkedIn comment or T-shirt reference you made to do it.
The reality is risk is specific to the context that you find yourself in. A few examples though... We retire risk by shipping and validating we're building the right things. In the Sprint Review we create product transparency and retire the risk that not everyone is on the same page. The retrospective creates process improvements that retire risks in regards to people, processes, and tool improvements. Self-management retires the risk that decision making is taking too long and eliminates dependencies. There are many more ways...
When leveraged well, risk retirement is inherently build into empirical process control (inspection, adaptation, and transparency) which is the fabric of the Scrum events and artifacts.
@@AgileforHumans Apologies if I sound too aggresive. But as agile coaches you need to provide more detail. Give an example from you work experience, draw something on the screen. You can earn so much more followers. And YT algorithn will boost your videos if they're longer. That way we all win.
Cheers!
Love the videos, Love the narrative "Retire the Risk, not accumulate". But there are risks and issues which take longer to address or require managing/tracking. Is that ok? Do you manage it in a traditional RAID log (Like i do) is there a better way to do it?
Great topic!
Great episodes guys! Love listening to them. Just in addition to Risk and your comment 'retire the risk' would you be able to elaborate if there is any way to demonstrate RAID log within scrum?
Great show guys! Thank you
Also, can you please mention a couple of real examples with respect to risk management 👍
I thought Todd had a "How you doin'...?" kind of voice. Be on your guard, Ryan! 😀
Excellent ..