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