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