Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

CAPM > "C" Terms & Definitions > Flashcards

"C" Terms & Definitions Flashcards

(83 cards)

Start Studying
1
Q

Cardinal scales

A

A ranking approach to identify the probability and impact by using a numerical value, from .01
(very low) to 1.0 (certain).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Cause-and-effect diagrams

A

Diagrams that show the relationship between variables within a process and how those
relationships may contribute to inadequate quality. The diagrams can help organize both the
process and team opinions, as well as generate discussion on finding a solution to ensure quality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

CARVER

A

An acronym to measure the goals and mission of the project with each letter meaning: Criticality,
Accessibility, Return, Vulnerability, Effect, and Recognizeability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Ceremony

A

A meeting conducted during an Agile project that consists of daily stand-up, iteration planning,
iteration review, and iteration retrospective.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Certified Associate in Project Management (CAPM)

A

A person who has slightly less project management experience than a PMP, but who has
qualified for and then passed the CAPM examination.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Change

A

To change requirements that increase value to the customer.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Change Control Board (CCB)

A

A committee that evaluates the worthiness of a proposed change and either approves or rejects
the proposed change.
* 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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Change Control System (CCS)

A

Documented in the scope management plan, this system defines how changes to the project
scope are managed and controlled.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Change log

A
  • All 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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Change management plan

A

This plan details the project procedures for entertaining change requests: how change requests
are managed, documented, approved, or declined.
* This subsidiary plan defines how changes will be allowed and managed within the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Charismatic leadership

A

The leader is motivating, has high-energy, and inspires the team through strong convictions
about what is possible and what the team can achieve. Positive thinking and a can-do mentality
are characteristics of a charismatic leader.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Charter

A

A document created during initiation that formally begins the project. The document includes
the project’s justification, a summary level budget, major milestones, critical success factors,
constraints, assumptions, and authorization to do it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Checklist

A
  • A simple approach to ensure that work is completed according to the quality policy.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Chicken

A

An individual involved but not committed to an agile project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Choice of media

A

The best modality to use when communicating that is relevant to the information being
communicated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Claims

A

These are disagreements between the buyer and the seller, usually centering on a change, who
did the change, and even whether a change has occurred. Claims are also called disputes and
appeals and are monitored and controlled through the project in accordance with the contract
terms.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Closure processes

A

This 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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Coach

A

A team role that keeps the team focused on learning and the process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Code of accounts

A

A numbering system for each item in the WBS. The PMBOK is a good example of a code of
accounts, as each chapter and its subheadings follow a logical numbering scheme. For example,
PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Coercive power

A
  • The project manager has the authority to discipline the project team members. This is also
    known as penalty power.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Collaborate/Problem solving

A

This approach confronts the problem head-on and is the preferred method of conflict resolution.
Multiple viewpoints and perspectives contribute to the solution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Collaboration

A

A method of cooperation among individuals to achieve a common goal.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Collective bargaining agreement constraints

A

Contracts and agreements with unions or other employee groups may serve as constraints on
the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Collective code ownership

A

