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