Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

PMI-ACP Prep > Term Glossary > Flashcards

Term Glossary Flashcards

1
Q

Acceptance Test Driven Development

A

A method used to communicate with business customers, developers, and testers before coding begins.

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

Active Listening

A

to focus on what is being said and provide feedback to communicate understanding

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

Adaptive Leadership

A

A leadership style that helps teams to thrive and overcome challenges throughout a project

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

Affinity estimation

A

A method used to place user stories in a comparable-sized group

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

Agile

A

to develop a goal through periodic experimentation in order to fulfill the needs of a complex decision

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

Agile Adaptation

A

to adapt the project plan continuously through retrospectives in order to maximize value creation during the planning process

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

Agile Coaching

A

To help achieve goals that are person or organizational

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

Agile experimentation

A

to use the empirical process, observation, and spike introduction while executing a project to influence planning

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

Agile manifesto

A

a statement that reflects agile philosophy that includes: individuals and interactions of processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to changes over following a plan

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

Agile Manifesto Principles

A

a document that describes the twelve principles of the agile manifesto

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

Agile Manifesto: Customer Satisfaction

A

satisfy customers through early and continuous delivery of products, to test and receive feedback, to inform customers on progress, and to fulfill the customers value by completing priority requirements.

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

Agile Manifesto: Welcome Changes

A

To allow quick responses to the changes in external environments, and late in development to maximize the customers competitive advantage

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

Agile Manifesto: Frequent Delivery

A

To deliver software frequently to the customer, allowing for a quicker product release, faster provision of value to the customer and a shorter delivery timeframe

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

Agile Manifesto: Collocated Team

A

to have individuals work together daily on a project to implement osmotic communication, focus, and receive instant feedback to achieve a common goal

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

Agile Manifesto: Motivated Individuals

A

to give individuals the empowerment, support, environment, and trust needed to complete a task susccessfully

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

Agile Manifesto: Face to Face communication

A

the most efficient and effective way to communicate in order to receive direct feedback and influence osmotic communication

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

Agile Manifesto: Working Software

A

working software enables the measurement of progress, enhance customer satisfaction, and maintain and improve the quality of the software to help support project goals.

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

Agile Manifesto: Constant Pace

A

To help team members establish a healthy work-life balance, remain productive, and respond to changes swiftly or progress during a project

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

Agile Manifesto: Continuous Attention

A

to enhance agility and time spent on work requirements in order to maintain a well balanced work environment

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

Agile Manifesto: Simplicity

A

Allows team members to focus on what is necessary to achieve the requirements needed to create and deliver value to the project and customer.

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

Agile Manifesto: Self-organization

A

a team that knows how to complete tasks effectively , has dedication to the project, and is expert on the process of the project

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

Agile Manifesto: Regular Reflection

A

This allows a team to learn how to become more effective, what changes need immediate implementation, and behavior that needs adjustment

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

Agile Mentoring

A

to pass on and teach based on experience, knowledge, and skills to other individuals in the team or that work for the organization

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

Agile Methodologies

A

a way to complete a goal effectively and efficiently.

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

Agile Modeling

A

A workflow depiction of a process or a system a team can review before it is turned in to code. Stakeholders shoulder understand the model.

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

Agile Planning

A

The most important aspect of the agile project. Planning happens at multiple levels such as strategic, release, iteration, and daily. Planning must happen upfront and can change throughout the project.

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

Agile practices

A

to make use of the agile principles through activities

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

Agile Smells

A

symptoms of a problem that effect agile teams and projects

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

Agile Space

A

a space that allows team members to establish collaboration, communication, transparency, and visibility.

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

Agile themes

A

Themes used to help the team focus on the functions of the iteration

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

Agile Tooling

A

To increase team morale through the use of software or artifacts

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

Analysis

A

To develop possible solutions by studying the problem and its underlying need and to understand the information provided

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

Approved iterations

A

after the deadline of iteration is reached, the team and stakeholders conduct a meeting for approval. Stakeholders approve the iteration if the backlog used supports the product increment.

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

Architectural Spikes

A

Spikes that relate to any area of a system, technology, or application domain that is unknown

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

Artifact

A

A process or work output ex: document, code

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

ASD

A

Exhibits continuous adaptation to the project and its process with characteristics that include: mission focused, feature based, iterative, time-boxed, risk driven, and change tolerant

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

Automated testing tools

A

These tools allow for efficient and strong testing. Examples: peer review, periodical code reviews, refactoring, unit tests, automatic and manual testing

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

Being Agile

A

to work in a responsive way to deliver the products or services the customer needs and when they want the products or services.

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

Brainstorming

A

