CS 3540 HFSD Chapter 3

4. At the end of an iteration your software should be ........
6. You should always try be ......... with the customer
8. Velocity does not account for ......... events
12. At the end of an iteration you should get ......... from the customer
14. Ideally you apply velocity ......... you break your Version 1.0 into iterations
15. Every 3 iterations you may have a complete and running and releasable ......... of your software
17. Your customer can remove some less important user stories when ......... them
18. Any more than ......... people in a team and you run the risk of slowing your team down

1. You should assume ......... working days in a calendar month
2. The ......... sets the priority of each user story
3. At the end of an iteration your software should be ........
5. When priotitizing, the highest priority (the most important to the customer) is set to a value of ........
7. The rate that you complete user stories across your entire project
9. You should have one ......... per calendar month
10. The set of features that must be present to have any working software at all is called the ......... functionality
11. 0.7 is your first pass ......... for a new team
13. Velocity is a measure of your .........'s work rate
16. Every 90 days you should ......... a complete version of your software