How often would you recommend to review the identification of risks in a project after its kick-off? This process after implemented as a routine in the project could negatively (or positively, if an opportunity - but with delay) influence the team just to perform the review at certain times, augmenting the possibility of unidentified risks show up, in your particular way to see this task? Saving Changes...
New risks should be brought up when they are identified. You shouldn't wait for periodic risk reviews of already documented risks to introduce new ones.
I would generally expect regularly recurring meetings to address emergent topics where new risks would be brought in for discussion with the team, along with other agenda items. There might be separate business management meetings and technical meetings, steering teams, technical review boards, etc. where you would bring in different types of risks, but those are part of the continuing business of running the project.
Once you've identified, communicated, and discussed a new emergent risk and add it to the register *then* you might assign a regular cadence to review the risk but don't wait a month to add one if that's your standard review cycle. Saving Changes...
Risk identification is a continual process throughout the life cycle of the project, and risk should be reevaluated in a constant form. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
I agree with Veronica. It is a continious process and should be revisited frequently, I would say if the project is high risk and critical, then weekly because new risks may arise, others may subside. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Don't wait for the kickoff meeting: you should have started risk management during initiation. (I usually start risk management at the business cases stage.)
The frequency of reviews should be based on the scope and schedule of your project. On my last, three-year long, project, we reviewed the risk register on a monthly basis. Saving Changes...
Vijay SuryavanshiProject Manager - Engineering| RECARO Aircraft SeatingPlantation, Fl, United States
Agree with Stephane here. In fact, doing an initial risk assessment is a requirement for us to get the project approved. However, risk monitoring is ongoing, and you can update the risk register on a frequency (internally in the organization) that you decide if unidentified risks occur. (This after assessment can becomes part of contingency reserves in your project planning. For the unknown, unknowns a management reserve of about 5 percent can be reserved.) Saving Changes...
Community Champion
