Overview of The Scrum Development Process

Scrum Master

Addresses team performance issues Helps team members understand how Scrum works

Sprint closure

Any completed functional part of the product are created and delivered to the customer

Product owner

Communicates changes to the product backlog to the relevant people Orders the requirements in the product backlog to secure maximum value for the customer

As product owner, you've established the product requirements for a project that involves creating a new web site. Next you need to create a product backlog. Which guidelines should you follow when creating the product backlog?

Consider merging related items that are unlikely to take more than a few days to develop Provide the most detail for the items listed first in the backlog- such as designing the site's home page Change the content and order of items in the backlog as requirements evolve throughout the project

Number of tests

Counts how many times the product is checked in terms of its accuracy

Game

Create the sprint goal and sprint Present functioning deliverables to stakeholders for inspection

Which are some of the guidelines for effective stakeholder communication in the scrum methodology?

Demonstrate the results of each sprint to customers keep documentation that tracks work progress updated Favor face-to-face over video communication

Development team

Determines how to build each product feature so it meets customer requirements

Daily standup meeting

Enables development team members to update each other on their progress

Scrum of Scrums

Enables multiple teams to coordinate their efforts

Unit testing

Engineers analyze a product while it's in development to check for defects

Pre-game

Establish the project's goal Develop the product backlog Develop a high-level design

Sprint review meeting

Gives stakeholders a chance to assess the results of a sprint and give feedback

Burndown chart

Helps team members determine how much work effort they need to complete to finish on time Plots the work to which a team has committed against the days of the production time that are left Show you at a glance how much work remains to be done in a sprint or project

Sprint retrospective

Helps the development team identify best practices it can use in subsequent sprints

The last activity in the pre-game phase for the web site project is to create a high-level design for the project. Which activities occur during the high-level design review?

Identifying which components of the web site should be delivered in each, fixed-length sprint Reviewing the product backlog to establish the web site's basic architecture

Sprint planning meeting

Involves creating a sprint backlog

What are characteristics of the daily standup meeting in Scrum?

It lasts for a maximum of 15 minutes Team members, who remain standing, update one another on their progress

Business value delivered

Measures how many user stories or story points the team needs to compete

Velocity

Measures how many user stories the team delivers per sprint

Identify activities that occur during sprint planning meetings.

Splitting each product backlog item into multiple sprint backlog tasks Charting the work that should be performed in a sprint

Sprint review

The Scrum team assesses whether a sprint adhered to its goal

In Scrum, pre-game planning includes establishing a project's goal and define product functionality. Who is involved in this process?

The product owner The customer

Sprint retrospective

The team meets with the customer and Scrum Master for three hours after the sprint review

Standards violation

Tracks of the number of design guidelines a team failed to follow during a sprint

Progress chart

Tracks the current status of tasks in a sprint