Introduce or enhance risks management

Make sure to create risks register and issues log - all this should be kept up to date and managed properly, i.e. there should be risks response strategy for each risk and action plan with owner for issues
Introduce RAID (risks, assumptions, issues, dependencies) practice
Track dependencies between teams/streams, or on stakeholders, and log issues into issues log if any blockers
Manage risks:
- implement proactive risks responses
- watch for high-priority risks unfolding
- monitor events triggering a contingency plan
- report on risk status
- assign risk on risk owner
- add due dates to the actions in the treatment plan
Use escalation as one of risks management processes in case of no power, information or resources and in order to move a project forward
Define risk tolerance/ appetite: which constraints are more important for your project? For instance, if quality can't be affected in any case, risks on quality would be much more important.
Make qualitative (risk exposure based on probability and impact) and quantitative (monetary impact) risk analysis
Allocate contingency/buffer in both estimations and budget taking into account monetary impact

Useful materials