an effective and efficient way of gathering ideas within a short period of time for a group

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

Burn-down chart

A

a chart used to display progress during and at the end of an iteration. Burning down means the backlog will lessen throughout the iteration

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

Burn Rate

A

the rate of resources consumed by the team. also cost per iteration

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

Burn-Up chart

A

A chart that displayed completed functionality. Progress will trend upward as stories are completed. only shows complete functions, it is not accurate at predicting or showing works in progress

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

CARVER

A

an acronym to measure the goals and missions of a project with each letter meaning Criticality, Accessibility , Return, Vulnerability, Effect, and Recognizability

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

Ceremony

A

A meeting conducted during an agile project which consists of daily standup, iteration planning, iteration review, and iteration retrospective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
45
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
46
Q

Charter

A

a document created during the initiation that formally begins the project. the document includes the projects 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
47
Q

Coach

A

a team role that keeps the team focused on learning the process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
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
49
Q

Collective code ownership

A

The entire team is responsible for 100% of the code

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

Collocation

A

The entire team is physically present working together in one room

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

Common Cause

A

an issue solved through trend analysis because the issue is systemic

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

Communication

A

To share smooth and transparent information of needs

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

Command and Control

A

Decisions created by higher up individuals in the organization and handed over to the team.

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

Compliance

A

To meet regulations, rules, and standards.

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

Cone of Silence

A

An environment for the team that is free of distractions and interruptions.

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

Conflict

A

Disagreements in certain areas between individuals.

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

Conflict Resolution

A

An agreement made after a conflict.

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

Continuous Improvement

A

To ensure that self-assessment and process improvement occurs frequently to improve the product.

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

Continuous Integration

A

To consistently examine a team member’s work. To build, and test the entire system.

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

Coordination

A

To organize work with the goal of higher productivity and teamwork.

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

Cost Performance Index (CPI)

A

To measure the cost spent on a project and its efficiency. Earned Value / Actual Cost = CPI

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

Cross-Functional Team

A

Teams that consist of members who can complete various functions to achieve a common goal. Team members are able to do more than one role in a project.

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

Crystal Family

A

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.

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

Cumulative Flow Diagram

A

A chart that displays feature backlog, work-in-progress, and completed features.

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

Customer-Valued Prioritization

A

To deliver the maximum customer value early in order to win customer loyalty and support.

66
Q

Cycle Time

A

The time needed to complete a feature (user story).

67
Q

Daily Stand Up

A

A brief meeting where the team shares the previous day’s achievements, plans to make achievements, obstacles, and how to overcome the obstacles.

68
Q

Decide As Late As Possible

A

To postpone decisions to determine possibilities and make the decision when the most amount of knowledge is available.

69
Q

DEEP

A

The qualities of a product backlog which include: detailed, estimate-able, emergent, and prioritized.

70
Q

Deliverables

A

A tangible or intangible object delivered to the customer. Ex. Document, Pamphlet, Report

71
Q

Disaggregation

A

To separate epics or large stories into smaller stories.

72
Q

Dissatisfaction

A

The lack of satisfaction among workers such as, work conditions, salary, and management-employee relationships. Factors known as demotivators.

73
Q

Distributive Negotiation

A

To reach a deal through tactics so both parties receive the highest amount of value possible.

74
Q

Done

A

When work is complete, and meets the following criteria: complies, runs without errors, and passes predefined acceptance and regression tests.

75
Q

Dot Voting

A

A system of voting where people receive a certain number of dots to vote on the options provided.

76
Q

Dynamic Systems Development Model (DSDM)

A

A model that provides a comprehensive foundation for planning, managing, executing, and scaling agile and iterative software development projects based on nine principles that involve business needs/value, active user involvement, empowered teams, frequent delivery, integrated testing, and stakeholder collaboration.

77
Q

Earned Value Management (EVM)

A

Earned Value Management, works well at iteration. It is a method to measure and communicate progress and trends at the current stage of the project.

78
Q

Emergent

A

Stories that grow and change overtime as other stories reach completion in the backlog.

79
Q

Emotional Intelligence

A

An individual’s skill to lead and relate to other team members.

80
Q

Epic Story

A

A large story that spans iterations, then disaggregated into smaller stories.

81
Q

Escaped Defects

A

Defects reported after the delivery by the customer.

82
Q

Expectancy Theory

A

An individual chooses to behave in a particular way over other behaviors because of the expected results of the chosen behavior.

83
Q

Exploratory Testing

A

To inquire how software works with the use of test subjects using the software and asking questions about the software.

84
Q

Extreme Persona

A

A team-manufactured persona that exaggerates to induce requirements a standard persona may miss.

85
Q

eXtreme Programming (XP)

