Vocabulary Flashcards

1
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
2
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
3
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
4
Q

Agile Adaptation

A

To adaption 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
5
Q

Agile Coaching

A

To help achieve goals that is either personal or organizational

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

Agile Manifesto: Customer Satisfaction

A

To satisfy customer 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
9
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 edge

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

Agile Manifesto: Working Software

A

Working software enables the measurement of progress, enhance customer satisfaction, and maintain and improve 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
15
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
16
Q

Agile Manifesto: Continuous Attention

A

To enhance agility and time spent on work requirements in order to retain a well-balanced work environment.

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

18
Q

Agile Manifesto: Self-Organization

A

A team that knows how to complete tasks effectively, has dedication to the project, and is expert on the process and project.

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

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

21
Q

Agile Methodologies

A

A way to complete a goal effectively and efficiently. Examples of Agile Methodologies include XP, Scrum, and Lean.

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

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

24
Q

Agile Smells

A

Symptoms of problems that affect Agile teams and projects.

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

26
Q

Architectural Spikes

A

Spikes that relate to any area of a system, technology, or application domain that is unknown.

27
Q

Artifact

A

A process or work output Ex. Document, Code

28
Q

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.

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

30
Q

CARVER

A

An acronym to measure the goals and mission of the project with each letter meaning: Criticality, Accessibility, Return, Vulnerability, Effect, and Recognizeability.

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

32
Q

Ceremony

A

A meeting conducted during an Agile project that consists of daily stand-up, iteration planning, iteration review, and iteration retrospective.

33
Q

Chicken

A

An individual involved but not committed to an Agile project.

34
Q

Collective Code Ownership

A

The entire team together is responsible for 100% of the code.

35
Q

Continuous Integration

A

To consistently examine a team member’s work. To build, and test the entire system.

36
Q

Cost Performance Index (CPI)

A

To measure the cost spent on a project and its efficiency. Earned Value / Actual Cost = CPI

37
Q

Crystal Family

A

An adaptable approach that focuses on interaction between people and processes that consists of families that vary based on team size, system criticality, and project priorities.

38
Q

Cumulative Flow Diagram

A

A chart that displays feature backlog, work-in-progress, and completed features.