Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
11 Cards in this Set
- Front
- Back
|
Acceptance Testing |
Formal testing done to verify that a system satisfies its acceptance criteria. Enables the customer to determine whether or not to accept the system. |
|
|
Backlog |
A collection of stories and tasks the team will work on at some point in the future. Either they have not been prioritized or have a lower priority. |
|
|
Burndown Chart |
A chart that depicts the total task hours remaining per day. It shows where the team stands regarding completing the tasks that comprise the backlog for the particular sprint. |
|
|
Chicken |
Anyone who is interested in a project but has no responsibility for working on a task in the active iteration. They may observe team meetings but cannot vote or talk. |
|
|
Pig |
Actively involved members of an iteration (opposite of Chickens). |
|
|
Continuous Integration |
Team members integrate their work to the main branch of a project frequently (at least daily). Each integration is verified for defects to be resolved quickly as possible. |
|
|
Scrum |
A daily meeting held to provide a status update to team members. Allows members to be aware of potential challenges as well as coordinate effort to resolve difficult and/or time-consuming issues. |
|
|
Extreme Programming (XP) |
Software development methodology adhering to a very iterative and incremental approach. Advocates for frequent releases and short development cycles (timeboxing). |
|
|
Scrum Master |
Responsible for maintaining the scrum process and the overall health of the team. |
|
|
Sprint |
The agile term for iteration. |
|
|
Unit Testing |
A unit is the smallest testable part of a software system. Usually the responsibility of the developer. |
