Brainscape's Knowledge GenomeTM

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


See full index

PMI-ACP Exam > PMI-ACP Study Cards > Flashcards

PMI-ACP Study Cards Flashcards

1
Q

Refers to different types of iterative development.

Build things in small increments.

Scum is the most common method of agile.

A

Agile

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

Who is the designated person that represents the customer on the project?

A

Product Owner

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

What are the 4 Values of Agile Manifesto

A
  1. Individuals & Interactions Over Processes and tools
  2. Working Software Over Comprehensive Documentation
  3. Customer Collaboration Over Contract Negotiation
  4. Responding to Change Over Following a Plan.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Is used in XP to explain designs and create a shared vision between customers and development team.

A

Metaphor

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

The bottleneck activity is the one immediately after the widening activity

A

Cumulative Flow Diagram

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

This will show how much points are worth of work the team is conducting per iteration.

A

Velocity Chart

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

This is when you bring a panel of experts together and anonymously get their opinions to come up with a decision such as estimations on story points.

A

Wideband Delphi

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

This is defined as when one programmer writes the code another inspects the code as it’s been written.

A

Pair Programming

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

What one person describes, is often different from how another person interprets it

A

Gulf of Evaluation

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

This displays work that remains to be done

A

Burn down Chart

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

The team inspects the methods they used to build an increment

A

Sprint Retrospective

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

Used in XP when the team writes tests prior to developing the code

A

Test Driven Development

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

Planning is done at multiple points in time as data becomes available

A

Rolling Wave Planning

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

A visual representation of the flow of information through a process in which you can identify waste such as waiting time and optimize the process

A

Value Stream Map

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

This optimization as a whole is to see a system more than the sum of its pasts

A

Lean Software Development

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

Provides information on something that has already happened.

A

Lagging Metrics

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

When will customers have the ability to evaluate the completed increment that was done in that Sprint and to provide their feedback?

A

Sprint Review Meeting

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

What activity is done during the step of generate insights into the data?

A

Fishbone Analysis

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

Who determines and prioritizes the next iteration?

A

The Product Owner

20
Q

When product conforms to the specifications?

A

Verification

21
Q

Has no value in Agile Projects

A

Work In Progress (WIP)

22
Q

What two factors should be considered when calculating total cycle time?

A

Value-Added and Non-Value-Added Time

23
Q

Deliver Fast
Empower The Team
Eliminate Waste
Create Knowledge
Build Quality In
Delay Decision Making
Optimize the whole

A

Lean Software Development Principles

24
Q

Serves as a Product Roadmap

A

Story Maps

25
Q

Set the Stage
Gather Data
Generate Insights
Decide What To Do
Close The Retrospective

A

Sprint Retrospective

26
Q

Short Iterations
Many Unknowns
Expects Change
It’s invisible

A

Knowledge Work

27
Q

Based on our experience and observations?

A

Empirical

28
Q

Three Pillars of Scrum

A

Transparency
Inspection
Adaption

29
Q

Welcome and expect change

Create small value - added increments

Feedback loops

Constantly learn through discovery and creativity

Focus on developing a value for stakeholders

It’s okay to fail fast

Deliver value throughout the project

Constantly improve upon the project and the project work.

A

Core Principles of Agile

30
Q

Which Manifesto are the following related to:

Most important

Projects are completed by people not processes and tools

Agile projects are people driven

A

Individual and Interactions over Processes and Tools

31
Q

Which Manifesto are the following related to:

Value is about the purpose

Documentation is barely sufficient

Documentations adds no value

A

Working Software Over Comprehensive Documentation

32
Q

Which Manifesto are the following related to:

Agile is flexible, accommodating, and willing to change.

Contracts are often ridge/uncooperative

Agile Contracts must accommodate changes

A

Customer Collaboration Over Contract Negotiation

33
Q

Which Manifesto are the following related to:

Agile Welcomes Change

Agile Projects have uncertainty upfront

A

Responding To Change Over Following a Plan

34
Q

Most important items are worked on first

Always prioritized before the current sprint

The team estimates their capacity to attack the items

A

Product Backlog

35
Q

What are the Scrum Artifacts

A

Product Increment

Product Backlog

Sprint Backlog

36
Q

Subset of the product backlog

The work we’re doing for the current sprint

Goal for the current iteration

Updated and refined by the development team

A

Sprint Backlog

37
Q

Define and Write the acceptability tests

A

Testers

38
Q

XP Team Roles

A

Coach
Customer
Programmer
Testers

39
Q

The developers who write the code

A

Programmer

40
Q

Compiling the code frequently throughout the day

Programmers check-in code to the code repository

A

Continuous Integration

41
Q

Cleaning up the code
Removing duplicated code
Increase Cohesion

A

Refactoring

42
Q

What is Simple Design (XP Core)?

A

Simple design is a risk mitigation approach

keeping things simple and straightforward

43
Q

Backlog of things that should be done but aren’t because of a push to deliver featured. This increases the cost of the project.

A

Technical Debt

44
Q

Making sure that the product manufactured is acceptable to the customers.

A

Validation

45
Q

Is a period of time where designated work is completed.

A

Timebox

46
Q

Product confirms to the specifications

A

Verification

PMI-ACP Exam (4 decks)

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