article thumbnail

Myth: Scrum is a Waste of Time

Scrum.org

One of the first things that people new to Scrum learn about is the five events. The five events in Scrum are 1) the Sprint, 2) Sprint Planning 3) Daily Scrum, 4) Sprint Review and 5) the Sprint Retrospective. When people first start learning about Scrum, it can seem like Scrum requires many meetings.

SCRUM 168
article thumbnail

The Rhythmic Dance of Agile with Cadence

MPUG

Now, you might be thinking what exactly a dance has to do with cadence in Agile? Let’s start first with the definition of cadence. Cadence – Definition and Basics. One can define cadence in Agile as follows: Cadence is a regular, predictable pattern of development work in Agile. Working with Single Cadence.

Cadence 115
Insiders

Sign Up for our Newsletter

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

article thumbnail

The Forgotten Scrum Event

Scrum.org

What are the 5 events in Scrum? Chances are that you said something like “Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and…. The Sprint is the most commonly overlooked event in Scrum. In fact, many people don’t even realize that it is an event in Scrum. A shorter Sprint is better to reduce risk.

SCRUM 157
article thumbnail

A 2021 Guide to Kanban Cadences to help Align Your Business Communication

nTask

If you have been studying the project management paradigm for a long time then you would know that Kanban is one of the most flexible of the agile frameworks out there. This flexibility comes when you as a manager ask the team to act based on the demand out there. What are Kanban Cadences? There is no scheduled timetable.

Cadence 78
article thumbnail

Managing Project Assumptions and Risks

The IIL Blog

By Alan Zucker We make hundreds of assumptions and take small risks daily. Recovering from these risks may be inconvenient but not horribly impactful. Project assumptions and risks are not as casual. Project assumptions and risks are not as casual. Our risks were identified, but a response strategy was never created.

article thumbnail

Size work to support incremental delivery

Scrum.org

I once worked with a Scrum team that deliberately underestimated the size of Product Backlog items during refinement to enable them to pull oversized items into the Sprint, bypassing the team agreement that restricted larger items from being pulled into the Sprint. Why would they do this? This reduces transparency and trust.

Cadence 168
article thumbnail

“Agile Is Just for Software” and other Scrum Myths

Scrum.org

Scrum is the most popular Agile framework. According to the latest State of Agile survey from Digital.ai, 90% of teams who are using an Agile framework are using Scrum. I like to think that this is because Scrum is a goldilocks framework … with just enough - but not too much - structure. That is the power of Scrum.

SCRUM 166