Great responses and don't forget to actively identify, manage and mitigate risks all throughout the project. Nian; has a great idea to use risk register.
Its a continuous exercise. Discussions and reviews with the stakeholders will assist in identifying potential risks and impacts. It is their business, I value their input. I can add relatable input from an IT perspective based on decisions and chosen paths.
Great thanks Andrew Saving Changes...
Aejaz ShaikhPM I| Alyx Technologies India Pvt LtdPune, Maharshatra, India
True, creating risk register to record all the risk is a great idea. And also as mentioned above there is no single method to identify risks. We can start identifying risk right from the Project Charter, WBS, Project Scope Statement and then while executing work one need to monitor/mitigate the already identified risks as well identify new ones.
Product Operations Program ManagerBarcelona, Cataluña, Spain
In addition to all previous comments, it is also important (and time saving) to use the historical list of risks for similar projects. If a Risk Breakdown Structure has been done in past projects, then risks may be classified into Organizational, Technical, Financial, etc. which might make easier to pick out for on-going/future projects.
...
1 reply by Eduin Fernando Valdes Alvarado
Mar 09, 2017 7:09 AM
Eduin Fernando Valdes Alvarado
...
Eduard great thanks
Saving Changes...
Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
As a final check for risks, I review each task and thin "What could I do to sabotage this task?" I find it helps change my perspective, which helps me see risks I previously overlooked.
Good question
The following aspects to be taken care.....
1. To check project/program/portfolio related risks
2. To check with team by briainstroming method
3. Organisation level/team level (new technology, training etc)
4. Earlier project risk from peer team
Through this exercise, potential risks are identified and mitigated for the project.....
I don't think there's a single best way to identify risks across every project since each one is different from every other, but there is probably a best way to identify risks for each particular project.
That said, I often use detailed workflows depicted in swimlanes to identify project risks. I step through the workflow in a literal fashion and ask myself "What will the result be if this happens as stated?", or "What happens if I get result B instead of the expected result A?" In this way I can often identify risks that others don't consider. Also, I share the workflows with others; this makes it easier for people to consider project risk in a collaborative manner.
Nice approach Eric, and i think you could also take a look at the external risk factor, like market conditons and law regulations. That said, the approach is pretty dependent on the business segment tyou are in and the external factors may prevail. Cheers,
The best way to identify risk to have everyone who has a stake (passively and actively) in the project involved. Everyone has their own perspective which can add value in identifying opportunities and threats.
True, creating risk register to record all the risk is a great idea. And also as mentioned above there is no single method to identify risks. We can start identifying risk right from the Project Charter, WBS, Project Scope Statement and then while executing work one need to monitor/mitigate the already identified risks as well identify new ones.
Community Champion
