Remove Cadence Remove Events Remove Software
article thumbnail

5  misconceptions about Scrum's Sprint Event

Scrum.org

The Sprint is one of the five events defined in the Scrum Guide. 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. According to the 2020 Scrum Guide, the Sprint is the “heartbeat” of Scrum. Conclusion.

SCRUM 228
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. The Scrum guide clearly describes the purpose of each of these events, but the Scrum guide doesn’t include a required agenda for any of these events. It is deliberately incomplete.

SCRUM 207
Insiders

Sign Up for our Newsletter

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

article thumbnail

Minimal measures for minimal stability in a complex environment

Scrum.org

Product development is the subset of complex problem domains where Scrum took root first; by explicitly acknowledging software and new product development to be complex work, serving to deliver complex products in complex circumstances. Benefit from the consistency that the Scrum events provide without industrializing your Scrum to death.

Cadence 247
article thumbnail

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

Scrum.org

CADENCE & RELIABILITY. CADENCE: What was the sprint cadence you folks started off with? What was sustainable cadence after improvements? In addition to all 5 scrum events, we added a pre-planning meeting at the halfway mark of the sprint to look ahead at the next sprint. UAT is part of DOD. .

Cadence 222
article thumbnail

How to make value flow without interruptions in SAFe

Scrum.org

Such elements might include handoffs (specialization or authorization), queues (describing the same work at different levels), groups of teams not working in the same cadence, etc. Proposed remedial actions: Try to match the size of the work realistically to the cadence (do the stories fit in the iteration, and the features in the Pis?).

Cadence 195
article thumbnail

Beyond Mechanical Scrum

Scrum.org

The teams at his company had well established cadences for their Scrum events; well-oiled Daily Scrums that are done within 15 minutes and result in transparency of what the team will do for the next 24-hours. They are releasing software after every 2-week sprint. Get the basics in place and yes, you are doing Scrum.

article thumbnail

How Agile Practices Enable Remote Working

Scrum.org

The following five simple events derived from Scrum offer leaders and managers a way of regularly checking-in with their teams, always being present for them without falling into the pitfalls of micro-management. We know Agile is not just for software teams. For leaders, these events facilitate the ability to support your teams.

Agile 191