Brainscape's Knowledge GenomeTM

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


See full index

Udemy PMP > Agile > Flashcards

Agile Flashcards

1
Q

ACP

A

Agile Certified Practitioner

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

Agile

A

To develop a goal through periodic experimentation in order to fulfill the need of a complex decision.

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

Affinity Estimation

A

A method used to quickly place user stories into a comparable-sized group.

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

Agile Adaption

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 either personal 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 over 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.
-Customer satisfaction
-Welcome changes
-Frequent delivery
-collocated team
-motivated individuals
-face to face conversatoin
-working software
-constant pace
-continuous attention
-simplicity
-self-organization
-regular reflection

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

Agile Manifesto: Customer Satisfaction

A

To satisfy customers through early and continuous delivery of products, to test and receive feedback, to inform customers on progress, and to fulfill the customer’s 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 changes in the external environment, and late in development to maximize the customer’s 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 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, environment, support, and trust needed to complete a task successfully.

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

Agile Manifesto: Face-to-Face Conversation

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, enhances customer satisfaction, and maintains and improves 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 for 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 retain 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 an expert on the process and 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. Examples of Agile Methodologies include XP, Scrum, and Lean.

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 system a team can review before it is turned into code. Stakeholders should 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 up-front and can change throughout the project.

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

Agile Smells

A

Symptoms of problems that affect Agile teams and projects.

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

Agile Themes

A

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

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

Agile Tooling

A

To increase team morale with software or artifacts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
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
32
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
33
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
34
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
35
Q

Adaptive Software Development (ASD)

A

Exhibits continuous adaptation to the project and its processes 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
36
Q

Automated Testing Tools

A

These tools allow for efficient and strong testing. Examples: Peer Reviews, 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
37
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.
Burn rate = cost per iteration.

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

Burn-Up Chart

A

A chart that displays completed functionality. Progress will trend upwards, as stories are completed. Only shows complete functions, it is not accurate at predicting or showing work-in-progress.

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

CARVER

A

An acronym to measure the goals and mission of the 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
40
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
41
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
42
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
43
Q

Common Cause

A

An issue solved through trend analysis because the issue is systematic.

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

Command & 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
45
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
46
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
47
Q

Cross-Functional Team

A

Teams that consist of members who can multi-task well and complete various functions to achieve a common goal.

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

Crystal Family

A

An adaptable approach that focuses on the 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
49
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
50
Q

Customer-Valued Prioritization

A

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

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

Cycle Time

A

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

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

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

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

DEEP

A

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

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

Disaggregation

A

To separate epics or large stories into smaller stories.

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

Distributive Negotiation

A

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

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

Done

A

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

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

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

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

Emergent

A

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

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

Epic Story

A

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

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

Escaped Defects

A

Defects reported after the delivery by the customer.

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

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

Exploratory Testing

A

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

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

Extreme Persona

A

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

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

eXtreme Programming (XP)

A

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

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

Feature-Driven Development (FDD)

A

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

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

Feature

A

A group of stories that deliver value to the customers.

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

Fibonacci Sequence

A

The traditional Fibonacci sequence is 1, 2, 3, 5, 8, 13, 21, 34, and so on. In Agile projects, this sequence is modified. The modified Fibonacci sequence is 0, 1, 2, 3, 5, 8, 13, 20, 40, 100 - it is used to estimate the relative size of User Stories in terms of Story Points.

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

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

Fishbone Diagram

A

A root cause diagram.

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

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

Fixed Time Box

A

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

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

Force Field Analysis

A

To analyze forces that encourage or resist change.

75
Q

Grooming

A

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

76
Q

High-Bandwidth Communication

A

Face-to-face communication also includes non-verbal communication.

77
Q

High Performing Team

A

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

78
Q

Ideal Time

A

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

79
Q

Information Radiator

A

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

80
Q

Information Refrigerator

A

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

81
Q

Innovation Games

A

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

82
Q

Integrative Negotiation

A

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

83
Q

Interaction

A

Face to face comms

84
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 the potential profitability of project or investment.

85
Q

Intraspectives

A

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

86
Q

Intrinsic Schedule Flaw

A

Poor estimation occurs at the beginning of the iteration.

87
Q

INVEST

A

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

88
Q

Iteration

A

Work cycle, Scrum uses 2-4 weeks, XP uses 1 week.

89
Q

Iteration Backlog

A

Work to complete in a particular iteration.

90
Q

Iteration H

A

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

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

92
Q

Iteration Retrospective

A

A meeting used in Scrum, the team discusses ways to improve after work is completed.

93
Q

Just-In-Time

A

Used to minimize inventory cost by materials delivered before they are required.

94
Q

Kaizen

A

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

95
Q

Kanban

A

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

96
Q

Kanban Board

A

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

97
Q

Kano Analysis

A

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

98
Q

Last Responsible Moment

A

To make decisions as late as possible in order to preserve all possible options.

99
Q

Lean Methodology

A

To eliminate waste, an Agile method derived from manufacturing.

100
Q

Little’s Law

A

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

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

102
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 value in small batches. Principles of Lean include: elimination of waste, amplify learning, to decide late as possible, deliver as fast as possible, empowerment the team, building integrity, and seeing the whole.

103
Q

Minimal Viable Product (MVP)

A

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

104
Q

Minimal Marketing Feature (MMF)

A

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

105
Q

Monopoly Money

A

To give fake money to business features in order to compare the relative priority of those features.

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

107
Q

Osmotic Communication

A

To communicate by sharing an environment.

108
Q

Pair Programming

A

When developers work together in XP Practice

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

110
Q

Participatory Decision Models

A

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

111
Q

Persona

A

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

112
Q

Pig

A

A committed individual impacted by the outcome.

