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