3460:480 F21 HFSD Chapter 11

123456789101112131415
Across
  1. 2. When new bug fix tasks appear on your board, your customer might need to re-.... the work left in the current iteration
  2. 6. Take .... for all the code in your software, not just the bits that you wrote
  3. 8. A spike test should be around a .... in duration
  4. 10. You should be .... of your software.
  5. 11. The first step when dealing with a new chunk of unfamiliar code is to get it under ...... control
  6. 13. When fixing bugs you are fixing ....
  7. 14. Close second priority is for your code to be .... and understandable by other developers
  8. 15. You should always be .... with your customer
Down
  1. 1. At the end of a spike test you have a good idea what your team's .... .... .... is
  2. 3. Top priority is for your code to ....
  3. 4. The best spike tests include attempting to fix a .... .... of the bugs
  4. 5. Before you change anything, get all your code ....
  5. 7. Fixing bugs becomes .... or sometimes full stories on your board
  6. 9. You can account for your team's gut feeling about a collection of bugs by factoring in their .... in your bug fixing estimate
  7. 12. To help you estimate how long it will take to fix a collection of bugs in software you are unfamiliar with, use a .... ....