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