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