Project Management

Please login or join to subscribe to this thread

Data gathering techniques in risk identification

linkedin twitter facebook  
avatar
JOONMIN SUH Project Engineering Manager| Samsung Construction & Trading Seongnam, Gyeonggi, South Korea
The first step of risk identification is data gathering followed data analyzing.
A range of tools and techniques for risk identification, especially for data gathering, are 1)Historical Review (Past), 2)Current Assessments (Current) and 3)Creativity Techniques (Future).
A wide range of Creativity Techniques can be used to develop a comprehensive list of all knowable uncertainties.
What are you favorite Creativity Techniques like "Brainstorming", "Interview", etc. for gathering the data?
Sort By:
< 1 2 3 >
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
This is inside the Elicitation activities. Elicitation belongs to business analysis field but from the new PMBOK you can find it when talking about project requirements mainly. My recommendation about a list of techniques is taking a look to Business Analysis Practice Guide or the new Business Analysis Guide. Search into Elicitation knowledge area.
...
1 reply by JOONMIN SUH
Dec 04, 2017 1:00 AM
JOONMIN SUH
...
Yes. I've just downloaded the latest BA Guide to look into related section.
Thank you for your recommendation.

Joonmin
avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
I would go for Expert Judgement and/or Delphi Technique to start with. I guess both tools will help you to identify risks in projects.
avatar
JOONMIN SUH Project Engineering Manager| Samsung Construction & Trading Seongnam, Gyeonggi, South Korea
Dec 01, 2017 5:06 AM
Replying to nwosuocha uchenna
...
you are on the right track
Thanks your applause :-)
avatar
JOONMIN SUH Project Engineering Manager| Samsung Construction & Trading Seongnam, Gyeonggi, South Korea
Dec 01, 2017 5:52 AM
Replying to Craig Brodbeck
...
Ideation tools such as SCAMPER, MIND MAPPING, BRAIN WRITING, SIX THINKING HATS, SWOT, and PESTLE could be of some help for risk identification.
Hi Craig,
It's very impressive, still there are many other risk identification techniques which were not mentioned in the practice standard for project risk managemen except SWOT.
Thanks alot.
avatar
JOONMIN SUH Project Engineering Manager| Samsung Construction & Trading Seongnam, Gyeonggi, South Korea
Dec 01, 2017 8:04 AM
Replying to Kiron Bondale
...
I'd second Craig's support for brainwriting as it overcomes some of the deficiencies of brainstorming.

Another approach I've used is to ask stakeholders to envision themselves as "hackers" trying to break the project to have them come up with ways in which this could occur.

Kiron
I have just reviewed the "Brainwriting" and totally agree yours.
Thank you.

Joonmin
avatar
JOONMIN SUH Project Engineering Manager| Samsung Construction & Trading Seongnam, Gyeonggi, South Korea
Dec 02, 2017 6:17 AM
Replying to Sergio Luis Conte
...
This is inside the Elicitation activities. Elicitation belongs to business analysis field but from the new PMBOK you can find it when talking about project requirements mainly. My recommendation about a list of techniques is taking a look to Business Analysis Practice Guide or the new Business Analysis Guide. Search into Elicitation knowledge area.
Yes. I've just downloaded the latest BA Guide to look into related section.
Thank you for your recommendation.

Joonmin
avatar
Bang Yang PM I| shenzhen Dongguang, China, Mainland
Hi,
that is a good qestion, I think the risk should be datamation then we can analysis it easily and more correctly. but sometime the risk come from person or people relationship. that need you have experiences and sensitive feeling. like those risks need your personal ability I think. that is my opinion.
...
1 reply by JOONMIN SUH
Dec 04, 2017 6:22 PM
JOONMIN SUH
...
Thanks your opinion, I like it. In addition, leadership and communication skill with stakeholders are the key ability to capture the risks coming from the person what you mentioned.
avatar
Vincent Guerard Coach - Trainer - Speaker - Advisor| Freelance Mont-Royal, Quebec, Canada
All good suggestion for gathering risk information from stakeholders.

Not to forget you schedule/planner, you should perform a review of the schedule. That can be done manually. a simulation software would give you additional information on risk hidden in the schedule.
...
1 reply by JOONMIN SUH
Dec 04, 2017 6:16 PM
JOONMIN SUH
...
Your comment always expands my horizons.
Thanks alot.
avatar
JOONMIN SUH Project Engineering Manager| Samsung Construction & Trading Seongnam, Gyeonggi, South Korea
Dec 01, 2017 8:20 AM
Replying to Mansoor Mustafa
...
from my point view expert interviews provide you direction and guidelines for identifying risks in projects
I like your comment.
avatar
JOONMIN SUH Project Engineering Manager| Samsung Construction & Trading Seongnam, Gyeonggi, South Korea
Dec 02, 2017 1:02 AM
Replying to Emmanuel Nya Paye
...
Technically, you have to assess what your perceived risk plan indicates. You secondly need to ask yourself if the process is in control or out of control. In this way, you can easily identify what the exact risks are. It would look weird to jump and start collecting data if your reason or reasons are not compelling.
Thanks for your kind comment. The focus of this discussion is data gathering just before the analysis the aquired data if that is risk or non-risk by evaluation. Anyway, I like your comment to identify the exact real risk.
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

A conference is a gathering of important people who singly can do nothing, but together can decide that nothing can be done.

- Fred Allen

ADVERTISEMENT

Sponsors