article thumbnail

“Agile Is Just for Software” and other Scrum Myths

Scrum.org

For example, Scrum includes five events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review and the Sprint Retrospective. PI Planning serves as the cornerstone of the Agile Release Train within SAFe, establishing a synchronized cadence for multiple teams to work together towards a common goal. It is deliberately incomplete.

SCRUM 177
article thumbnail

How We Reduced Cycle Time from 164 Days to 8 Days in 6 Months

Scrum.org

In December 2020, my friend Adrian Galarza and I delivered a Scrum.org Scrum Pulse Webinar - A Cycle Time Journey: 164 to 8 Days in 6 Months that summarized the journey of Adrian’s Scrum Team. Due to horrible time-management on my part, we could not answer all the questions in the webinar, so we are answering them in this blog instead.

Cadence 221
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

5  misconceptions about Scrum's Sprint Event

Scrum.org

As the 2020 Scrum Guide puts it, “Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.”. It is a container event, which means that it contains all other events, including Sprint Planning, the Daily Scrum, the Sprint Retrospective, and the Sprint Review. Conclusion.

SCRUM 196
article thumbnail

A modern (and easy) guide to the 5 agile ceremonies

Planio

Sprint review ceremony. Agile ceremonies — also known as Scrum ceremonies or just ‘events’ — are specific events that provide a structured framework for iterative software development processes. Agile is an umbrella term for different iterative and feedback-driven software development processes. (And why do they matter?).

Agile 88
article thumbnail

Getting started with a Definition of Done (DoD)

Scrum.org

In my last post about Professional software teams creating working software David Corbin made a good point. Updated to reflect the 2020 Scrum Guide! TL;DR; Your Developers are ultimately responsible for creating done increments of working software. The 2020 Scrum Guide. Done Increments. So what do you do?

article thumbnail

Release planning and predictable delivery

Scrum.org

Updated to reflect the 2020 Scrum Guide! TL;DR; Without working software, you can’t build trust and you don’t know when you will get the next piece of working software. Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software.

article thumbnail

Sprint Anti-Patterns

Scrum.org

Every activity required to achieve the Product Goal, such as Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, occurs within Sprints. Source : Scrum Guide 2020. It just feels good to solve yet another puzzle from the board, here: coding a new task. Scrum as a framework is mainly of a tactical nature.