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