Mario CoquillatProject, Program and Portfolio consultant, mentor and trainer| CoquillatPMSan Pedro Del Pinatar, Murcia, Spain
Some practitioners consider that agile manage risks implicitly through a variety of practices (Continuous Delivery, Automated Testing, short iterations).
Other practitioners consider necessary to manage risks explicitly using practices as Spikes, ROAM and Risk Breakdown Chart.
Your insights would be much appreciated. Saving Changes...
I consider that the best approach in agile is to work with the kanban board including risk (or the different response plans -activities- to be done in order to attack them). So that the team can visualize and priotize them, exactly the same as any other user story.
On the other hand, I also think that having a risk register where the risks can be handed propertly is mandatory. Saving Changes...
Mario CoquillatProject, Program and Portfolio consultant, mentor and trainer| CoquillatPMSan Pedro Del Pinatar, Murcia, Spain
Thanks Angel
So you´re talking about a hybrid approach, both in Kanban (agile) and risk register (predictive). That´s a good point. Saving Changes...
"Impartial observers from other planets would consider ours an utterly bizarre enclave if it were populated by birds, defined as flying animals, that nevertheless rarely or never actually flew. They would also be perplexed if they encountered in our seas, lakes, rivers and ponds, creatures defined as swimmers that never did any swimming. But they would be even more surprised to encounter a species defined as a thinking animal if, in fact, the creature very rarely indulged in actual thinking."
