Khushboo SinghProject Manager| Envestnet|YodleeBangalore, Karnataka, India
I have seen this with almost all the projects that programmers (developers, testers, architects, etc) do not like highlighting the risks well in advance. This becomes a major challenge.
During stand-ups I do prefer asking what risks do you see. Sometimes, it takes lot of time and effort to push them to speak up.
How can I ensure that all the internal stakeholders and participants do highlight the risk well in advance that we get ample time to resolve those?
In one such project, I did think through and found out one major risk which could put the entire project delivery at stake, but everyone else jumped in to say it is not that a major risk and can be avoided.
Later on, it became a road-block.
At that moment, I could have gone back and stated I did highlight this but that would not have had any impacts.
I did highlight this in retrospectives.
Developers, architects did concur and assured they would let us know the risks well in advance.
But I still do not see that happening.
Is there a different and proven way for finding out the risks pretty early in the process? Saving Changes...
