Software Development C5

1234567891011121314
Across
  1. 4. When you improve a design to make it more flexible and easier to maintain you are ......... the design.
  2. 5. You should always be ......... with your customer.
  3. 8. Striving for a ......... design can mean that you never actually cut any code.
  4. 10. When a task is finished it goes in the ......... column.
  5. 11. When a class does one job and it's the only class that does that job it is said to obey the ......... responsibility principle.
  6. 12. An unplanned task is going to happen in your current iteration once you have added it to your .........
Down
  1. 1. When all the tasks in a user story are finished, the user story is transferred to the ......... bin
  2. 2. ......... is the only constant in software development.
  3. 3. When a design helps you meet your deadlines, it is said to be a ..... ..... design.
  4. 6. If a user story is not quite finished at the end of an iteration, it is moved to the ......... bin on your project board.
  5. 7. Unplanned tasks are treated the ......... as unplanned tasks once they are on your board.
  6. 9. A good enough design helps you .........
  7. 11. Great developers .........
  8. 13. Your burn down rate should show ......... the work on your board, including any new unplanned tasks.
  9. 14. If you find you are cutting and pasting large blocks of your design and code then there's a good chance that you're breaking the ......... principle.