CAPM Glossary Pt. 4 Flashcards
An uncertain event or condition that can have a positive or negative impact on the project.
Risk
The systematic process of combing through the project, the project plan, the work breakdown structure, and all supporting documentation to identify as many risks that may affect the project as possible.
Risk identification
A project management subsidiary plan that defines how risks will be identified, analyzed, responded to, and monitored within the project. The plan also defines the iterative risk management process that the project is expected to adhere to.
Risk management plan
The individuals or entities that are responsible for monitoring and responding to an identified risk within the project.
Risk owners
A project plan component that contains all of the information related to the risk management activities. It is updated as risk management activities are conducted to reflect the status, progress, and nature of project risks.
Risk register
A report that explains the overall project risks and provides summaries about the individual project risks.
Risk report
An audit to test the validity of the established risk responses.
Risk response audit
A subsidiary plan that defines the risk responses that are to be used in the project for both positive and negative risks.
Risk response plan
The level of ownership an individual or entity has over a project risk.
Risk responsibility
The calculated score based on a risk’s probability and impact. The approach can be used in both qualitative and quantitative risk analysis.
Risk score
When the project management team decides to use transference to respond to a risk, this agreement is created between the buyer and the seller.
Risk-related contractual agreement
Denotes what a person is specifically responsible for in a project. Roles are usually tied to job titles, such as network engineer, mechanical engineer, and electrician.
Role
A form of progressive elaboration in which the imminent work is planned in detail, while the work in the future is planned at a high level.
Rolling wave planning
A process that aims to determine why a risk event may be occurring, the causal factors for the risk event, and then, eventually, how the event can be mitigated or eliminated.
Root cause identification
A rough estimate that is used during the initiating processes an din top-down estimates. The range of variance for the estimate can be from -25 percent to +75 percent.
Rough order of magnitude
A component of a control chart that illustrates the results of seven measurements on one side of the mean, which is considered “out of control” in the project.
Rule of Seven
A quality control tool that shows the results of inspection in the order in which they’ve occurred. The goal is to first demonstrate the results of a process over time and then to use trend analysis to predict when certain trends may reemerge.
Run chart
A quality control tool that tracks the relationship between two variables over time. The two variables are considered related the closer they track against a diagonal line.
Scatter diagram
The planned start and finish of the project.
Schedule baselines
A subsidiary plan in the project management plan. It defines how the project schedule will be created, estimated, controlled, and managed.
Schedule management plan
Specific dates when phases of the project should be completed. These are often treated as project constraints.
Schedule milestones
Measures the project based on its schedule performance. The formula is SPI = EV/PV
Schedule performance index (SPI)
The comparison of what was planned and what was experienced – the difference between the earned value and the planned value. The formula is SV = EV-PV
Schedule variance (SV)
A combination of three project documents: the project scope statement, the work breakdown structure and the WBS dictionary. The creation of the project deliverable will be measured against this to show any variances from what was expected and what the project team has created.
Scope baseline
Undocumented, unapproved changes to the project scope.
Scope creep
The formal inspection of the project deliverables, which leads to project acceptance.
Scope validation
Models that use a common set of values for all of the projects up for selection. For example, values can be profitability, complexity, customer, demand, and so on.
Scoring models
A tool that filters or screens out vendors that don’t quality for the contract.
Screening system
New risks that are created as a result of a risk response.
Secondary risks
A system used by organizations to rate prior experience with each vendor that they have worked with in the past. This system can track performance, quality ratings, delivery and even contract compliance.
Seller rating system
The person who is sending the message
Sender
Communication requires a sender and receiver. Within this model may be multiple avenues to complete the flow of communication, but barriers to effective communication may be present as well.
Sender-receiver model
A quantitative risk analysis tool that examines each risk to determine which one has the largest impact on the project’s success.
Sensitivity analysis
The leader puts others first and focuses on the needs of the people they serve. They provide opportunity for growth, education, autonomy within the project, and the well-being of others. The primary focus of this type of leadership is service to others.
Servant leadership
Seven tools that are used in quality planning and in quality control: cause-and-effect diagrams, flowcharts, check sheets, Pareto diagrams, histograms, control charts, and scatter diagrams.
Seven basic quality tools
A risk response that shares the advantages of a positive risk within a project.
Sharing
Many vendors can provide what your project needs to purchase, but you prefer to work with a specific vendor.
Single source
The project manager has power because of certain situations in the organization.
Situational power
An approach to conflict management that addresses a conflict by minimizing the perceived size of the problem. It is a temporary solution but can calm team relations and boisterous discussions.
Smoothing
The activities don’t necessarily have to happen in a specific order. For example, you could install the light fixtures first, then the carper, and then paint the room. Based on this, the project manager can change the order of the activities if so desired.
Soft logic
Only one vendor can provide what your project needs to purchase. Examples include a specific consultant, a specialized service, or a unique type of material.
Sole source
Time-boxed duration, typically two to four weeks, or project execution in an agile environment. They are iterations of executing the prioritized list of product backlog requirements.
Sprint