What Is Scrum Development?

What Scrum development delivers

The goal is to solve complex problems while delivering products of the highest quality and value. The Scrum development cycle does so iteratively but isn’t limited to product releases or increments. The process itself is reviewed and improved so that the following cycle can run more effectively. 

It’s the responsibility of the Scrum master to ensure that value is delivered beyond product increments. To measure this, they will be defining and monitoring Scrum metrics including:

• Productivity
• Reduced time to market
• Team happiness
• Collaboration effectiveness

Scrum development events

These are also referred to as ceremonies and, along with team roles and artifacts, they define the Scrum framework. Scrum development events usually take place in and around the context of a sprint, a time-boxed period of time lasting between 1 to 4 weeks when specific work is completed. 

• Sprint planning: Product owners and the development team meet to decide which product backlog items should be tackled in the sprint.
• Daily Scrum: These are time-boxed to 15 minutes and typically take place around a Scrum board, whether a physical or virtual one. During the meeting, developers discuss progress, challenges, and their plan for the next 24 hours.
• Sprint review: As described in the Scrum Guide, the purpose of the Sprint review is to “inspect the outcome of the sprint and determine future adaptations.” 
• Sprint retrospective: While the Sprint review focuses on the product, the Sprint retrospective is the opportunity to review and improve the process itself.