Course 2 - W2 : All Quiz

Calculate the velocity range a team should use to select work for next iteration based on their past velocities (see chart below). The team uses the last 5 iterations to estimate their velocity. Use format "from-to" to specify the answer (e.g., 0-100). Table 1: The velocity of previous iterations Iteration Story points completed 1 14 2 18 3 23 4 17 5 15 6 21 7 22 8 20

15-22

Who estimates the effort to complete a product backlog item (a user story)? A. The scrum development team after clarifying the requirement. B. The scrum master with input from the scrum development team. C. The most senior people in the organization such as the engineering managers and the chief architect. D. The product owner with input from the scrum development team.

A

What is true about Agile Estimation techniques? Select two. A. Estimates are shared. B. They estimate effort and not duration. C. No planning, No estimation. It is considered non productive activity. D. The senior-most person should create estimates and get feedback from team members.

A, B

What are some of the activities you expect to see in a story mapping exercise? Select three. A. Find gaps in the story map by walking through the user experience (as expressed in the activities/tasks) aloud. B. Plan releases/journeys. C. Find variations in the paths the user can take through the system. D. Randomly write a story and its details.

A, B, C

Which of the following statements are true about "Spike" stories? Choose three. A. They can be used for knowledge acquisition. B. It is recommended that these stories have well defined acceptance criteria so that team knows what is expected at the end of exploration. C. Spike stories are timeboxed. D. Spikes are stories that allow slack time for team members to pursue their interests.

A, B, C

What are some of the ways a story map can help software development? Select all that apply. A. It builds a shared understanding among team members. B. It helps communicate user needs with the stakeholders and get feedback. C. It helps plan releases and work. D. It organizes and prioritizes the story backlog. E. It helps discover user needs.

A, B, C, E, F

What are the characteristics of good product backlog? (Select any 4) A. Prioritized B. Detailed appropriately C. Every story is assigned to developer D. Estimated E. Complete with design details F. Emergent

A, B, D, F

Which of the following estimates represents concept of relative sizing? Select three. A. Story A is bigger than Story B. Story C is smaller than Story A. B. Story A is 1 apple, Story B is 5 apples, and Story C is 10 apples C. Story A will take 1 day, Story B will take 5 Days and Story C will take 10 days D. Story A will take 1.5 ideal days, Story B will take 5 ideal days and Story C will take 3.5 Ideal Days E. Story A will take half the time Story B will take. Story C will take double the time Story A will take.

A, B, E

What are some of the valid ways to handle non-functional requirements in agile development? Select two. A. Add non-functional requirements to the definition of done for all stories. B. Delay handling non-functional requirements until the end and then work on them after development is done. C. Create specific stories that outline the non-functional needs with clear acceptance criteria.

A, C

Which of the following observations are true about Card Sorting? Select two. A. It is very useful for estimating a large number of stories. B. It is a very inaccurate method of estimation. C. This technique benefits from using relative sizing. D. Not everybody on the development team participates in this method.

A, C

What are some of the key parts of a user story? Choose four. A. The estimated development time B. The design of the back-end functionality including table and field names. C. Acceptance tests D. The story title E. The names of the developer who will implement the story and the tester who will validate it. F. Who is it for? What does the user want to do? Why does the user want to do that?

A, C, D, F

Select scenarios below where the team used the correct approach to handle special cases of team velocity. A. To forecast velocity for first iteration, 1) the team builds deeper understanding of few stories from the backlog 2) From the understood stories, they select stories they feel they can get done in one sprint. 3) The sum the estimates of the selected stories is the team's forecasted velocity. B. The team is getting more defects / support work so they are not able to finish the stories selected for the current sprint. The team estimated that it takes 30% of team capacity to handle support work. The team decided to reduce velocity by 30% and use it for future iteration. C. A new team member is going to join the team in the next iteration, so the team adjusted their velocity appropriately and selected more work to do in the iteration D. One of the team members is taking a couple days off in next iteration, but the team didn't adjust its velocity to reflect that.

A, D

A team was doing release planning and they decided that the next release will include all stories from Story 1 to Story 11 (see table 2 below). The velocity range to be used for the release planning is 15-22. The team works in a 2 week iteration. It costs about $50,000 per iteration to fund the entire team. Calculate the estimated duration for next release. Additionally, how much will this release cost? Table 2: Prioritized Product Backlog Story Title Estimate (in ideal days) Story 1 5 Story 2 5 Story 3 8 Story 4 3 Story 5 5 Story 6 5 Story 7 3 Story 8 5 Story 9 8 Story 10 8 Story 11 3 Story 12 3 Story 13 3 Story 14 5 Story 15 8 Story 16 3 Story 17 5 Story 18 5 Story 19 8 Story 20 8 A. Duration: 6-8 weeks, Cost: 150K to 200K B. Duration: 3-4 weeks, Cost: 150K to 200K C. Duration: 10-14 weeks, Cost: 500K to 700K D. Duration: 6-8 weeks, Cost: 300K to 400K

A

What issues do you see in following story? As a grocery buyer, I want to see different food items in different colors: red for meats, brown for grains, green for vegetables so that i can identify food items by type. A. This story breaks the quality of negotiable. B. The user "grocery buyer" is not a valid user. C. This story has no issues. It has all the info we need in a story. D. This story is not testable.

A

Which of the following methods can help you track a release? (select any 2) A. A cumulative flow diagram for a release B. A release burn-up chart C. An iteration burn-down chart D. A weekly status report

A, B

What of the following are the qualities of good user story as mentioned in the INVEST model? Choose three. A. Independent: Dependencies among stories should be minimized B. Natural: Stories should feel intuitive to the user C. Valuable: Stories should be valuable to user D. Editable: Stories should be editable after and during development E. Specific: Stories should define a very specific requirement F. Testable: Once the story is implemented, we should be able to test that it is done

A, C, F

What is true about estimation using Ideal Days? Select two. A. It has a potential issue of "My ideal days are not your ideal days". B. It is relative sizing technique. C. It is very fast to estimate. D. It is very natural for a new team member to understand.

A, D

Which of the following are true about story writing workshops? Select two. A. All stories created have to be at the same level. B. A story writing workshop can take anywhere between a few hours to a few days. C. The whole team (including the product owner, the scrum master, and the development team) participates in the story writing workshop.

B, C

What is true about the planning poker estimation technique? Select three. A. It is a superfast technique to estimate lots of stories in a short amount of time. B. It helps uncover misunderstandings. C. Everyone involved in development has to participate in estimation. D. It supports the concept of shared estimates.

B, C, D

The goal of a story writing workshop is to: A. Write as many foundational stories as possible. B. Write as many user stories as possible in priority order. C. Write as many user stories as possible under the themes identified. D. Write as many themes as possible.

C

What are the 3 Cs of user stories? A. Complete B. Creative C. Card D. Conversation E. Confirmation

C, D, E