Software Development Cross Solution - Index of - Free

7
H
2
B
3
A
1
Q
gathering requirements
Requirements and Estimation Cross
SolutionUntitled Puzzle
L U E S K Y B R A I N S T O R M I N G
E
S S U M P T I O N S
T
I T
4
5
E C
H N I C A L R
6
8
O W L O N G U O C
12
P
9
N C
11
M F
10
U S T O M E R L C
Header Info 1
Header Info 2
etc...
T E O N
L A N N I N G P O K E R T
13
O
P N S
R F M H L F E
K T
14
18
C
I T L E O
15
B S
16
E R V A T I O N
E R P E Y D S
E A
17
R E I E U
O N V E R G E N C E N N S
D A G T
Across
Down
2. When you and the customer are really letting your ideas run 1. When you just have no idea how to estimate a user story, use
wild you are ......... [BLUESKYBRAINSTORMING]
a card with this on it. [QUESTIONMARK]
3. When coming up with estimates, you are trying to get rid of as 5. User stories are written from the perspective of the .........
many ......... as possible. [ASSUMPTIONS]
[CUSTOMER]
4. None of this language is allowed in a user story.
6. When you and the customer act out a particular user story,
[TECHNICAL]
you are ......... [ROLEPLAYING]
7. If a requirement is the what, an estimate is the ......... 8. When everyone agrees on an estimate, it is called a .........
[HOWLONG]
[CONSENSUS]
9. Requirements are oriented towards the ......... [CUSTOMER] 10. An estimate is good when eveyone on your team is
12. The best way to get honest estimates and highlight
feeling ......... [CONFIDENT]
assumptions. [PLANNINGPOKER]
11. The maximum number of days that you a good are estimate here 4 should 67
14. A User Story is made up of a ......... and a description. Download at WoweBook.Com
be for one user story. [FIFTEEN]
[TITLE]
13. A great user story is about ......... lines long. [THREE]
D