Remove Cadence Remove Events Remove Software Review
article thumbnail

Facilitating Effective Sprint Reviews

Scrum.org

In Scrum, the Sprint Review event is when the Scrum Team collaborates with stakeholders by inspecting the work that was completed during the Sprint and discussing how to move forward in a valuable way. However, in our experience, it is rare that teams get the full value that they should from their Sprint Reviews.

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 194
Insiders

Sign Up for our Newsletter

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

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 176
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. Kanban 101.

article thumbnail

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

Scrum.org

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. You might get more value from reading this blog if you watched the recording and reviewed the slides that are available on the webinar page - A Cycle Time Journey: 164 to 8 Days in 6 Months.

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. This will make a visit to a Review time well spent. That’s because software development is complex, i.e., too many unknowns exist.

Cadence 179
article thumbnail

Scaling Agile Practices – Improve Business Outcomes

Agilemania

Develop on Cadence; Release on Demand. In SAFe®, this is known as Develop on Cadence, a coordinated set of practices that support Agile Teams by providing a reliable series of events and activities that occur on a regular, predictable schedule. Agile Team and Agile Release Train Cadences. Release on Demand.

Cadence 98