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