Remove Cadence Remove Engineering Remove Estimate Remove Technical Review
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. When Inaccurate Estimation Results in Delayed Delivery.

Lean 64
article thumbnail

A modern (and easy) guide to the 5 agile ceremonies

Planio

Sprint review ceremony. Sprint review: At the end of each sprint cycle, teams meet to demo what they’ve shipped and get early feedback from stakeholders. These review sessions can be informal ‘show and tell’ sessions or more formal meetings. (And why do they matter?). The 3 key players of every ceremony. Daily scrum ceremony.

Agile 88
Insiders

Sign Up for our Newsletter

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

article thumbnail

New PM, New Choices

Leading Answers

When our projects undertake defined, repeatable work using technologies and approaches our organizations have experience in, then uncertainty and change rates are typically low and manageable. Here, formal planning and estimation are difficult because we don’t know what we will encounter.

article thumbnail

Product Discovery Anti-Patterns Leading to Failure

Scrum.org

Apparently, there is a difference in the inspect & adapt cadence when product strategy and Sprint Backlog are compared to each other. The product roadmap needs to be adapted to the learnings from running product experiments regularly in an appropriate cadence to meet that standard. The engineers and I handle customer support.

article thumbnail

Handling Unplanned Work

Leading Agile

Technical teams who are building or supporting application software usually work from a prioritized list of improvements, new features, and ideas to try out. All that unplanned activity used to create stress for technical workers. What happens when the actual time to complete a piece of work differs from our estimate?

article thumbnail

Overcoming the Barriers to Business Agility

Leading Agile

The roles, the ceremonies, the artifacts, the cadences, all those different things that we model as implementation details. Are we doing story point estimating or are we using planning poker? Are we doing reviews? What kind of reviews and retrospectives are we doing and how are we doing them?”

Agile 62
article thumbnail

Release planning and predictable delivery

Scrum.org

Without a regular cadence of delivery of working software any belief that you will get a usable increment is misguided at best. Even in manufacturing if you asked an engineer how long it would take to develop a new type of unit of work they would not be able to tell you with any certainty. Release planning and predictable delivery.