Software Profession 4500 FINAL
If a user story has to get bumped from the current iteration, where does it go on the big board?
next
When it comes to requirements...
no assumption is a good assumption
If a programmer X is assigned to work on two tasks, but she's only actually working on one, how many tasks get put into the In Progress area on the big board?
one
Your task estimates should ideally be between ___________ days long.
one half and five
"You should promise and deliver rather than ______ and fail."
overpromise
"Any user stories that don't make it into Milestone 1.0 are not ignored, just..."
postponed until milestone 2, or 3
According to the textbook, "Adding more developers or getting everyone to work longer hours will often blow your budget and _____ results in the performance gains you might expect.
rarely if ever
What color does the textbook suggest for unplanned tasks that go up on the Big Board?
red
"If the features don't fit, _____."
reprioritize
"Two particularly useful techniques that help you understand the customer are _____ and _____."
role playing observation
What the customer needs is also known at the " ."
software requirements
A daily meeting that is designed to be quick and keep everyone in the loop is called a _________ meeting.
standup
Which kind of estimate is better to rely on, user story estimates or task estimates?
task estimates
"Don't let the customers talk you into longer development cycles _____"
than your comfortable with
A great requirement is written from whose perspective?
the customer
Who sets the priorities, including adding unexpected new tasks?
the customer
Ultimately, whose choice is it about what is in and what's left out of a project?
the customoer
What is the best tool for ensuring that your software meets the needs of your customer?
the feedback that comes out of each iteration
In the role playing described in the textbook, the software developer pretends to be...
the software
Your project estimate is...
the sum of the estimates for your user stories.
What goes into the left column on the big board?
the user stories for this iteration
Which is better: to deliver some of the features working perfectly; or to deliver all of the features, some of which might be less than perfect.
to deliver some of the features working perfectly
Keep iterations short.
true
Sometimes working on two tasks at the same time is the best option.
true
There are no hard and fast rules about who to give a task to.
true
If one approach to gather good requirements doesn't work..
try another.
What is the main technique for briding the gap between what the customer wants (in his or her head) and what s/he receives in delivered software?
user stories
What are three ways the authors list to "get inside your customer's head"?
user stories brain storming the estimation game
"Great software development delivers..."
what the customer wants
When do tasks move from Complete to Completed on the Big Board?
when all of the tasks in a user story are done
"Successful software development is about knowing ____ you are."
where
"'Version' is a label and doesn't mean anything more, whereas 'Milestone' means you deliver significant functionality and..."
you get paid
What is "Milestone 1.0?"
your first major release of the software to the customer
If you are a team of one, you do not need to iterate.
False
"...the final decision on priorities is _____ the customer's to make."
always
"Try to keep your observation..."
as unobtrusive as possible
When during your project should you apply velocity?
at the beginning
When does the process of gathering requirements happen?
at the beginning of each iteration
"Every great piece of software starts with a customer's..."
big idea
Who should understand what a user story means?
both you and the customer
Task estimates add _____ to user story estimates.
confidence
Which two of the following are mentioned in the textbook in conjunction with "blueskying?"
contribute without criticism think big.
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.
converge
"When user stories are being prioritized, you need to stay..."
customer-focused
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?
"and"
What units are used on both axes of a burn down graph?
days
Assuming that multiple days of work are required for your project, and that your velocity is within the range specified in the book, then which of these will always be at least as large as the other two? : days of work estimated days required to get the work done (after using velocity) velocity
days required to get the work done
Which two of the following best describe the textbook's ideas about how long an iteration should be?
don't iterate so often that you're spending all your time preparing for the end of an iteration. iterate often enough to catch yourself when you're deviating from the goal always make an iteration exactly 20 workings days
The goal during estimation is to ____ as many assumptions as possible by ___ those assumptions with the customer
eliminate/ clarifying
end of quiz 1
end of quiz 1
end of quiz 2
end of quiz 2
end of quiz 3
end of quiz 3
end of quiz 4
end of quiz 4
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 should you update new estimates and the time left on the burn-down chart?
every time we do any work or review an estimate
If you know who'll be working on a task in the near future, put that task into the In Progress section of the Big Board.
fale
Adding appropriate technical terms to user stores make them more useful
false
If a user story gets a priority of 50, then you automatically can leave it out.
false
The key to capturing good requirements is to focus on a small subset of the most important stakeholders.
false
Try to double-up on tasks that have large estimates.
false
Your team's velocity does not have to be recalculated for each iteration.
false
When in the day should you schedule your daily standup meetings?
first thing in the morning
A daily standup meeting should last between _____ minutes.
five and fiteen
"If you're not sure what the customer wants, or even if you think you're sure, always..."
go back and ask
"Software development is NOT [or at least should not be]..."
guesswork
"...every person you add to your team makes the job of keeping everyone focused and knowing what they are doing _____."
harder
During the gathering of requirements, if you are unclear about anything, then it's time to...
have another discussion with your customer
When determining priorities among the user stories, don't get caught up on _____.
how long those user stories will take to develop
The phrase "Big Bang" means that you work a lot, and than, BANG, something _____ comes out of the work all at once.
huge and complex
According to the authors, what is the perfect thing for writing down requirements?
index cards
"The secret to great software development is...
iteration
"If a feature isn't essential, ..."
its probably not a 10
Usually (during a software development project), cash is a _________.
limitation
If you start with the days of work left and subtract the days left before your deadline, which of the results below make you the happiest?
-2
Make sure that your software builds from almost day _______.
1
With iteration, every time you make significant progress in your software development, you ______ and _____. [Mark two of the following...]
1) Check with the customer. 2)Refine what you're working on.
If you start with 30 days on a calendar, then take away weekends and holidays, then apply a velocity of 0.7, then you get ___ days of real work.
14
How many workdays do the authors recommend as a rule of thumb of the time between iterations.
20
A good user story includes about how any lines or so of description?
3
Another name for the "Big Bang" in software development is _____, because the customer sees you at the beginning of the project, and then you disappear until the software is delivered at the end.
Going Dark
"If you can get by without a feature, then..."
It isn't really baseline functionality
If you haven't been checking in with your customer, the gap between their ideal software and what you're building to grow very large without you knowing it.
True
Really getting the requirements down tight, and not letting the customers change their minds downstream, is a recipe for disaster.
True
"Use ... _____ to plan and monitor your current iteration's work.
a big board on your wall
What kind of "big board" does the book recommend?
a real bulletin boar or white board hanging somewhere
