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