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