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
Set the Stage Gather Data Generate Insights Decide What To Do Close The Retrospective
Sprint Retrospective
26
Short Iterations Many Unknowns Expects Change It's invisible
Knowledge Work
27
Based on our experience and observations?
Empirical
28
Three Pillars of Scrum
Transparency Inspection Adaption
29
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.
Core Principles of Agile
30
Which Manifesto are the following related to: Most important Projects are completed by people not processes and tools Agile projects are people driven
Individual and Interactions over Processes and Tools
31
Which Manifesto are the following related to: Value is about the purpose Documentation is barely sufficient Documentations adds no value
Working Software Over Comprehensive Documentation
32
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
Customer Collaboration Over Contract Negotiation
33
Which Manifesto are the following related to: Agile Welcomes Change Agile Projects have uncertainty upfront
Responding To Change Over Following a Plan
34
Most important items are worked on first Always prioritized before the current sprint The team estimates their capacity to attack the items
Product Backlog
35
What are the Scrum Artifacts
Product Increment Product Backlog Sprint Backlog
36
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
Sprint Backlog
37
Define and Write the acceptability tests
Testers
38
XP Team Roles
Coach Customer Programmer Testers
39
The developers who write the code
Programmer
40
Compiling the code frequently throughout the day Programmers check-in code to the code repository
Continuous Integration
41
Cleaning up the code Removing duplicated code Increase Cohesion
Refactoring
42
What is Simple Design (XP Core)?
Simple design is a risk mitigation approach keeping things simple and straightforward
43
Backlog of things that should be done but aren’t because of a push to deliver featured. This increases the cost of the project.
Technical Debt
44
Making sure that the product manufactured is acceptable to the customers.
Validation
45
Is a period of time where designated work is completed.
Timebox
46
Product confirms to the specifications
Verification