Risk Event: A discrete occurrence that may affect the project for better or worse. (来源：EnglishCN.com)
Risk Identification: Determining which risk might affect the project and documenting their characteristics. Tools used include brainstorming and checklists.
Risk Management Plan: Documents how the risk processes will be carried out during the project. This is the output of risk management planning.
Risk Management Planning: Deciding how to approach and plan risk management activities for a project.
Risk Mitigation: Risk mitigation seeks to reduce the probability and/or impact of a risk to below an acceptable threshold.
Risk Monitoring and Control: Monitoring residual risks, identifying new risks, executing risk reduction plans, and evaluating their effectiveness throughout the project life cycle.
Risk Register: See risk response plan.
Risk Response Plan. A document detailing all identified risk, including description, cause, probability of occurring, impact(s) on objectives, proposed responses, owners, and current status. Also known as risk register.
Risk Response Planning: Developing procedures and techniques to enhance opportunities and reduce threats to the project's objectives. The tools include avoidance, mitigation, transference, and acceptance.
Risk Transference: Risk transference is seeking to shift the impact of a risk to a third party together with ownership of the response.
S-Curve: Graphic display of cumulative costs, labor hours, percentage of work, or other quantities, plotted against time. The name derives from the S-like shape of the curve (flatter at the beginning and end, steeper in the middle) produced on a project that starts slowly, accelerates, and then tails off. Also a term for the cumulative likelihood distribution that is a result of a simulation, a tool quantitative risk analysis.
Schedule: See project schedule.
Schedule Analysis: See network analysis.
Schedule Compression. See duration compression.
Schedule Control: Controlling changes to the project schedule.
Schedule Development: Analyzing activity sequences, activity durations, and resource requirements to create the project schedule.
Schedule Performance Index (SPI): The schedule efficiency ratio of earned value accomplished against the planned value The SPI describes what portion of the planned schedule was actually accomplished The SPI = F" divided by PV.
Schedule Variance (SV): 1) Any difference between the scheduled completion of an activity and the actual completion of that activity. 2) In earned value, EV less BCWS = SV.
Scheduled Finish Date (SF): The point in time that work was scheduled to finish on an activity. The scheduled finish date is normally within the range of dates delimited by the early finish date and the late finish date. It may reflect leveling or scarce resources.
Scheduled Start Date (SS): The point in time that work was scheduled to start on an activity. The scheduled start date is normally within the range of dates delimited by the early start date and the late start date. It may reflect leveling of scarce resources.
Scope: The sum of the products and services to be provided as a project. See project scope and product scope.
Scope Baseline: See baseline.
Scope Change: Any change to the project scope. A scope change almost always requires an adjustment to the project cost or schedule.
Scope Change Control: Controlling changes to project scope.
Scope Definition: Subdividing the major deliverables into smaller, more manageable components to provide better control.
Scope Planning: The process of progressively elaborating the work of the project, which includes developing a written scope statement that includes the project justification, the major deliverables, and the project objectives.
Scope Statement: The scope statement provides a documented basis for making future project decisions and for confirming or developing common understanding of project scope among the stakeholders. As the project progresses, the scope statement may need to be revised or refined to reflect approved changes to the scope of the project.
Scope Verification: Formalizing acceptance of the project scope.
Secondary Risk: A risk that arises as a direct result of implementing a risk response.
Seller: The provider of goods or services to an organization.
Should-Cost Estimate: An estimate of the cost of a product or service used to provide an assessment of the reasonableness of a prospective contractor's proposed cost.
Simulation: A simulation uses a project model that translates the uncertainties specified at a detailed level into their potential impact on objectives that are expressed at the level of the total project. Project simulations use computer models and estimates of risk at a detailed level, and are typically performed using the Monte Carlo technique.