Discovering Risks in Project Documents

A.

As a project management consultant, Joan's first step in identifying risk events within a project is to examine project documents, including plans, assumptions lists, project files, and contracts. By reviewing these documents, Joan can gain insight into the project's goals, objectives, and constraints.

The key thing that can help Joan discover risks within the review of project documents is to look for inconsistencies between plans, project requirements, and assumptions. Lack of consistency between plans and the project requirements and assumptions can be an indicator of risk in the project. For example, if the project plan assumes that a particular resource will be available at a certain time, but the requirements document doesn't specify this, there is a risk that the resource won't be available when needed.

In addition to inconsistencies, Joan should also look for loose definitions of terms and disconnected approaches in the project plans. These can reveal risks that may have been overlooked or not adequately addressed. For example, if the project plan includes vague or undefined terms, it may be difficult to assess whether the project has met its objectives.

Finally, poorly written requirements can reveal inconsistencies in the project plans and documents. If the requirements document is unclear or ambiguous, it can be difficult to determine whether the project is meeting its objectives. Similarly, if the requirements document is incomplete or lacks detail, it may be difficult to assess the risks associated with the project.

In summary, by reviewing project documents, Joan can identify inconsistencies between plans, project requirements, and assumptions, loose definitions of terms and disconnected approaches, and poorly written requirements. These factors can all reveal risks within the project and help Joan develop an effective risk management strategy.