Remove Cadence Remove Demo Remove Lean Remove Risk
article thumbnail

Facilitating Effective Sprint Reviews

Scrum.org

We and others have experienced Sprint Reviews more as performance reviews or demos that feel like one-way presentations from the team. The event was fairly well attended, but after a demo very little else happened. To mitigate these risks, a team and its stakeholders can agree on some lightweight rules for making decisions.

article thumbnail

Creating a Risk-Adjusted Backlog

Leading Answers

This article explains what a risk-adjusted backlog is, why they are useful, how to create one and how teams work with them. What is a Risk-Adjusted Backlog? A risk-adjusted backlog is a backlog that contains activities relating to managing risk in addition to the usual features associated with delivering value.

Risk 145
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

Many project managers utilize a Lean-Agile approach when there is high change or churn in project requirements, significant lack of clarity in scope, high complexity to their projects, and/or a larger number of risks associated with such. Two Lean-Agile Types. Iteration-based Lean-Agile. Flow-based Lean-Agile.

Lean 65
article thumbnail

Review: Introduction to Disciplined Agile Delivery

Henny Portman

DAD is characterized by the following aspects: Hybrid: combines Scrum, Agile Modelling, XP, Unified Process, Kanban, Lean, Outside-In Development (OID) and other methods. Every day there will be a coordination meeting and the iteration ends with the iteration review/demo and the retrospective. Full delivery cycle.

article thumbnail

New PM, New Choices

Leading Answers

Yet when projects use new (to us) technology and tackle problems our organizations have not solved before, then risk, uncertainty, and rates of change will be high. Approaches like lean, kanban and agile work well in these uncertain, high-change environments. Integrating with the COTS software was a hybrid process.

article thumbnail

Team using “Waiting for Release” column on their kanban board

Digite

It is then up to them – or some business function like sales or support – to have the conversation with your customers that they need to accept new releases at a certain frequency or they may be at a risk of not getting the support they might need on an old version of the product.

article thumbnail

Kanban = Continuous Delivery? Not Necessarily

Digite

It is then up to them – or some business function like sales or support – to have the conversation with your customers that they need to accept new releases at a certain frequency or they may be at a risk of not getting the support they might need on an old version of the product.