From the course: Agile Software Development: Scrum for Developers

Sprint overview

From the course: Agile Software Development: Scrum for Developers

Start my 1-month free trial Buy for my team

Sprint overview

“

- [Instructor] Scrum teams build products in an iterative and incremental manner, each time boxed iteration of work is called a sprint. The sprint is often described as the container event for all other Scrum events. Let's take a quick high-level view of the sprint event. Each sprint starts with an event called sprint planning. Scrum team members continue to sync their work on a daily basis in another daily event called the Daily Scrum. Each sprint ends with two events, the sprint review and sprint retrospective. This entire iteration cycle is called a sprint. This cycle continues to repeat as the Scrum team builds a product. In Scrum, each sprint must have a duration of 30 calendar days or less. Most teams prefer sprints that are one to two weeks long. Each sprint must end with a potentially releasable product increment. The product increment may get released to the user community in production immediately, or later, at the product owner's discretion. The product increment needs to be a vertically sliced portion of the product that provides end-to-end functionality. It should be usable in production and provide business value. A good example of a product increment is working software that allows a user to search for a product by providing the product name and price range. This includes components that work at the user interface layer, business layer, and also the database schema layer to support the business functionality. A bad example of product increment is a database schema or mocked user interface with no business functionality.

Contents