CompTia Project Terms - Part 01 Flashcards Preview

CompTIA Project+ > CompTia Project Terms - Part 01 > Flashcards

Flashcards in CompTia Project Terms - Part 01 Deck (120)
Loading flashcards...
1

The decision to tolerate the defects that are found as a result of the quality testing. This is also a tool for risk response planning.

acceptance

2

The process and the criteria that will be used to determine whether the deliverables are acceptable and satisfactory.

acceptance criteria

3

Identifying the activities of the project that need to be performed to produce the product or service of the project.

activity definition

4

A list of all the activities required to complete the work of the project that also includes an identifier code and the WBS code it?s associated with. Activities are broken down from the work package level of the WBS.

activity list

5

Sequencing activities in logical order and determining whether dependencies exist among the activities.

activity sequencing

6

The cost to complete a component of work in a given time period. Actual costs include direct and indirect costs.

actual cost (AC)

7

A type of project ending that occurs when projects evolve into ongoing operations.

addition

8

A process that involves gathering and disseminating information to formalize project closure. The completion of each project phase requires Administrative Closure also. The primary purpose of this process is to gather lessons learned and distribute the notice of acceptance.

Administrative Closure

9

An estimating technique that uses the actual duration of a similar, completed activity to determine the duration of the current activity. This is also called top-down estimating.

analogous estimating

10

Costs of quality that cover the activities that keep the product defects from reaching the client, including inspection, testing, and formal quality audits.

appraisal costs

11

An event or action believed to be true for planning purposes. Project assumptions should always be documented.

assumption

12

A conflict-resolution technique that occurs when one party refuses to talk anymore about the issue and physically leaves. This is an example of a lose-lose conflict-resolution technique. This technique is also known as withdrawal.

avoiding

13

Calculating late start and late finish dates by starting at the end of a network diagram and working back through each path until reaching the start of the network diagram. This is part of critical path method (CPM), which is a mathematical technique to develop the project schedule.

backward pass

14

Compares previous similar activities to the current project activities to provide a standard to measure performance against. It?s often used to derive ideas for quality improvements for the poject

benchmarking

15

A type of decision model that compares the benefits obtained from a variety of new project requests by evaluating them using the same criteria and comparing the results.

benefit measurement methods

16

A meeting held by the buyer with potential vendors during the procurement process to allow vendors to ask questions and get clarification on the project.

bidder conference

17

Individually estimating each work package, all of which are then rolled up, or added together, to come up with a total project estimate. This is a very accurate means of estimating, provided the estimates at the work package level are accurate.

bottom-up estimating

18

The total amount of the project budget for a work package, control account, or schedule activity, or for the project.

budget at completion (BAC)

19

The person in charge of understanding the business unit?s needs when assessing a project request. The business analyst might be assigned directly from the business unit itself or may be part of the IT organization.

business analyst

20

Formally documents components of the project assessment, including a description of the analysis method and the results.

business case

21

Applying changes to an IT system and putting those elements into place based on a project request and a business analyst?s examination of the workflow?how people handle their work relative to the request.

business process reengineering

22

The requirements that describe how the business objectives of the project will be met.

business requirements

23

A Quality Control technique that shows the relationship between the effects of problems and their causes. This is also known as an Ishikawa diagram and a fishbone diagram.

cause-and-effect diagram

24

A board responsible for reviewing and approving, denying, or delaying change requests. The change control board is usually made up of stakeholders, managers, project team members, and others who might have an interest in the project.

change control board (CCB)

25

A process that concerns completing and settling the terms of the contract and documenting its acceptance.

Close Procurements

26

A process that documents the final delivery and acceptance of the project and is where hand-off occurs to the operational unit. Lessons learned are performed during this process, and project team members are released.

Closing

27

When team members work together at the same physical location.

collocated

28

Describes a software application that is purchased from a reseller, vendor, or manufacturer.

commercial off-the-shelf (COTS)

29

Variances that come about as a result of circumstances that are common to the process you?re performing and are easily controlled at the operational level. The three types of common cause variances are random, known or predictable, and variances that are always present in the process.

common causes of variances

30

plan Documents the types of information needs the stakeholders have, when the information should be distributed, and how the information will be delivered.

communications management plan