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