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