Software Development C3

2. Ideally you apply velocity ......... you break your Version 1.0 into iterations.
4. Every 90 days you should ......... a complete version of your software.
7. At the end of an iteration your software should be .........
8. 0.7 is your first pass ......... for a new team.
12. Every 3 iterations you should have a complete and running and releasable ......... of your software.
13. You should always try be ......... with the customer.
14. You should have one ......... per calendar month.
15. If you add more people to a project, it may …….. the time it takes.
17. At the end of an iteration your software should be .........

1. Velocity is a measure of your .........'s work rate.
2. The set of features that must be present to have any working software at all is called the ......... functionality.
3. When prioritizing, the highest priority (the most important to the customer) is set to a value of .........
5. Your customer can remove some less important user stories when ......... them.
6. The rate that you complete user stories across your entire project.
9. At the end of an iteration you should get ......... from the customer.
10. Velocity does not account for ......... events.
11. The ......... sets the priority of each user story.
16. You should assume ......... working days in a calendar month.