article thumbnail

Do you deliver dazzling demos?

Kiron Bondale

Demos, or showcases as they are sometimes called, are a critical ceremony when they are run effectively as they address multiple project delivery objectives in a single event including: Validating that what the team has completed to date is valuable from the perspective of their customer and other key stakeholders. committed vs. completed).

Cadence 120
article thumbnail

Myth: Scrum is a Waste of Time

Scrum.org

These events need to happen on a cadence of one month per less to ensure that the team is collaborating frequently enough to reduce risk (the Sprint). It’s not juts a demo, it’s an opportunity to inspect the increment that was delivered and to collaborate with Stakeholders on what would add the most value in the future.

SCRUM 173
Insiders

Sign Up for our Newsletter

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

article thumbnail

Seven Sins of Reviews

Kiron Bondale

Whether your team sets a regular cadence for external product reviews or they are conducted on a just-in-time basis, it is important to get actionable feedback. Holding a demo rather than a two-way exchange. But conducting a review is not just a matter of bringing people together.

Cadence 339
article thumbnail

Comparing Nexus and SAFe - Similarities, Differences, potential synergies

Scrum.org

Empiricism via working integrated increments every Sprint - System Demo & Nexus Sprint Review meeting a common Definition of “Done”. The Nexus Sprint Review and the System Demo are similar events happening on a similar cadence - every several weeks (Sprint/Iteration). What’s appropriate is a matter of context of course. .

Cadence 137
article thumbnail

How to Use Flow Metrics to Optimize Product Delivery

Scrum.org

Armed with the data, you can set realistic deadlines, allocate resources efficiently, and prevent delays that might disrupt your delivery cadence. ActionableAgile has a nice explanation and demo video on how and when to run a Monte Carlo simulation using their tool. This metric is purely an output measure.

Cadence 170
article thumbnail

Agile Communications Plans

Leading Answers

Demos  – Having the team demonstrate increments of functionality at the end of every iteration shows what the project has achieved to date. Frequent demos mean the project never disappears for long. It is this predictable cadence of show-and-tell sessions that creates the dolphins-versus-submarines comparison. 

Agile 135
article thumbnail

Stakeholder Communication Strategy: Part 3 of 4 Steps of Stakeholder Engagement

Scrum.org

Again, not to my surprise, the response was ‘people are not interested in the demos’. A regular cadence of 1:1 meetings will be needed. My next question was why we are not having these conversations in the Sprint Review and why stakeholders are not attending the Sprint Review.