SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
Search
Test your basic knowledge |
SWA Software Architecture - XP - Agile Programming
Start Test
Study First
Subjects
:
certifications
,
swa
,
it-skills
Instructions:
Answer 18 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.
Unit Test First
CRC Cards
Move People Around
Metaphor
2. No more than 40 hours to stop burnouts.
Unit Test First
40 Hour Work Week
Spike Solution
Metaphor
3. Allows consumers to try a system earlier and give early feedback.
Move People Around
Continuous Integration
Optimization Last
On-Site Customer
4. Meetings used to create a release plan - which will lay out the overall project.
CRC Cards
Iteration Planning
Optimization Last
Release Planning
5. Always do the simplest design that could possibly work.
On-Site Customer
Move People Around
Simplicity
Pair Programming
6. Are what function classes should include.
Continuous Integration
Move People Around
Simplicity
CRC Cards
7. Quick program.
Refactoring
Spike Solution
Release Planning
Optimization Last
8. Developers should be integrated and releasing code into the code repository every few hours.
Continuous Integration
CRC Cards
Iteration Planning
Release Planning
9. Keeps a team using a similar naming convention for things.
Spike Solution
Stand Up Meetings
Metaphor
Pair Programming
10. Meetings at the beginning of each iteration to produce a plan of programming tasks.
Metaphor
Release Planning
Refactoring
Iteration Planning
11. Create a test and then create a function.
Acceptance Tests
Metaphor
Unit Test First
Release Planning
12. Do not optimize until the very end.
Coding Standards
Optimization Last
Pair Programming
Acceptance Tests
13. Functionality Tests.
Unit Test First
Simplicity
Acceptance Tests
Move People Around
14. Stand up meetings show who will be valuable and needed.
Stand Up Meetings
Optimization Last
Unit Test First
Pair Programming
15. Formatted code standards.
Iteration Planning
Continuous Integration
Spike Solution
Coding Standards
16. Written by the customers as things that the system needs to do for them.
Simplicity
User Stories
Optimization Last
Acceptance Tests
17. When we remove redundant or obsolete designs and replace them with a new.
Refactoring
User Stories
On-Site Customer
Acceptance Tests
18. 2 Eyes + 2 Minds = AWESOME!
Continuous Integration
Pair Programming
Coding Standards
Spike Solution