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