113
Q

Plan-Do-Check-Act

A

Work cycle in smaller, quick iterations than traditional.

114
Q

Planning Game

A

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

115
Q

Planning Poker

A

A tool used to estimate team effort on user stories.

116
Q

Positive Value

A

To maximize value through incremental work in order to gain a competitive advantage.

117
Q

Pre-Mortem

A

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

118
Q

Productivity Variation

A

The difference between the planned and actual performance.

119
Q

Product Backlog

A

The known features for a project.

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

121
Q

Refactoring

A

To adjust working code to improve functionality and conservation.

122
Q

Relative Prioritization

A

A list of all user stories and features ordered by highest priority to the lowest priority.

123
Q

Relative Sizing

A

To estimate the size of a story in comparison with another story.

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

125
Q

Requirements Prioritization Model

A

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

126
Q

Requirements Review

A

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

127
Q

Risk-Adjusted Backlog

A

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

128
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”.

129
Q

Risk Burn Down

A

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

130
Q

Risk Impact

A

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

131
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

132
Q

Rolling Wave Planning

A

To divide the planning phase into stages.

133
Q

Scrum

A

A popular Agile methodology.

134
Q

Scrum of Scrums

A

Meetings used to organize large projects with scrum masters from different teams.

135
Q

Software Development Life Cycle (SDLC)

A

This cycle tends to be long and requires a lot of advanced planning.

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

137
Q

Self-Organizing Team

A

Naturally formed teams that interact with minimal management supervision.

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

139
Q

Special Cause

A

A cause that occurs once because of special reasons.

140
Q

Specification Breakdown

A

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

141
Q

Spike

A

An experiment that helps a team answer, a particular question and determines future actions.

142
Q

Sprint

A

A consistent iteration that lasts from one week to one month in order to measure velocity in Scrum.

143
Q

Sprint Plan

A

A document that explains sprint goals, tasks, and requirements and how the tasks will reach completion.

144
Q

Sprint Retrospective

A

A team-member meeting occurs after each sprint to evaluate the product and process to improve efficiency and effectiveness.

145
Q

Sprint Review

A

A meeting that occurs after each sprint to show the product or process to stakeholders for approval and to receive feedback.

146
Q

Story Card

A

An index card that displays the user story.

147
Q

Story Map

A

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

148
Q

Story Point

A

A unit of measurement to estimate the difficulty of a user story.

149
Q

Swarming

A

When the team collaborates to focus on a single user story.

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

151
Q

Tasks

A

The smaller jobs to fulfill a user story, usually divided among team members.

152
Q

Team Empowerment

A

A team that is empowered has collaboration, responsibility, and self-sufficiency.

153
Q

Team Formation

A

Formation happens when a team creates ground rules and processes to build bonds and shared goals.

154
Q

Team Participation

A

When the team discusses the requirements that will fulfill the customer’s needs.

155
Q

Team Space

A

An area for team members to collocate, usually a physical location, in some cases a virtual location is created.

156
Q

Team Velocity

A

The number of story points completed during iteration and used to determine the planned capacity.

157
Q

Technical Debt

A

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

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

Red - Green -

159
Q

Tester

A

Explains acceptance test to the customers then consistently measures the product against the test and records results for the team. (XP Role)

160
Q

Theme

A

A group of stories, iteration, or releases idea determined by the customer, and the team agrees with the idea.

161
Q

Time-boxing

A

To set a fixed delivery date for a project or release.

162
Q

Unit Testing

A

These tests are used for continuous feedback to achieve quality improvement and assurance.

163
Q

Usability Testing

A

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

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

165
Q

User Story

A

At least one business requirement increases the value for the user.

166
Q

Validation

A

The way to make sure that the product is acceptable to the customer.

167
Q

Value-Based Prioritization

A

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

168
Q

Value-Driven Delivery

A

To realize the values needed to deliver a project.

169
Q

Value Stream Mapping

A

A tool used to analyze a chain of processes with the desired outcome of eliminating waste.

170
Q

Velocity

A

The total number of features that a team delivers in an iteration.

171
Q

Verification

A

To ensure the product meets requirements and specifications.

172
Q

Waterfall

A

Resistant to change that requires heavy planning and a sequential, traditional approach.

173
Q

Wide-Band Delphi Estimating

A

An estimation technique for user stories. The PO presents user stories & discusses challenges. Each story’s estimates plotted, and then the team comes to an agreement on the range of points.

174
Q

WIP Limits

A

To limit work-in-progress so a team can do the following: maintain focus on completing work, maintaining quality, and delivering value.

175
Q

Wireframe

A

A lightweight non-functional UI design that shows the customer the vital elements and how they will interact before coding.

176
Q

WIP

A

Work-In-Progress- Stories that have started, which are displayed in workflows to show progress and what still needs to be completed.

177
Q

Workflow

A

A series of phases or stages the team has agreed to execute for a project.

178
Q

100-Point Method

A

A method that allows customers to score (total 100 points) different features of a product.

179
Q

Agile Approaches and Methods

A

Kanban, scrum, XP, FDD, DSDM, AUP, and Crystal.

180
Q

Definable Work

A

Clear procedures based on similar past projects

181
Q

3 Cs of User Stories

A

Card, conversation, confirmation

182
Q

Use Case Diagram

A

A use case model consists of a use case diagram and narrative text detailing the use cases. The diagram is a picture of the system, actors, and use cases. It contains the system boundary, called a boundary box, the actors, and the use cases.

183
Q

Acceptance Test

A

Formal description of a software product, expressed as an example of a usage scenario.

184
Q

Highsmith Decision Spectrum

A

People can indicate support and reservations at same time.

Udemy PMP (15 decks)

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