Across
- 3. Any more than ......... people in a team and you run the risk of slowing your team down
- 4. Every 90 days you should ......... a complete version of your software
- 5. The ......... sets the priority of each user story
- 7. The rate that you complete user stories across your entire project
- 9. At the end of an iteration your software should be ........
- 11. Your customer can remove some less important user stories when ......... them
- 12. 0.7 is your first pass ......... for a new team
- 13. At the end of an iteration you should get ......... from the customer
- 14. Velocity is a measure of your .........'s work rate
- 15. The set of features that must be present to have any working software at all is called the ......... functionality
- 16. When priotitizing, the highest priority (the most important to the customer) is set to a value of ........
- 17. You should always try be ......... with the customer
Down
- 1. Every 3 iterations you may have a complete and running and releasable ......... of your software
- 2. Ideally you apply velocity ......... you break your Version 1.0 into iterations
- 6. Velocity does not account for ......... events
- 8. At the end of an iteration your software should be ........
- 10. You should have one ......... per calendar month
- 14. You should assume ......... working days in a calendar month