Flashcards
4 Project Integration Management
Flashcards do conjunto (42)
- 1Assumption logAn assumption is something that is believed to be true or false, but it has not yet been proven to be true or false. Assumptions that prove wrong can become risks for the project. All identified project assumptions are recorded in the assumption log for testing and analysis, and the outcomes are recorded.
- 2Benefit/cost ratio (BCR) modelsThis is an example of a benefits comparison model. It examines the benefit-to-cost ratio.
- 3Change control board (CCB)A committee that evaluates the worthiness of a proposed change and either approves or rejects the proposed change.
- 4Change control system (CCS)The change control system communicates the process for controlling changes to the project deliverables. This system works with the configuration management system and seeks to control and document proposals to change the project’s product.
- 5Change logAll changes that enter into a project are recorded in the change log. The characteristics of the change, such as the time, cost, risk, and scope details, are also recorded.
- 6Change management planThis plan details the project procedures for entertaining change requests: how change requests are managed, documented, approved, or declined.
- 7Closure processesThis final process group of the project management life cycle is responsible for closing the project phase or project. This is where project documentation is archived and project contracts are also closed.
- 8Communications management planThis plan defines who will get what information, how they will receive it, and in what modality the communication will take place.
- 9Configuration identificationThis includes
labeling of the components
how changes are made to the product,
amd the accountability of the changes. - 10Configuration management plan & what's it an input to?It defines how changes to the features and functions of the project deliverable, the product scope, may enter the project.
This plan is an input to the control scope process. - 11Configuration management systemThis system defines how stakeholders are allowed to submit change requests, the conditions for approving a change request, and how approved change requests are validated in the project scope. Configuration management also documents the characteristics and functions of the project’s products and any changes to a product’s characteristics.
- 12Configuration status accountingThe organization of the product materials, details, and prior product documentation.
- 13Configuration verification and auditingThe scope verification and completeness auditing of project or phase deliverables to ensure that they are in alignment with the project plan.
- 14Contract closureThe formal verification of the contract completeness by the vendor and the performing organization.
- 15Cost baselineThis is the aggregated costs of all of the
work packages within the work breakdown structure (WBS). - 16Cost management planThis plan details how the project costs will be planned for, estimated, budgeted, and then monitored and controlled.
- 17Explicit knowledgeKnowledge that can be quickly and easily expressed through conversations, documentation, figures, or numbers, is easily communicated.
- 18Future valueA benefit comparison model to determine a future value of money. The formula to calculate future value is FV = PV(1 + I)n, where PV is present value, I is the given interest rate, and n is the number of periods.
- 19Integrated change controlA process to consider and control the impact of a proposed change on the project’s knowledge areas.
- 20Issue logIssues are points of contention where some question of the project’s direction needs to be resolved. All identified issues are documented in the issue log, along with an issue owner and a deadline to resolve the issue. The outcome of the issue is also recorded.
- 21Mathematical modelA project selection method to determine the likelihood of success. These models include linear programming, nonlinear programming, dynamic programming, integer programming, and multiobjective programming.
- 22MilestoneMilestones are significant points or events in the project’s progress that represent accomplishment in the project. Projects usually create milestones as the result of completing phases within the project.
- 23Milestone listThis list details the project milestones and their attributes. It is used for several areas of project planning, but also helps determine how quickly the project may be achieving its objectives.
- 24Murder boardsThese are committees that ask every conceivable negative question about the proposed project. Their goals are to expose the project’s strengths and weaknesses, and to kill the project if it’s deemed unworthy for the organization to commit to. Also known as project steering committees or project selection committees.
- 25Net present valueEvaluates the monies returned on a project for each period the project lasts.
- 26Payback periodAn estimate to predict how long it will take a project to pay back an organization for the project’s investment of capital.
- 27Present valueA benefit comparison model to determine the present value of a future amount of money. The formula to calculate present value is PV = FV ÷ (1 + i)n, where FV is future value, I is the given interest rate, and n is the number of periods.
- 28Procurement management planThe procurement management plan controls how the project will acquire goods and services.
- 29Project charterThis document authorizes the project. It defines the initial requirements of the project stakeholders. The project charter is endorsed by an entity outside of the project boundaries.
- 30Project management planThe documented approach of how a project will be planned, executed, monitored and controlled, and then closed. This document is a collection of subsidiary management plans and related documents.
- 31Project scope management planDefines how the project scope will be planned, managed, and controlled.
- 32Quality baselineDocuments the quality objectives for the project, including the metrics for stakeholder acceptance of the project deliverable.
- 33Quality management planThis plan defines what quality means for the project, how the project will achieve quality, and how the project will map to organizational procedures pertaining to quality.
- 34Regression analysisA mathematical model to examine the relationship among project variables, like cost, time, labor, and other project metrics.
- 35Risk management planRisk is an uncertain event or condition that may affect the project outcome. The risk management plan defines how the project will manage risk.
- 36Risk registerThe risk register is a centralized database consisting of the outcome of all the other risk management processes, such as the outcome of risk identification, qualitative analysis, and quantitative analysis.
- 37Risk response planThis subsidiary plan defines the risk responses that are to be used in the project for both positive and negative risks.
- 38Schedule baselineThis is the planned start and finish of the project. The comparison of what was planned and what was experienced is the schedule variance.
- 39Schedule management planDefines how the project schedule will be created and managed.
- 40Scope baselineThe scope baseline is 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 the scope baseline to show any variances from what was expected and what the project team has created.
- 41Scoring modelsThese models 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.
- 42tacit knowledgeKnowledge that’s more difficult to express because it’s personal beliefs, values, knowledge gain from experience, and
“know-how” when doing a task.
Informações
- Descrição
- 4 Project Integration Management
- Criado por
- Daniel Gomez-Windshuttle
- Visualizações
- 11
- Avaliação