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