The entire team together is responsible for 100% of the code.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Collocation
The entire team is physically present, working in one room.
26
Command & Control
Decisions created by higher up individuals in the organization and handed over to the team.
27
Commercial database
A cost-estimating approach that uses a database, typically software-driven, to create the cost estimate for a project.
28
Common cause
An issue solved through trend analysis because the issue is systematic.
29
Communication
To share smooth and transparent information of needs.
30
Communication assumptions
Anything that the project management team believes to be true but hasn’t proven to be true. For example, the project management team may assume that all of the project team can be reached via cell phone, but parts of the world, as of this writing, don’t have a cell signal.
31
Communication barrier
Anything that prohibits communication from occurring.
32
Communication channels formula
N(N – 1)/2, where N represents the number of identified stakeholders. This formula reveals the total number of communication channels within a project.
33
Communication constraints
Anything that limits the project management team’s options. When it comes to communication constraints, geographical locales, incompatible communications software, and even limited communications technology can constrain the project team.
34
Communications management plan
* A project management subsidiary plan that defines the stakeholders who need specific information, the person who will supply the information, the schedule for the information to be supplied, and the approved modality to provide the information. * This plan defines who will get what information, how they will receive it, and in what modality the communication will take place.
35
Competency
This attribute defines what talents, skills, and capabilities are needed to complete the project work.
36
Compliance
* To meet regulations, rules, and standards.
37
Compromising
This approach requires that both parties give up something.
38
Cone of silence
* An environment for the team that is free of distractions and interruptions.
39
Configuration identification
This includes the labeling of the components, how changes are made to the product, and the accountability of the changes.
40
Configuration management plan
This plan is an input to the control scope process. This subsidiary plan defines how changes to the features and functions of the project deliverables will be monitored and controlled within the project.
41
Configuration management system
This 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.
42
Configuration status accounting
The organization of the product materials, details, and prior product documentation.
43
Configuration verification and auditing
The scope verification and completeness auditing of project or phase deliverables to ensure that they are in alignment with the project plan.
44
Conflict
Disagreements in certain areas between individuals.
45
Conflict of interest
A situation where a project manager may have two competing duties of loyalty. For example, purchasing software from a relative may benefit the relative, but it may do harm to the performing organization.
46
Conflict resolution
An agreement made after a conflict.
47
Context diagram
These diagrams show the relationship between elements of an environment. For example, a context diagram would illustrate the networks, servers, workstations, and people that interact with the elements of the environment.
48
Continuous improvement
To ensure that self-assessment and process improvement occurs frequently to improve the product.
49
Continuous integration
To consistently examine a team member’s work. To build, and test the entire system.
50
Contingency reserve
A contingency allowance to account for overruns in costs. Contingency allowances are used at the project manager’s discretion and with management’s approval to counteract cost overruns for scheduled activities and risk events.
51
Contract change control system
This defines the procedures for how the contract may be changed. The process for changing the contract includes the forms; documented communications; tracking; conditions within the project, business, or marketplace that justify the needed change; dispute resolution procedures; and the procedures for getting the changes approved within the performing organization.
52
Contract closure
The formal verification of the contract completeness by the vendor and the performing organization.
53
Contract Statement of Work (SOW also CSOW)
* This document requires that the seller fully describe the work to be completed and/or the product to be supplied. The SOW becomes part of the contract between the buyer and the seller.
54
Control account
A WBS entry that considers the time, cost, and scope measurements for that deliverable within the WBS. The estimated performance is compared against the actual performance to measure overall performance for the deliverables within that control account. The specifics of a control account are documented in a control account plan.
55
Control chart
A quality control chart that maps the performance of project work over time.
56
Control quality
An inspection-driven process that measures work results to confirm that the project is meeting the relevant quality standards.
57
Control threshold
A predetermined range of acceptable variances, such as +/–10 percent off schedule. Should the variance exceed the threshold, then project control processes and corrected actions will be enacted.
58
Coordination
To organize work with the goal of higher productivity and teamwork.
59
Cost aggregation
* Costs are parallel to each WBS work package. The costs of each work package are aggregated to their corresponding control accounts. Each control account is then aggregated to the sum of the project costs.
60
Cost baseline
This is the aggregated costs of all of the work packages within the work breakdown structure (WBS). It is time-lapse exposure of when the project monies are to be spent in relation to cumulative values of the work completed in the project.
61
Cost budgeting
The cost aggregation achieved by assigning specific dollar amounts for each of the scheduled activities or, more likely, for each of the work packages in the WBS. Cost budgeting applies the cost estimates over time.
62
Cost change control system
* A system that examines any changes associated with scope changes, the cost of materials, and the cost of any other resources, and the associated impact on the overall project cost.
63
Cost management plan
* This plan details how the project costs will be planned for, estimated, budgeted, and then monitored and controlled. * The cost management plan dictates how cost variances will be managed.
64
Cost Performance Index (CPI)
To measure the cost spent on a project and its efficiency. Earned Value / Actual Cost = CPI
65
Cost of conformance
This is the cost associated with the monies spent to attain the expected level of quality. It is also known as the cost of quality.
66
Cost of nonconformance to quality
* The cost associated with not satisfying quality expectations. This is also known as the cost of poor quality.
67
Cost of poor quality
The monies spent to recover from not adhering to the expected level of quality. Examples may include rework, defect repair, loss of life or limb because safety precautions were not taken, loss of sales, and loss of customers. This is also known as the cost of nonconformance to quality.
68
Cost of quality
The monies spent to attain the expected level of quality within a project. Examples include training, testing, and safety precautions.
69
Cost plus award fee contract
* A contract that pays the vendor all costs for the project, but also includes a buyer-determined award fee for the project work. * A contract that requires the buyer to pay for the cost of the goods and services procured plus a fixed fee for the contracted work. The buyer assumes the risk of a cost overrun.
70
Cost plus incentive fee
* A contract type that requires the buyer to pay a cost for the procured work, plus an incentive fee, or a bonus, for the work if terms and conditions are met.
71
Cost plus percentage of costs
* A contract that requires the buyer to pay for the costs of the goods and services procured plus a percentage of the costs. The buyer assumes all of the risks for cost overruns.
72
Cost Variance (CV)
The difference of the earned value amount and the cumulative actual costs of the project. The formula is CV = EV – AC.
73
Cost-benefit analysis
* A process to study the trade-offs between costs and the benefits realized from those costs.
74
Crashing
* A schedule compression approach that adds more resources to activities on the critical path to complete the project earlier. When crashing a project, costs are added because the associated labor and sometimes resources (such as faster equipment) cause costs to increase.
75
Critical path
* The path in the project network diagram that cannot be delayed; otherwise, the project completion date will be late. There can be more than one critical path. Activities in the critical path have no float.
76
Cross-functional team
* Teams that consist of members who can multi-task well and complete various functions to achieve a common goal.
77
Crystal family
An adaptable approach that focuses on interaction between people and processes that consists of families that vary based on team size, system criticality, and project priorities.
78
Cultural and social environment
Defines how a project affects people and how those people may affect the project. Cultural and social environments include the economic, educational, ethical, religious, demographic, and ethnic composition of the people affected by the project.
79
Cultural norms
Cultural norms describe the culture and the styles of an organization. Cultural norms, such as work ethics, hours, view of authority, and shared values, can affect how the project is managed.
80
Cumulative flow diagram
* A chart that displays feature backlog, work-in-progress, and completed features.
81
Customer
The end-user who determines and emphasizes business values.
82
Customer-valued prioritization
To deliver the maximum customer value early in order to win customer loyalty and support.
83
Cycle time
* The time needed to complete a feature (user story).

CAPM (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions