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