A

A methodology in Agile with one-week iterations and paired development.

86
Q

Feature-Driven Development (FDD)

A

A comprehensive model and list of features included in the system before the design work begins.

87
Q

Feature

A

A group of stories that deliver value to the customers.

88
Q

Feedback

A

Information or responses towards a product or project used to make improvements.

89
Q

Fibonacci Sequence

A

A sequence of numbers used in Agile estimating, 0, 1, 2, 3, 5, 8, 13, 20, 40, 100.

90
Q

Finish Tasks One by One

A

Tasks must be finished in all iterations to meet the “Definition of Done” requirements as a way to track progress and allow frequent delivery.

91
Q

Fishbone Diagram

A

A root cause diagram.

92
Q

Five Whys

A

The root causes analysis technique that asks WHY five times. The problem is looked into deeper each time WHY is asked. Toyota developed this technique.

93
Q

Fixed Time Box

A

Assigned tasks prioritized for completion based on an estimated number of days. Top priorities are usually completed first.

94
Q

Force Field Analysis

A

To analyze forces that encourages or resists change.

95
Q

Functionality

A

An action the customer must see and experience from a system, which will add value to the customer.

96
Q

Grooming

A

To clean up the product backlog by removal of items, disaggregation of items, or estimation of items.

97
Q

Ground Rules

A

Unwritten rules decided and followed by team members.

98
Q

Herzberg’s Hygiene Theory

A

A theory that states factors in the workplace create satisfaction and dissatisfaction in relation to the job.

99
Q

High Performing Team

A

This team reaches maximum performance by creation of clear, detailed goals, open communication, accountability, empowerment, use of the participatory decision model, and the team consists of twelve dedicated members or less.

100
Q

Ideal Time

A

The amount of time needed to complete an assignment without distractions or interruptions.

101
Q

Information Radiator

A

Artifacts used to help maintain transparency of a project status to team members and stakeholders.

102
Q

Information Refrigerator

A

Information that is not transparent or useful to the team and stakeholders.

103
Q

Innovation Games

A

Practice used to induce requirements from product, owners, users, and stakeholders.

104
Q

Integrative Negotiation

A

To reach an agreement collaboratively that creates more value for both parties by a win-win solution.

105
Q

IRR

A

Internal Rate of Return- a discount rate that makes the net present value of all cash flows from a project equal to zero. Used to determine potential profitability of project or investment.

106
Q

Intraspectives

A

To inspect within, during a meeting with the Agile team to review practices, usually when a problem or issue occurs.

107
Q

Intrinsic Schedule Flaw

A

Poor estimation that occurs at the beginning of iteration.

108
Q

INVEST

A

The benefits of good user stories, which include: Independent, Negotiable, Valuable, Estimate-able, Small, and Testable.

109
Q

Iteration H

A

Iteration used to prepare the launch of software, and to test software.

110
Q

Iteration 0

A

Iteration to complete tasks before the development work occurs, for technical and architectural spikes and to gather requirements into the backlog.

111
Q

Kaizen

A

Based on Japanese management philosophy, to continue improvement through small releases.

112
Q

Kanban

A

A signal used to advance transparency of work-in-progress, a new task can begin once a previous one is complete.

113
Q

Kanban Board

A

A chart that shows workflow stages to locate work-in-progress.

114
Q

Kano Analysis

A

An analysis of product development and customer satisfaction based on needs fulfilled/not fulfilled vs. satisfaction/dissatisfaction.

115
Q

Little’s Law

A

The law that limits work-in-progress efficiently with development of an appropriate cycle time.

116
Q

Low Performing Team

A

This team has a lack of trust, no accountability, fear of conflict, less commitment, and less attention to details and results.

117
Q

Lean Software Development (LSD)

A

This methodology focuses on the “Value Stream” to deliver value to customers. The goal is to eliminate waste by focusing on valuable features of a system and to deliver the value in small batches. Principles of Lean include: elimination of waste, amplify learning, to decide late as possible, deliver as fast as possible, empowerment of the team, to build in integrity, and to see the whole.

118
Q

Maslow’s Hierarchy of Needs

A

This theory suggests the interdependent needs (motivators) of people based on five levels in this order: Physiological, Safety & Security, Social, Esteem, and Self-Actualization.

119
Q

Minimal Viable Product (MVP)

A

A product with only the essential features delivered to early adopters to receive feedback.

120
Q

Minimal Marketing Feature (MMF)

A

The smallest feature of a product that provides value to the end-user.

121
Q

MoSCoW Analysis

A

An analysis used to help stakeholders understand the importance of each requirement delivered. MoSCoW is the acronym for Must have, Should have, Could have, and Would like to have.

