Remove Cadence Remove Events Remove Software Review Remove Technical Review
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. Or, imagine that your team is working in an environment with unstable technology.

SCRUM 179
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 159
Insiders

Sign Up for our Newsletter

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

article thumbnail

Troubleshooting in Lean-Agile Development

MPUG

It’s usually based on a cadence. As shown in the above figure, there is no regular timeboxed iteration, but incremental delivery can happen in cadence. When you fire a gun in the dark, it’s difficult to aim due to the lack of light. Developers, with all due respect to them, are generally optimistic people.

Lean 64
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. 4 – The Review. 1 – Planning. 5 – The retrospective.

Agile 248
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 197
article thumbnail

Improving SAFe Through Professional Scrum

Scrum.org

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. SAFe has a cadence at the Team and Program levels.

SCRUM 135
article thumbnail

The Increment Is Dead

Scrum.org

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. What we REALLY mean when we say Working Software. The Increment Got Us Here.

Cadence 133