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