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