122
Q

NPV

A

Net Present Value- A value that compares the amount invested today to the present value of future cash receipts from the investment.

123
Q

Osmotic Communication

A

To communicate by sharing an environment.

124
Q

Pareto Principle

A

Known as the 80/20 rule. For Agile projects, it means that 80% of all development should be spent on the top 20% of the features the customers need.

125
Q

Participatory Decision Models

A

To have stakeholder’s involvement in decision making with techniques such as a simple vote.

126
Q

Persona

A

A depiction of the customer of system with applicable details about usage.

127
Q

Pig

A

A committed individual impacted by the outcome.

128
Q

Plan-Do-Check-Act

A

Work cycle in smaller, quick iterations than traditional.

129
Q

Planning Game

A

To prioritize work and estimate effort required by creation of a release plan in XP.

130
Q

Pre-Mortem

A

Team members asked to define reasons of a project’s failure and to identify causes of failure missed in previous analyses.

131
Q

Present Value

A

A way to calculate the time value of money.

132
Q

Process Tailoring

A

To perfect agile processes for a particular project and environment.

133
Q

Productivity Variation

A

The difference between the planned and actual performance.

134
Q

Product Vision

A

A document that describes what the product is, who will use the product, why the product will be used, and how the product supports the strategy of a company.

135
Q

Product Vision Statement

A

A statement that defines the purpose and value of the product.

136
Q

Progressive Elaboration

A

An approach for planning that occurs in cycles instead of upfront, which happens frequently.

137
Q

Requirements at a High Level

A

Requirements are in the form of user stories, and collected at a high level to estimate a budget.

138
Q

Requirements Prioritization Model

A

A model to rate each feature with the calculation of weighted formula defined by the team.

139
Q

Requirements Review

A

To review the requirements so they fulfill the needs and priorities of stakeholders.

140
Q

ROI

A

Return on Investment- The return an organization makes on an investment expressed by a percentage.

141
Q

Risk-Adjusted Backlog

A

A product backlog adjusted to help balance the risk and value factors of product.

142
Q

Risk-Based Spike

A

This spike helps the team remove major risks, and if the spike fails every approach possible, the project is defined as “fast failure”.

143
Q

Risk Burn Down

A

A chart that displays risk and success with feature vs. time.

144
Q

Risk Impact

A

To analyze the consequences of the risk if they occur based on their probability.

145
Q

Risk Severity

A

How much the risk’s consequences will influence the success or failure of a project. Risk Probability (%) x Risk Impact ($) = Risk Severity

146
Q

Schedule Performance Index

A

The ratio of earned value to planned value. EV/PV=SPI.

147
Q

Self-Directing Team

A

This team has the capability to make their own decisions, empowerment, mutual accountability, and collective ownership of a project, which leads them to be more productive and efficient.

148
Q

Self-Organizing Team

A

Naturally formed teams that interact with minimal management supervision.

149
Q

Servant Leadership

A

Leaders collaborate with the team and do anything the team does when needed.

150
Q

Shu-Ha-Ri Model

A

Originated in Japan as a way to understand learning and mastery, Shu – obeying the rules, Ha - consciously moving away from the rules, and Ri – consciously finding an individual path.

151
Q

Specification Breakdown

A

This occurs when requirements for the specification are incomplete or conflicting.

152
Q

Story Map

A

A prioritization tool that backlogged stories made smaller and organized by user functionality.

153
Q

Tabaka’s Model

A

A model originated in Japan to describe a team with values that include self-organization, empowered to make decisions, belief in vision and success, a committed team, trust, participatory decision making, consensus-driven, and construction disagreement.

154
Q

Technical Debt

A

Technical decisions a team chooses to not implement currently, but must do so or face difficulty in the future.

155
Q

Test-Driven Development (TDD)

A

A written acceptance test for a module with the code built to pass the tests in order to ensure correct performance.

156
Q

Tracker

A

A role in XP that measures the team’s progress, and communicates the measurements to the team.

157
Q

Trend Analysis

A

This analysis provides trends that will occur in the future to help control and implement continuous improvement.

158
Q

Two-Way Communication

A

To allow communication between parties so their concerns and perspectives are given for effective feedback.

159
Q

Usability Testing

A

An exploratory test which uses a test subject to understand the usability of software.

160
Q

Users Involvement

A

The active involvement of users in the development cycle of a project so team members can receive feedback about the user’s requirements.

161
Q

Value-Based Prioritization

A

To allow the PO or customer determine which function to implement first based on the value it delivers.

162
Q

Value-Driven Delivery

A

To realize the values needed to deliver a project.

PMI-ACP Prep (1 decks)

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