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