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