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