PM Documents - Inverse Flashcards
The activity characteristics such as activity codes, predecessor and successor activities, leads and lags, resource requirements, dates, constraints, and assumptions.
Activity Attributes
The collections of documents that detail how the project’s cost estimate was created, which includes the following information:
- The scope of the work that the estimate is based on
- The basis for the estimate
- Documentation of the assumptions used in the estimate creation
- Documentation of the constraints used in the estimate creation
- The range of possible estimates, such as the =/- percentage or dollar amount
Activity cost estimate supporting detail
An estimate of the likely time it will take to complete the project, a phase, or individual activities within the project.
Activity duration estimate
The collection of project schedule activities.
Activity list
A tool that helps the project team sort ideas and data. This simple tool clusters similar ideas and is useful after a brainstorming session.
Affinity diagram
A document that defines what the project aims to accomplish for a person, customer, stakeholder, business, or organization. An agreement can be a verbal agreement, but it is more likely documented in a contract, memorandum of understanding, memo or email.
Agreement
An estimate based on a previous similar project to predict the current project’s time or cost expectations.
Analogous estimate
A document in which all assumptions identified in the project are documented and the status of each as an assumption is monitored. Assumptions need to be tested to determine risk likelihood.
Assumptions log
Narratives about the product requirements that need to be completed. These are often prioritized, numbered, and scheduled for creation based on time, budget, and stakeholder demand.
Backlog
A histogram that typically depicts the project activities and their associated start and end dates. Also known as a Gantt chart.
Bar chart
A project management plan that defines how the project will create and deliver the benefits for the organization.
Benefits management plan
Defines the materials and products needed to create the items defined in the corresponding work breakdown structure (WBS). The BOM is arranged in sync with the hierarchy of the deliverables in the WBS.
Bill of materials (BOM)
Documents the financial reasoning for the project and the end result of a feasibility study. A business case is often needed for the project charter to justify the project’s existence.
Business case
A diagram that illustrates how potential problems within a project may contribute to failure or errors within the project. Also known as an Ishikawa diagram, a fishbone diagram, or why-why diagram.
Cause-and-effect diagram
A document that records all changes that happen during the project. It is useful for scope verification, quality control, and tracking changes.
Change log
A project management plan that defines how the project will manage changes.
Change management plan
A documented request to change the project’s scope, which is managed through the project’s integrated change control process.
Change request
A checklist that is used as part of requirements gathering, task execution, quality control, and other aspects of the project to ensure that a task or process is completed accurately. Also known as a tally sheet.
Checksheet
A documented disagreement between the buyer and the seller. Claims are often settled through negotiations, mediation, or in the courts, depending on the terms of the contract.
Claim
A subsidiary plan that defines who needs what information, when the information is needed, the frequency of the communication, and the accepted modalities for the communication needs.
Communications management plan
A project management plan that defines the configurable items (features and functions) and the formal process for how these items are allowed to be changed.
Configuration management plan
Part of the monitor and control risk process includes the option of executing a contingency plan to respond to worst-case scenarios with risk impact.
Contingency Plan
A legal relationship between the buyer and the seller that describes the work to be completed, the fee for performing the work, a schedule for completing the work, and acceptance criteria to deem the contract complete. If a project is being completed by one organization for another organization, there is typically a contractual relationship between the seller and the customer. Contracts may be inputs for the project charter.
Contract
A plan that is used for significant purchases. This plan directs the acquisition and adherence of both the buyer and the seller to the terms of the contract.
Contract management plan
A document that defines the products and services that are being procured to satisfy portions of the project scope statement.
Contract statement of work
A quality control tool that illustrates the stability of a process and enables the project management team to determine whether the process may have trends and predictability.
Control chart
A time-phased budget that tracks the planned project expenses against the actual project expenses. This document is used to measure, monitor, and control project costs in conjunction with the cost management plan.
Cost baseline
A project management subsidiary plan that defines the structure for estimating, budgeting, and controlling project costs.
Cost management plan
A contract in which the buyer pays the seller a fee for the contract work or deliverable, plus an additional fee based on the percentage of total costs for the goods or services provided.
Cost plus fee or Cost plus percentage of costs
A contract in which the buyer pays the seller the costs of the materials and/or labor to complete the contract work or deliverable, plus a predetermined fee.
Cost plus fixed fee
A contract in which the buyer pays the seller the costs of the materials and labor plus an incentive bonus for reaching objectives set by the buyer. Incentives are typically based on reaching schedule objectives.
Cost plus incentive fee
A diagram that identifies and evaluates each available outcome of a decision and the decision’s implication, consideration of each choice, and the value of each decision.
Decision tree
A change request to repair defects within the project deliverables.
Defect repair request
A worst-case scenario plan to enable the organization to “fall back” if a project plan needs to be scrapped because of risks or issues.
Fallback plan
A diagram that illustrates how potential problems within a project may contribute to failure or errors within the project. Also known as a cause-and-effect diagram and Ishikawa diagram.
Fishbone diagram
A contract that defines the total price for the work or product the organization agrees to purchase.
Fixed-price or lump-sum contract
A visual representation of a process through a system.
Flowchart
A diagram that plots the strengths and weaknesses of the forces (stakeholders) that have influence over project decisions.
Force field analysis diagram
A document that formally records that the project customer and/or sponsor has accepted the project deliverables.
Formal acceptance documentation
A bar chart that shows scheduling information and relationships among tasks. Tasks are represented by nodes. The length of the node combined with the calendar shows the duration of the activity.
Gantt chart
A bar chart that shows the distribution of values.
HIstogram
Past project documentation and lessons learned documents are often used as inputs and references for current projects. Current project documentation and lessons learned documentation become historical information for future projects within an organization. Organizational Process Assets (OPAs)
Historical information
A document that serves as a means for evaluation estimates provided by potential vendors to complete the work the contract calls for. Tna independent estimate is often created by a third party for the performing organization for a fee. Also known as a third-party estimate and a should-cost estimate.
Independent estimate
A chart that shows the relationships between and among causal factors, events, situations, and other project conditions.
Influence diagram
A document inviting a prospective vendor to bid on the contents of the contract statement of work. This is a price-based decision model.
Invitation for bid
A diagram that illustrates how potential problems within a project may contribute to failure or errors within the project. Also known as a cause-and-effect diagram and fishbone diagram.
Ishikawa diagram
A document that records all issues, their statuses, and resolutions.
Issue log
A document listing the results of quality control and other types of lessons learned, which becomes part of organizational process assets. Lessons learned documentation is created throughout the project’s life cycle.
Lessons learned register