Chapter 2 - Agile Framework Flashcards Preview

PMI-ACP > Chapter 2 - Agile Framework > Flashcards

Flashcards in Chapter 2 - Agile Framework Deck (45)
Loading flashcards...
1
Q

What are the four agile values?

A

Individuals and interactions over Processes and tools
Working software over Comprehensive documentation
Customer collaboration over Contract negotiation
Responding to change over Following a plan

2
Q

Working software over?

A

Comprehensive documentation

3
Q

Responding to change over?

A

Following a plan

4
Q

Individuals and interactions over?

A

Processes and tools

5
Q

Customer collaboration over?

A

Contract negotiation

6
Q

Guiding principle: Our highest priority is to satisfy the customer through doing what?

A

early and continuous delivery of valuable software

7
Q

Guiding principle: how do we consider changing requirements?

A

We welcome changing requirements, even late in development for the customer’s competitive advantage

8
Q

Guiding principle: How frequently do we deliver working software?

A

From couple of weeks to couple months, with a preference for the shorter timescale

9
Q

Guiding principle: How often must business people and developers work together?

A

Daily throughout the project

10
Q

Guiding principle: Build projects around motivated individuals. what do you need to give them?

A

the environment and support they need, and trust them to get the job done.

11
Q

Guiding principle: what’s the most efficient and effective way of conveying information to and within a development team?

A

Face to face conversation

12
Q

Guiding principle: What’s the primary measure of progress?

A

Working software

13
Q

Guiding principle: What do Agile processes promote in terms of work-life balance?

A

Sustainable development. The sponsors, developers and users should be able to maintain constant pace indefinitely

14
Q

Guiding principle: What needs to be paid attention to in order to enhance agility?

A

Technical excellence and good design

15
Q

Guiding principle: what is essential regarding work to be done?

A

Simplicity - the art of maximizing the work not done

16
Q

Guiding principle: Where do the best architectures, requirements and designs emerge from?

A

Self-organizing teams

17
Q

Guiding principle: what reflection does the team have at regular intervals?

A

It reflects on how to become more effective, then tunes and adjusts its behavior accordingly

18
Q

What are the 3 pillars of Scrum?

A

Transparency, Inspection and Adaptation

19
Q

What does “grooming” the product backlog mean?

A

it is the process of adding more detail and order to the backlog and refining the estimates of the backlog items

20
Q

What are the core values of XP?

A

Simplicity, Communication, Feedback, Courage, Respect

21
Q

How long is a typical iteration in XP

A

2 weeks

22
Q

What does generalizing specialists mean?

A

People can take up multiple roles

23
Q

Which roles does a XP team include?

A

A customer, developers, QA, BA. Sometimes a coach and a manager

24
Q

How many planning games does XP have and which ones?

A

2: release planning and iteration planning

25
Q

How is the XP practice of all contributors sitting together in the same location called?

A

Whole Team

26
Q

How is the XP practice of frequently releasing software to the Test environment called?

A

Small Releases

27
Q

How is the XP practice of the customer describing one or more tests to show that the software works called?

A

Customer Tests

28
Q

How is the XP practice of multiple people working on the code called?

A

Collective Code Ownership

29
Q

How is the XP practice of the team taking a consistent approach to coding called?

A

Code Standards

30
Q

How is the XP practice of avoiding repeated long hours of work called?

A

Sustainable Pace

31
Q

How is the XP practice of using descriptions that all the stakeholders can understand called?

A

Metaphor

32
Q

How is the XP practice of running integration tests each time a developer checks in code?

A

Continuous Integration

33
Q

How is the XP practice of writing tests prior to code called?

A

Test-Driven Development

34
Q

How is the XP practice of improving the design of existing code without altering the external behavior called?

A

Refactoring

35
Q

How is the XP practice of keeping the design simple but adequate called?

A

Simple Design

36
Q

How is the XP practice of two developers producing the same code called?

A

Pair Programming

37
Q

What is a “Feature Team”?

A

Dynamically formed team that vets designs and allow multiple design options to be evaluated before a design is chosen

38
Q

How are reviews that help ensure good quality design and code called in FDD?

A

Inspections

39
Q

How is the FDD practice of teams exploring and explaining the business domain called?

A

Domain object modelling

40
Q

How is the FDD practice of breaking functions down into 2-week or shorter chunks and calling them features called?

A

Developing by feature

41
Q

How is the FDD practice of code having a single owner called?

A

Individual class (code) ownership

42
Q

How is the FDD practice of labeling code, tracking changes and managing source code called?

A

Configuration management

43
Q

How is the FDD practice of making sure the new code integrates with existing code called’

A

Regular builds

44
Q

How is the FDD practice of tracking progress based on completed work called?

A

Visibility of progress and results

45
Q

What does DSDM stand for?

A

Dynamic Systems Development Method