Brainscape's Knowledge GenomeTM

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


See full index

APM-CERT > Agile Manifesto > Flashcards

Agile Manifesto Flashcards

1
Q

Principles behind the Agile Manifesto 1.

A
  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Principles behind the Agile Manifesto 2.

A
  1. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Principles behind the Agile Manifesto 3.

A
  1. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Principles behind the Agile Manifesto 4.

A
  1. Business people and developers must work together daily throughout the project.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Principles behind the Agile Manifesto 5.

A
  1. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Principles behind the Agile Manifesto 6.

A
  1. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Principles behind the Agile Manifesto 7.

A
  1. Working software is the primary measure of progress.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Principles behind the Agile Manifesto 8.

A
  1. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Principles behind the Agile Manifesto 9.

A
  1. Continuous attention to technical excellence and good design enhances agility.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Principles behind the Agile Manifesto 10.

A

10 .Simplicity–the art of maximizing the amount of work not done–is essential.

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

Principles behind the Agile Manifesto 11.

A
  1. The best architectures, requirements, and designs emerge from self-organizing teams.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Principles behind the Agile Manifesto 12.

A
  1. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

SCRUM pillar 1

A

Trasparency: This pillar involves giving visability to those responsible for the outcome

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

SCRUM pillar 2

A

Inspection: This pillar involves timely checks on how well a project is processing towards its goals, looking for problematic deviation or differences from the goals

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

SCRUM pillar 3

A

Adaptation: This pillar involves adjusting a process to minimize further issues if an ispection shows a problem or undesirable tred.

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

Development Team

A

who build the product increments in each iteration (sprint). The Development Team manages own work, are sel-organized and cross-functional

17
Q

Produc Owner

A

is responsible for mixmizing the value of the product. This person has the sole responsability for managing the product backlogs (prioritization. accurancy, shared understanding, value and visibility)

18
Q

SCRUM Master

A

is the responsible for ensuring that SCRUM is understood and used. He’s the servant leader to the development team, removing impediments to progress, facilitating events as needed. and providing coaching. ScrumMaster assists the product owner with managing the backlog and comunicating the vison, goal, and backlog item to development team.

19
Q

Sprints

A

A sprint is a timeboxed (time-limited) to build a potentially releasable product (like a mini-project). Each sprint includes a sprint planning meeting, daily scrumb, the development work a sprint review mwwting and review retrospective.

20
Q

Spring Planning Meeting

A

is used to determine what will be delivered in that sprint and how the work will be achived. The produc owner presents the backlog itmes and the whole team discusses them to create a shared understanding. Here the development team willl define what will be delivered on in the next sprit goal

21
Q

Daily SCRUM

A

is the 15 minutes timeboxed daily meeting. Here the development team synchronizing activites, communicates, and raises issues. it is held the same place and time.

  1. What has been achieved since the last meeting?
  2. What will be done before the next meeting?
  3. What obstacle are in the way?

ScrumMaster makes sure these meetings happen and helps obstacles

22
Q

Sprint Review

A

is a meeting held at the end of the sprint to iinspect the increment, or evolving product (backlog can change). The development team demonstrates the work that is done

23
Q

Sprint Retrospective

A

team reflect o the process and look for opportunities for improvments (team incorporate the product owner’s feedbacks)

24
Q

Product Backlog

A

is the ordered list of everithing that might be needed for the product. It serves as the single source for requirements. Backlog is dynamic and evolves as the product. it contains all requirements. Grooming is the process of adding more detail and order to the backlog and refining the estimates of the blacklog item.(grooming is done by development team and product owner)

25
Q

Sprint Backlog

A

is the set of items from the product backlog that were selected for a specific sprint

26
Q

Definition of Done

A

agreement on what means “done”

27
Q

Extreme Programming is a software-development-centric agile method. While Scrum at the project management level focuses on prioritizing work and getting feedback, XP focuses on software development good pratices.

A

Simplicity (FInd the simplest thing that could possibility work)

Communication. (the Daily stand-up meeting is a key communication component)

Feedback (Failing fast can be useful, especially if in doing so)

Courge (It takes courge to allow our work to be entirely visible to others.

Respect. Respect is essential on XP projects where people work together as a team and everyone is accountable for the succes or failure of hte project

Architectural spikes are iterations used to prove a technological approach, and spikes are periods of work undertaken to reduce risks.

28
Q

4 First level

A

4 First level:

Whole Team (XP emphizes the notion of generalizing specialists, as opposed to role specialists)

**Planning Games **()

Small Releases (Frequent, small releases to test environments are encuraged in XP)

Customer Test (the customer provide one ore more tests to show that the softwarei is working)

29
Q

5 Second level

A

Collective Code Ownership

Code Standards

Sustainable Pace

Metaphor (create a shared technical vsion)

Continuous Integration

30
Q

4 tirdh level

A

Test-Driven Development

Refactoring

Simple Design (what is the simplest thing that could work?)

Pair Programming

APM-CERT (2 decks)

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