Software Development Cross Solution - Index of - Free

crossword solution
10
F
15
H
5
P
BugSquashingCross Solution
1
R
4
P
E B
2
7
R N C
U G F I X R
3
S A
R E F A C T O R I N G
A T E
O D R
6
8
S
Across
Down
2. At the end of a spike test you have a good idea what your 1. Take .... for all the code in your software, not just the bits
team's .... .... .... is [BUGFIXRATE]
that you wrote [RESPONSIBILITY]
4. When you apply your refactoring experience to avoid 3. The best spike tests include attempting to fix a .... .... of the
problems up front, that is called .... [PREFACTORING] bugs. [RANDOMSAMPLE]
9. When new bug fix tasks appear on your board, your 5. You should be .... of your software. [PROUD]
customer might need to re-.... the work left in the current 6. When you change code to make it work or just to tidy it up,
iteration. [PRIORITIZE]
this is called .... [REFACTORING]
10. When fixing bugs you are fixing .... [FUNCTIONALITY] 7. You can account for your team's gut feeling about a
11. Fixing bugs becomes .... or sometimes full stories on your collection of bugs by factoring in their .... in your big fixing
board. [TASKS]
estimate. [CONFIDENCE]
12. A spike test should be around a .... in duration. [WEEK] 8. To help you estimate how long it will take to fix a collection
14. Close second priority is for your code to be .... and of bugs in software you are unfamiliar with, use a .... ....
understandable by other developers [READABLE]
[SPIKETEST]
15. You should always be .... with your customer [HONEST]
416 Chapter 11
16. The first step when dealing with a new chunk of unfamiliar
13. Top priority is for your code to .... [WORK]
code is to get it under source code .... [CONTROL] Download at WoweBook.Com
17. Before you change anything, get all your code ....
9
P
R I O R I T I Z E
O S O P M F
U N C T I O N A L I T Y S A
D B F K T
11
13
W
I I W
12
A S K S C
E E K M T
L D T P O
I E R
14
E A D A B L E R
O N E S T N S E I
16
R Y C
K E B
17
O N T R O L N
U I L D I N G