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