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