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