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