CS4500

7. Which two of the following best describe the textbook's ideas about how long an iteration should be?

a. Iterate often enough to catch yourself when you're deviating from the goal, don't iterate so often that you're spending all your time preparing for the end of an iteration

20. "The secret to great software development is..."

a. Iteration

11. Usually (during a software development project), cash is a BLANK.

a. Limitation

1. The authors plan to teach us how to avoid being a software development casualty by delivering software that is...[mark three]

a. Needed, on budget, on time

2. If a user story has to get bumped from the current iteration, where does it go on the big board?

a. Next

2. According to the textbook, your brain craves...

a. Novelty

3. Make sure that your software builds from almost day BLANK.

a. One

8. If you spot a redundancy in this textbook,...

a. Pay attention; the redundancy is intentional and important

7. To what does your brain pay more attention?

a. People

16. According to the textbook, "Adding more developers or getting everyone to work longer hours will often blow your budget and BLANK results in the performance gains you might expect."

a. Rarely if ever

10. The authors give advice on how to read their textbook. They tell you to...

a. Read the book from the beginning

14. With iteration, every time you make significant progress in your software development, you BLANK1 and BLANK2.

a. Refine what you're working on, check with the customer

1. The authors let us know that we should not expect all the examples to be...

a. Robust or complete

5. The slow, tedious way to get your brain to treat software development like it was a hungry tiger is about...

a. Sheer repetition

12. What it customer needs is also known as the "BLANK".

a. Software requirements

15. Why do the authors suggest that you talk about software development out loud?

a. Speaking activates a different part of your brain.

6. What is the best tool for ensuring that your software meets the needs of your customer?

a. The feedback that comes out of each iteration

18. 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?

a. To deliver some of the features working perfectly

19. Really getting the requirements down tight, and not letting the customers change their minds downstream, is a recipe for disaster.

a. True

8. If you haven't been checking in with your customer, the gap between their ideal software and what you're building can grow very large without you knowing it.

a. True

14. "Slow down. The more you BLANK, the less you have to memorize."

a. Understand

12. According to the textbook, to which of the following is your brain tuned?

a. Visuals

13. The authors even give advice on what to consume in order to increase cognitive function. What is it?

a. Water

7. "Use ... BLANK to plan and monitor your current iteration's work."

a. a big board on your wall

13. "... the final decision on priorities is BLANK the customer's to make."

a. always

25. 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?

a. and

5. "...always do only what your user story says,..."

a. and not an ounce more

10. "Try to keep your observation..."

a. as unobtrusive as possible

9. When during your project should you apply velocity?

a. at the beginning

14. When does the process of gathering requirements happen?

a. at the beginning of each iteration

3. Who should understand what a user story means?

a. both you and your customer

17. "You really BLANK factor in complete surprises."

a. can't

16. After playing a round of planning poker, the goal is to get rid of as many assumptions as possible, and to BLANK all of the points on each user story's spread of estimates.

a. converge

12. "When user stories are being prioritized, you need to stay..."

a. customer-focused

2. What units are used on both axes of a burn down graph?

a. days

22. 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

a. days of work required to get the work done

12. The goal during estimation is to BLANK as many assumptions as possible by BLANK those assumptions with the customer.

a. eliminate/clarifying

11. 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?

a. estimating each user story

6. If a user story gets a priority of 50, then you automatically can leave it out.

a. false

28. "As a rule of thumb, estimates that are longer than BLANK days are much less likely to be accurate..."

a. fifteen

13. What is the most important activity for coming up with estimates you believe in?

a. getting rid of assumptions

16. "... every person you add to your team makes the job of keeping everyone focused and knowing what they are doing BLANK."

a. harder

27. During the gathering of requirements, if you are unclear about anything, then it's time to...

a. have another discussion with your customer

24. When determining priorities among the user stories, don't get caught up on BLANK.

a. how long those user stories will take to develop

18. According to the authors, what is the perfect thing for writing down requirements?

a. index cards

10. "If you can get by without a feature, then..."

a. it isn't really baseline functionality

4. "If a feature isn't essential, ..."

a. it's probably not a 10

22. When it comes to requirements, ...

a. no assumption is a good assumption

11. According to the textbook, is there a maximum team size that you should never go over?

a. not really

8. What are the three ways the authors list to "get inside your customer's head"?

a. observation, brainstorming, user stories

3. "You should promise and deliver rather than BLANK and fail."

a. overpromise

