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