HFSD Chapter 2

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