Week 10 - 11 Sprint Release Planning

Criteria that a product must meet for it to be considered finished

• Definition of done

• Sprint Release Planning

• User Story

• Sprint Goal

• Product backlog

A prioritized list of all desired work on the project.

• Definition of done

• Sprint Release Planning

• User Story

• Sprint Goal

• Product backlog

A meeting held at the end of a sprint for the team to reflect on their processes and make improvements

• Story points

• Velocity

• Sprint retrospective

• User's story

• Sprint Backlog

A brief description of a feature told from the user's perspective

• Story points

• Velocity

• Sprint retrospective

• User's story

• Sprint Backlog

As a meal planner, I want to see nutrition information for a given amount of a specific food, so that I prepare a healthy meal. What are suitable acceptance tests? Choose two that are correct.

• See nutrition information for a given amount of a given food.

• Correct nutrition information is shown for a given amount of a given food.

• Enter the name of an item of food not in the system and confirm an error message is displayed.

• Enter 250 g of baked Pacific salmon and confirm the correct nutrition information is displayed.

Horatio has been keeping track of his development team's output by measuring the number of story points per sprint. Halfway through the project, the client requests that Horatio start to measure the team's productivity by using hours per sprint. Horatio explains to his client that this is not a good idea, because it breaks which desirable property of a metric?

• It is specific to the project.

• It is not consistent as a unit.

• It is not simple.

• It is not objective.

What is a key difference between use cases and user stories?

• A use case description defines the interactive steps of a task, while a user story generally does not.

• A use case description defines a benefit, while a user story generally does not.

• A use case description defines an actor, while a user story generally does not.

• A use case description defines a goal, while a user story generally does not.

Consider the following user story: As a traveler, I want the journal application to have a good user interface, so that I enjoy using it regularly. What is poor about this requirement? Choose two that are correct.

• It is not negotiable.

• It is an epic.

• It is not testable.

• It is too small.

A development team estimates their velocity to be 15 story points per sprint, based on data from a similar project with the same developers, type of software product, and sprint duration. For the current project, after the first few sprints, their actual velocity was calculated to be 12 story points per sprint. What should be done for the next sprint?

• Increase the sprint duration by 25 per cent.

• Inflate all the story point estimates by 25 per cent.

• Continue to use 15 story points per sprint as their estimated velocity.

• Use 12 story points per sprint as their estimated velocity.

Over time, sprint velocities tend to become more and more stable. This is likely because (choose two that apply):

• Development teams have consulted with other workers.

• Development teams learn how to count story points better.

• At the beginning of a project, the development team is still learning to work together, so velocities will change.

• If the development team is following Agile principles, then a sustainable development pace should develop.