Software Development C2

123456789101112131415161718
Across
  1. 3. You can use the ……… rule for breaking up large user stories.
  2. 5. The goal of estimation is .........
  3. 7. When you and the customer are really letting your ideas run wild you are ..... .....
  4. 12. The maximum number of days that a good estimate should be for one user story.
  5. 13. If a requirement is the what, an estimate is the .... ....
  6. 14. User stories are written from the perspective of the ………
  7. 15. A great user story is about ……… lines long.
  8. 16. When you and the customer act out a particular user story, you are .... ....
  9. 17. ……… is a great way of getting first hand evidence of exactly how your customer works at the moment.
  10. 18. A User Story is made up of a ......... and a description.
Down
  1. 1. The best way to get honest estimates and highlight assumptions.
  2. 2. When you just have no idea how to estimate a user story, use a card with this on it.
  3. 4. When coming up with estimates, you are trying to get rid of as many ……… as possible.
  4. 6. After a round of planning poker, you plot all of the estimates on a ………
  5. 8. An estimate is good when everyone on your team is feeling .........
  6. 9. What an assumption becomes if it is not eliminated.
  7. 10. None of this language is allowed in a user story.
  8. 11. When everyone agrees on an estimate, it is called a .........