18. "Any user stories that don't make it into Milestone 1.0 are not ignored, just..."

a. postponed until Milestone 2, or 3...

3. What color does the textbook suggest for unplanned tasks that go up on the Big Board?

a. red

21. "If the features don't fit, BLANK."

a. reprioritize

17. "Two particularly useful techniques that help you understand the customer are BLANK and BLANK."

a. role playing, observation

8. A daily meeting that is designed to be quick and keep everyone in the loop is called a BLANK meeting.

a. standup

7. In order to "get to the real work", you break each user story into

a. tasks

1. "Don't let the customers talk you into longer development cycles BLANK"

a. than you're comfortable with

15. A great requirement is written from whose perspective?

a. the customer

5. Ultimately, whose choice is it about what is in and what's left out of a project?

a. the customer

6. Who sets the priorities, including adding unexpected new tasks?

a. the customer

23. Why is it a red flag when you learn that a customer doesn't understand one of your requirements?

a. the customer couldn't possibly have asked for a requirement she or he doesn't understand

24. The larger the difference between estimates, .... [pick two]

a. the less confident you are in the estimate, the more assumptions you need to root out

9. In the role playing described in the textbook, the software developer pretends to be...

a. the software

21. Your project estimate is...

a. the sum of the estimates of your user stories

29. Which two of the following are mentioned in the textbook in conjunction with "blueskying"?

a. think big, contribute without criticism

4. a good user story includes about how many lines or so of description?

a. three

1. The three parts of a task are...

a. title, estimate, rough description

2. "Everyone should get an equal say to ensure you get the most out of each brainstorming session."

a. true

23. Keep iterations short.

a. true

4. There are no hard and fast rules about who to give a task to.

a. true

5. Velocity is about how fast you and your team can comfortably work, for real.

a. true

7. If one approach to gather good requirements doesn't work,...

a. try another

20. 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?

a. user stories

26. "Great software development delivers..."

a. what the customer wants

8. "Milestone 1.0 is about delivering BLANK ..."

a. what's needed

25. "'Version' is a label and doesn't mean anything more, whereas 'Milestone' means you deliver significant functionality and..."

a. you get paid

14. What is "Milestone 1.0"?

a. your first major release of the software to the customer

5. If you start with the days of work left and subtract the days left before your deadline, which of the results below makes you the happiest?

a. -2

15. If you don't know how fast your team performs, start with a velocity of BLANK.

a. 0.7

19. 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 BLANK days of real work.

a. 14 (but the book says 15 on page 89)

2. How many workdays do the authors recommend as a rule of thumb of the time between iterations?

a. 20

20. 30-day iterations are basically 30 calendar days which you can assume turn into about BLANK WORKING days of productive development.

a. 20 (but the book says 15 on page 89)

4. The textbook says that you can up to XX% improvement in recall and transfer studies when images are used in learning.

a. 89

10. "...checking back with the customer is BLANK worth it."

a. Always

3. The authors advise you to read the textbook when?

a. Before going to bed

17. "Every great piece of software starts with a customer's..."

a. Big idea

9. If your customer isn't happy, you...

a. Built the wrong software

9. When reading this textbook, the marginal notes are vital. Some are meant to be funny, some are insightful. You can't tell the difference without reading them, so READ THEM ALL. This question is about of the (perhaps not so amusing) notes. The note says, "[Note from marketing: this book is for anyone with a BLANK.]" What is in that blank?

a. Credit card

6. There are different kinds of exercises in this book. Some of them are called "Brain Power exercises." Brain Power exercise...

a. Don't have answers listed in the book

11. "We know that your ability to remember something is largely dependent on its BLANK content."

a. Emotional

19. The key to capturing good requirements is to focus on a small subset of the most important stakeholders.

a. False

24. If you are a team of one, you do not need to iterate.

a. False

4. Good iteration is like a rare checkup for your software.

a. False

6. Adding appropriate technical terms to user stories make them more useful.

a. False

13. "If you're not sure what the customer wants, or even if you think you're sure, always..."

a. Go back and ask

21. Another name for the "Big Bang" in software development is BLANK because the customer sees you at the beginning of the project, and then you disappear until the software is delivered at the end.

a. Going dark

15. "Software development is NOT [or at least should not be]..."

a. Guesswork

22. Besides their big idea, customers probably have two basic concerns:

a. How much will it cost, how long will it take

23. The phrase "Big Bang" means that you work a lot, and then, BANG, something BLANK comes out of the work all at once.

a. Huge and complex