ADVANCED SOFTWARE DEVELOPMENT FINAL
EXAM LATEST QUESTIONS AND ANSWERS
(VERIFIED ANSWERS)
Planning Game - ANS-Very short (1-2 week) iterations. Features broken down into stories, estimated and
chosen. Some cannot exceed the total completed from last week
Whole Team - ANS-Team has diverse skills, work in close, open area
Acceptance Tests - ANS-Stories/features defined by automated tests. These premade suites must pass
for story/feature to pass
Small Releases - ANS-Release very frequently. 2-3 month maximum. Incremental versions
Continuous Integration - ANS-System must be deployable at all times.
Collective Ownership - ANS-Code is not owned by individuals, anyone can work on anything
Coding Standard - ANS-Must follow team coding standards, not individual preference
Metaphor - ANS-Names w/i code suggestive to system being created. Appropriate variable names
Sustainable Pace - ANS-Tired people don't win
Pair Programming - ANS-Code produced by two individuals, working together. Pairs change frequently
TDD - ANS-No code until you have a failing unit test
Refactoring - ANS-Go back and update code to make it cleaner and simpler
Simple Design - ANS-The system should be designed as simple as possible
XP - ANS-Popular early agile method. Had practices, principles, and values. Today, scrum has only the
practices.
User Stories - ANS-Simple form of stating requirements. As a [type of user], i want to [do action]. Very
high-level, nothing about implementation
Product Backlog - ANS-Complete set of stories that describe what the entire system does.
EXAM LATEST QUESTIONS AND ANSWERS
(VERIFIED ANSWERS)
Planning Game - ANS-Very short (1-2 week) iterations. Features broken down into stories, estimated and
chosen. Some cannot exceed the total completed from last week
Whole Team - ANS-Team has diverse skills, work in close, open area
Acceptance Tests - ANS-Stories/features defined by automated tests. These premade suites must pass
for story/feature to pass
Small Releases - ANS-Release very frequently. 2-3 month maximum. Incremental versions
Continuous Integration - ANS-System must be deployable at all times.
Collective Ownership - ANS-Code is not owned by individuals, anyone can work on anything
Coding Standard - ANS-Must follow team coding standards, not individual preference
Metaphor - ANS-Names w/i code suggestive to system being created. Appropriate variable names
Sustainable Pace - ANS-Tired people don't win
Pair Programming - ANS-Code produced by two individuals, working together. Pairs change frequently
TDD - ANS-No code until you have a failing unit test
Refactoring - ANS-Go back and update code to make it cleaner and simpler
Simple Design - ANS-The system should be designed as simple as possible
XP - ANS-Popular early agile method. Had practices, principles, and values. Today, scrum has only the
practices.
User Stories - ANS-Simple form of stating requirements. As a [type of user], i want to [do action]. Very
high-level, nothing about implementation
Product Backlog - ANS-Complete set of stories that describe what the entire system does.
