3460:480 S20 HFSD Chapter 3

3. Every 90 days you should ......... a complete version of your software
5. Every 3 iterations you may have a complete and running and releasable ......... of your software
8. At the end of an iteration your software should be ........
11. At the end of an iteration you should get ......... from the customer
13. When priotitizing, the highest priority (the most important to the customer) is set to a value of ........
14. Your customer can remove some less important user stories when ......... them
15. The ......... sets the priority of each user story
16. You should assume ......... working days in a calendar month
18. The set of features that must be present to have any working software at all is called the ......... functionality

1. Ideally you apply velocity ......... you break your Version 1.0 into iterations
2. Any more than ......... people in a team and you run the risk of slowing your team down
4. You should always try be ......... with the customer
6. You should have one ......... per calendar month
7. At the end of an iteration your software should be ........
9. The rate that you complete user stories across your entire project
10. 0.7 is your first pass ......... for a new team
12. Velocity does not account for ......... events
17. Velocity is a measure of your .........'s work rate