Study sets, textbooks, questions
Upgrade to remove ads
Terms in this set (28)
The goal during estimation is to ____ as many assumptions as possible by ___ those assumptions with the customer.
eliminate / clarifying
According to the authors, what is the perfect thing for writing down requirements?
When does the process of gathering requirements happen?
at the beginning of each iteration
"...always do only what your user story says, ..."
and not an ounce more
Which two of the following are mentioned in the textbook in conjunction with "blueskying?"
Contribute without criticism, think big
What are three ways the authors list to "get inside your customer's head"?
"Great software development delivers..."
What the customer wants
In the role playing described in the textbook, the software developer pretends to be...
What is the main technique for bridging the gap between what the customer wants (in his or her head) and what s/he receives in delivered software?
"Try to keep your observation..."
as unobtrusive as possible
A great requirement is written from whose perspective?
Which of these is more difficult: estimating each user story, or adding up all the user story estimates to get a total estimate for the project?
estimating each user story
When it comes to requirements,...
no assumption is a good assumption
Which of the following are things that describe a good user story?
is written using language that the customer understand, describes one thing that the software needs to do for the customer, is written by the customer (no matter who scribbles on a notecard), is short
Why is it a red flag when you learn that a customer doesn't understand one of your requirements?
The customer couldn't possibly have asked for a requirement she or he doesn't understand.
Who should understand what a user story means?
both you and your customer
What is the most important activity for coming up with estimates you believe in?
getting rid of assumptions
"Two particularly useful techniques that help you understand the customer are _____ and _____."
observation, role playing
This is the X rule: Any user story that has "X" in its title or in its description can probably be split into two or more smaller user stories.
What is "X" in the description above?
If one approach to gather good requirements doesn't work, ...
"Everyone should get an equal say to ensure you get the most out of each brainstorming session."
Your project estimate is...
the sum of the estimates for your user stories
Adding appropriate technical terms to user stores make them more useful.
After playing a round of planning poker, the goal is to get rid of as many assumptions as possible, and to ____ all of the points on each user story's spread of estimates.
The larger the difference between the estimates, ... [pick two]
the more assumptions you need to root out, the less confident you are in the estimate
During the gathering of requirements, if you are unclear about anything, then it's time to...
"As a rule of thumb, estimates that are longer than _____ days are much less likely to be accurate..."
A good user story includes about how many lines or so of description?
Sets found in the same folder
Other sets by this creator
Other Quizlet sets
Ob module 5 High risk obstetrics
APES unit 5
S.S FINAL STUDY GUIDE 7 TH GRADE
Oncology: Chemotherapeutic Agents