SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
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. Quick program.
Simplicity
Spike Solution
Unit Test First
Acceptance Tests
2. Create a test and then create a function.
Unit Test First
Release Planning
CRC Cards
Metaphor
3. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.
Move People Around
Iteration Planning
User Stories
CRC Cards
4. 2 Eyes + 2 Minds = AWESOME!
Simplicity
Unit Test First
Iteration Planning
Pair Programming
5. Formatted code standards.
Coding Standards
Simplicity
Refactoring
Metaphor
6. Stand up meetings show who will be valuable and needed.
Spike Solution
Optimization Last
CRC Cards
Stand Up Meetings
7. When we remove redundant or obsolete designs and replace them with a new.
Move People Around
Refactoring
Iteration Planning
Acceptance Tests
8. Are what function classes should include.
CRC Cards
Stand Up Meetings
Refactoring
Optimization Last
9. Functionality Tests.
Acceptance Tests
Refactoring
Pair Programming
CRC Cards
10. Always do the simplest design that could possibly work.
Simplicity
Acceptance Tests
On-Site Customer
40 Hour Work Week
11. Do not optimize until the very end.
Move People Around
Stand Up Meetings
Optimization Last
Unit Test First
12. Meetings at the beginning of each iteration to produce a plan of programming tasks.
Metaphor
Iteration Planning
Simplicity
Move People Around
13. Developers should be integrated and releasing code into the code repository every few hours.
Continuous Integration
Spike Solution
Iteration Planning
Pair Programming
14. Keeps a team using a similar naming convention for things.
Metaphor
Continuous Integration
Simplicity
User Stories
15. Meetings used to create a release plan - which will lay out the overall project.
Spike Solution
Continuous Integration
Release Planning
Acceptance Tests
16. Written by the customers as things that the system needs to do for them.
Coding Standards
User Stories
Acceptance Tests
Move People Around
17. No more than 40 hours to stop burnouts.
Release Planning
Acceptance Tests
Move People Around
40 Hour Work Week
18. Allows consumers to try a system earlier and give early feedback.
Move People Around
On-Site Customer
Spike Solution
User Stories