SWA Software Architecture - XP - Agile Programming MCQs
SWA Software Architecture - XP - Agile Programming MCQs
The following SWA Software Architecture - XP - Agile Programming MCQs have been compiled by our experts through research, in order to test your knowledge of the subject of SWA Software Architecture - XP - Agile Programming. We encourage you to answer these multiple-choice questions to assess your proficiency.
Please continue by scrolling down.
1: Meetings used to create a release plan - which will lay out the overall project.
A. Simplicity
B. Release Planning
C. Pair Programming
D. Optimization Last
2: Stand up meetings show who will be valuable and needed.
A. Stand Up Meetings
B. Metaphor
C. Move People Around
D. Pair Programming
3: No more than 40 hours to stop burnouts.
A. CRC Cards
B. 40 Hour Work Week
C. Stand Up Meetings
D. Continuous Integration
4: Meetings at the beginning of each iteration to produce a plan of programming tasks.
A. Refactoring
B. Iteration Planning
C. On-Site Customer
D. Spike Solution
5: Formatted code standards.
A. Continuous Integration
B. Coding Standards
C. Refactoring
D. User Stories
6: Quick program.
A. Iteration Planning
B. CRC Cards
C. Spike Solution
D. Refactoring
7: Always do the simplest design that could possibly work.
A. Refactoring
B. Acceptance Tests
C. CRC Cards
D. Simplicity
8: Allows consumers to try a system earlier and give early feedback.
A. CRC Cards
B. On-Site Customer
C. Iteration Planning
D. Move People Around
9: Keeps a team using a similar naming convention for things.
A. Metaphor
B. Coding Standards
C. Iteration Planning
D. CRC Cards
10: What function classes should include.
A. On-Site Customer
B. CRC Cards
C. Coding Standards
D. Release Planning
11: Do not optimize until the very end.
A. Optimization Last
B. Iteration Planning
C. Stand Up Meetings
D. Metaphor
12: Written by the customers as things that the system needs to do for them.
A. User Stories
B. Iteration Planning
C. Stand Up Meetings
D. Pair Programming
13: When we remove redundant or obsolete designs and replace them with a new.
A. Refactoring
B. CRC Cards
C. Continuous Integration
D. Coding Standards
14: Create a test and then create a function.
A. Release Planning
B. Continuous Integration
C. Pair Programming
D. Unit Test First
15: Developers should be integrated and releasing code into the code repository every few hours.
A. User Stories
B. Unit Test First
C. Continuous Integration
D. Metaphor
16: Functionality Tests.
A. Unit Test First
B. Acceptance Tests
C. Simplicity
D. Refactoring
17: 2 Eyes + 2 Minds = AWESOME!
A. Pair Programming
B. Continuous Integration
C. User Stories
D. Iteration Planning
18: Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.
A. Coding Standards
B. Refactoring
C. Move People Around
D. Release Planning
List of SWA Software Architect...
Available in:
SWA Software Architecture - XP - Agile Programming MCQs
