Remove Cadence Remove Information Remove Lean Remove Software
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. Flow-based.

Lean 65
article thumbnail

Project Management: Principles, Practices & Context

Velociteach

Everything from putting people back on the moon, developing new therapeutics and software, or planning a wedding. Lean manufacturing influenced the quality movement, Agile , and DevOps. Lean Lean principles originated in Japan’s manufacturing sector after World War II but have since been adopted by various industries worldwide.

Lean 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

How Do you Make a Retrospective an Interesting Session?

NimbleWork

Many teams lean into retrospectives to help uncover areas where processes could be slicker, where engagement hasn’t been as effective as it could and to look for areas of improvement. The output from the retro informs the next sprint. You’ll find them at the end of an iteration, for the team to look back on that portion of the work.

Cadence 109
article thumbnail

A Deeper Look: Top Changes in the New 2020 Scrum Guide for Agile Practitioners

MPUG

It’s less prescriptive and seems to be intended for a wider audience group, particularly non-software users. The new guide clearly informs that Sprint Reviews should not be considered “gates” for releasing value. Introduction of Cadence. For the first time, we are introduced of a concept called “Cadence.”

Cadence 116
article thumbnail

Disciplined Agile & SAFe

International Institute for Learning

They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. They are “open source,” with all the information publicly available. They emerged about a decade after the Agile Manifesto.

Agile 59
article thumbnail

Release planning and predictable delivery

Scrum.org

TL;DR; Without working software, you can’t build trust and you don’t know when you will get the next piece of working software. Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Professional Developers create working software.

article thumbnail

How to Set and Achieve Effective Sprint Goals

Scrum.org

Teams can amalgamate information on the product's strategic direction, the product owner's current tactical direction, and ongoing engineering aspects. Create a Cadence of Accountability. Lean-agile practitioners thrive on these kinds of challenges, but most teams find daunting. When are Sprint Goals crafted?