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