|
|
| Records Retention - Records retention is the process of deciding which documents will remain and which documents will be destroyed after a determined amount of time. The project librarian is typically responsible for managing the life cycle of documents and describes the process in the Document management plan. |
| Referential integrity - refers to rules governing data consistency, specifically the interaction between primary keys and foreign keys in different tables. Referential integrity dictates what happens when you update or delete a value in a referenced column in the parent table and when you delete a row containing a referenced column from the parent table. |
| Relationships - links information together and it is an essential part of database normalization. Most of the time, relationships reflects the one (master table, or referenced table) to many (child table, or referencing table) relationships between the tables. There may be one-to-one, one-to-many, etc, relationship between the parent and child tables. |
| Request for Information (RFI) - A letter released to the bidding community seeking to identify interested bidders for a particular procurement. The RFI generally describes the background of the business problem and may describe some of the key requirements. The project works with DGS to develop and release the RFI. |
| Request for Proposal (RFP) - The RFP used to solicit proposals from the bidding community based on a set of defined requirements. The requirements may be general in nature allowing the bidders to propose a solution and the specific products to be used. The RFP describes the problem requirements, contractual terms, and required format for the proposal responses. The RFP also includes the specific criteria which will be used to evaluate the received proposals. The project works with DGS to ensure the RFP meets all appropriate state guidelines and regulations. |
| Requirement - A statement or model identifying a capability, physical characteristic, or quality factor that bounds a need for which a solution will be pursued. |
| Requirements Management Plan - This document describes the approach to managing the system requirements. The plan describes how requirements are derived and validated, how requirements changes are analyzed and managed, how requirements traceability is maintained and validated, and how the project works with the contractor to ensure traceability of requirements to the system and system documentation. |
| Requirements Traceability - the process of understanding, documenting, approving, and auditing the relationships between a system’s components and functions and the requirements from which the system was developed. Each function and component of a system should be directly traceable to a requirement identified by a user, client, customer, and or stakeholder. |
| Requirements Traceability Matrix - A Requirements Traceability Matrix is a tool that will ensure that all requirements have been fulfilled in the end product by associating each requirement with the object via a matrix. Requirements traceability includes tracing to things other than software that satisfy requirements such as capabilities, design elements, manual operations, tests, etc. A traceability matrix is also used to ensure all requirements are met and to locate affected system components when there is a requirements change. |
| Responsibility Assignment Matrix (RAM) - The Responsibility Assignment Matrix (RAM) assigns responsibilities for project work components to project roles. Refer to the Staff Management Plan for instructions on using the RAM. |
| Resource Breakdown Structure (RBS) - Variation of the organizational breakdown structure used to show which work elements are assigned to individuals. |
| Resource Pool - (1) Collection of human and material resources that may be used concurrently on several projects.
(2) A set of project resources that is available for assignment to the accomplishment of project tasks.
|
| Resource Tracking - Resource tracking is monitoring the actual resource expenditures (time and costs) against the plan; identifying variances early; and making appropriate decisions on how to correct the problems before they worsen. |
| Responsibility - (1) Obligation of an individual or group to perform assignments effectively. (2) Status of a prospective contractor that determines whether it is eligible for contract award. |
| Return On Investment (ROI) - Amount of gain, expressed as a percentage, earned on an organization's total capital; calculated by dividing total capital into earnings before interest, taxes, and dividends. |
| RFP Addenda - Addenda are issued after the RFP is released to the bidders to clarify requirements or bidder instructions, or to respond to questions from the bidders. The project must work with DGS to issue any addenda. |
| Risk - A potential event that would have a negative impact on the success of the project if the event were to occur. Also an opportunity for benefit to the project, if acted upon. |
| Risk (External) - Those risks beyond the control or influence of the project team. |
| Risk (Internal) - Those risks the project team can control or influence. |
| Risk Acceptability - The exposure to loss (financial or otherwise) that an organization is willing to tolerate from a risk. |
| Risk Action Request or Plan - The recommended treatment alternatives and supporting information for one or more risks determined to be above a risk tolerance or threshold. |
| Risk Analysis - The evaluation of risks and risk interactions to assess the range of possible project outcomes. The determination of which risk events warrant response. (Is the negative impact of the potential risk event significant enough to warrant inclusion in the risk management process?) |
| Risk Consequence - An outcome of an event, hazard, threat or situation. |
| Risk Contingency Planning - For those risks where it is unlikely or uncertain that the mitigation will be effective, a contingency plan should be developed. The contingency plan should attempt to minimize the effects of the risk assuming the event does occur. |
| Risk Criticality - A designation of the project’s risk, sensitivity or importance based on several factors including size, project manager and team experience, and several project characteristics. The criticality rating is determined using the OCIO IT Project Oversight Framework. OCIO makes the final determination regarding a project’s criticality rating. This rating is used to determine the requirements for risk reporting to external stakeholders. |
| Risk Description - Documentation of the risk element to identify the boundaries of the risk. |
| Risk Escalation - The process of elevating a risk to appropriate management and stakeholders to ensure sufficient visibility to effect a decision, action or change to the risk’s current profile. There are usually three levels of risk escalation. |
| Risk Exposure - A determination of the importance of or potential loss from the risk based upon 1) potential impact of the risk on the project, and 2) the probability of occurrence. Usually categorized as high, medium or low. |
| Risk Factor - Risk event, risk probability, or amount at stake. |
| Risk Identification - The determination of which risks are likely to affect the project and the documenting of the characteristics of each risk. Risk identification is not a one-time event; it is performed on a regular basis throughout the project’s life cycle. Risk identification must address both internal and external risks. |
| Risk Impact - The potential consequences, either positive or negative, should the risk occur. Impacts may affect several areas in both tangible and intangible ways. Usually expressed as High, Medium or Low. |
| Risk Likelihood - A qualitative or quantitative expression of the changes that an event will occur. |
| Risk Mitigation - The identification of ways to minimize or eliminate project risks. Depending on the severity of the risk and the level of effort for the mitigation strategies, it may be appropriate to initiate several mitigation activities. In other cases, it may not be possible to mitigate a risk. |
| Risk Probability - The likelihood of the occurrence of the risk (high, medium, low). |
| Risk Profile - The current and historical risk-related information; a compendium or aggregate of all the individual risk profiles in a project. |
| Risk Ranking - The relative importance of the risk compared to the list of all project risks. Assists in prioritizing and applying resources for mitigation and contingency actions. |
| Risk Severity - A function of the risk exposure compared to the timeframe. The control agencies require risks of a certain severity to be escalated. Ranking of risks is often driven by severity. |
| Risk State - The current information relating to an individual risk. |
| Risk Timeframe - The period of time within which the risk is expected to occur (short-term, medium-term, long-term). |
| Risk Tolerance or Threshold - The criteria against which stakeholders evaluate a risk. Different risk tolerances may be defined for each risk, risk category, or combination of risks. Exceeding a risk threshold is a condition that triggers some action. |
| Risk Tracking/Control - A method to insure that all steps of the risk management process are being followed and, as a result, risks are being mitigated effectively. Risk tracking/control involves the oversight and tracking of risk mitigation action plan execution, re-assessment of risks, reporting risk status, and recording risk information changes in the project risk database. |
| Roster - A list of people's names and their contact information, often with their assigned roles or tasks. |
