Test your basic knowledge |

SWA Software Architecture - XP - Agile Programming

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 at the beginning of each iteration to produce a plan of programming tasks.






2. Written by the customers as things that the system needs to do for them.






3. Developers should be integrated and releasing code into the code repository every few hours.






4. Functionality Tests.






5. When we remove redundant or obsolete designs and replace them with a new.






6. No more than 40 hours to stop burnouts.






7. Keeps a team using a similar naming convention for things.






8. Create a test and then create a function.






9. Allows consumers to try a system earlier and give early feedback.






10. Meetings used to create a release plan - which will lay out the overall project.






11. 2 Eyes + 2 Minds = AWESOME!






12. Do not optimize until the very end.






13. Stand up meetings show who will be valuable and needed.






14. Formatted code standards.






15. Are what function classes should include.






16. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






17. Always do the simplest design that could possibly work.






18. Quick program.