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